There is a "Patch1.exe" in the download folder.
It installs/overwrites lots of things, including the "PSMV4.exe" which you should use in preference to the "PSMV2.exe".
Run it in your "140PSM" folder.

There is also a "MAKE SURE YOU DO THIS.txt" file installed which reads:

Task #1
Go to the "Aircraft_Inventory" folder
Cut "Planes_ETO"
Paste it into the root folder


Task #2
Go back to the "Aircraft_Inventory" folder
Delete the "Planes_24BitTest" folder.
The one put into the root folder by this patch has a more user friendly structure

Task #3
The "Malta140_Planes" folder has "DAW" and "Malta" folders in both the "FMs" and "Skins" subfolders.
Delete any that are not "DAW"
The Malta ones are re-installed by the patch in a "Original Malta Planes" folder.

Task #4
Do a search for "weapons.dat" and "weapons.str" files.
The only pair you need are in "savedata"
Delete all the others as they are incompatible and cause CDTs.
I forgot to delete a few from the theatre folders in the first place.


If you prefer to be cautious then copy your "140PSM" folder, name the copy as "UAW150" and run the patch in that folder

Jel

So here we go.

There are problems with the weapons and the loadouts in SPAW.

First I noticed that the para racks were not located in the same position under the wings.

As this could be either a loadout problem or a 3dz hardpoint problem the first thing I did was copy the A20G wings from DAW, which are correct, over to the A20G in SPAW. (As an aside, this is a perfect example of how easy it is to move things around in the new system. No slot renaming needed, just copy / paste the files and you're all set.)

I had set up a planeset of just the A20G from DAW and SPAW so I could easily compare them. ( Again, dead simple for checking out conflicts of this nature )

Anyhow, this did not fix the problem meaning that there's something off in the loadout of the new SPAW. It's actually worse that that because there are certain loadouts in the SPAW A20G that are carrying two weapons on the same hardpoint at the same time.

I'm not worried, we'll get it all sorted but it does point out that those of us who support this system need to take a good, detailed look at it.

Next up I found that the parabombs are dropping like bombs again. We had this problem before and it's back. The parabombs as originally configured drop like drop tanks so that they sail back behind the plane. I know some work was done recently on cargo drops so maybe something crept back into the code that we already solved.

Also, I see a few new SPAW FM's, like

SPAW_B5N25(Torpedo)_FM
BillsAvenger (Torpedo)_FM
NewFT-A6M2-N Rufe_FM
NewFT-E13_A Jake_FM
NewFT-F1M1 Pete_FM
PBY-5 Catalina (USN)_FM
Axis_Catalina_FM

I have no objection to these additions, in fact I'm glad to see them as it means someone else is keeping things fresh. However I would like to know what they are.

Lastly for now, while testing the two A20G's I experienced CTD's in single mission mode but not in instance mission mode. I seemed to have solved it by adding an enemy plane. If that turns out to be true it would be a good thing to add a warning about that somewhere on the selection planeset maker screen.

I'm not going to bother testing any more SPAW planes for now since the loadout problem probably infects all of them to one extent or another.

So I will thoroughly check the Med planes for now.