Ok, I fixed the typo error in the "SPAW-1943 Early" plane set and I've uploaded a new planeset.zip file.

I see that eight members have already downloaded the new package. If you are one of them you need to redownload just the Planesets.zip file.

It's not crucial as it only affects the P40L in that one planeset.

Great collection, Ray. You must have been burning the midnight-oil for a long time compiling this. The cockpit gauges and gunsights are excellent. Now, I have a new way to crash or get shot down unawares-looking too long at my gauges.

With such a huge number of aircraft it's inevitable there will be an occasional mishap, and I certainly wasn't dedicated enough to find them all. The same might be the case with other planesets if we looked deeply enough.

Regarding the B-17E, in single-player escort missions, it doesn't appear at all, no CTD. In an intercept by Zero's of unescorted 17E's, the mission immediately ended with a return to base/mission accomplished message from ground-control and no sign of any 17E's.

What's this "NoDragStab", never heard of it?

There are some very strange "calculations" for flight modelling in 1.2, a bit like multiplying length by width to calculate something that is a perimeter.
The calculations were mainly connected with lift and drag if I remember correctly.
Knegel came up with something more plausible so we ended up with two types of "*.flt" files, old and new. Knegel's new versions are all in the "Planes_ETO" folder, whereas the ones in the "Aircraft_Inventory" are the old type.
They cannot be mixed in a planeset. If they are then you get a CTD. It s a bit of a PITA when it happens, so I made a botch in the code. If there is a file named "NoDragStab" in the root folder then the code generating the CTD does not run.
However, in reality it is much more desirable to have all the planes in every planeset of the same type (either old or new) so that the problem does not occur in the first place.

There is no data in the "NoDragStab" file, the exe just checks to see whether it is there or not.

Jel

Sky,

Our resident flight model expert was working on more sophisticated flight models (FM's) with things like two stage superchargers, nitrous oxide injection and a few other things. Unfortunately he had to leave our world due to real world issues and more than likely not to return.

We were left with a mish-mass of flight models which cause some grief until Jel came up with a band aid.

I've tried to keep to the old style FM's because it's what I know but it is always possible with such a large project that one or two new style slipped by me. Jel's band aid is insurance that if one slips by the game won't CTD.

One thing guys can do if the B-17E is the only one causing problems is to delete all the files in the B17E folder EXCEPT the pnames.str file and and copy over the B17F or G flight data set EXCEPT for the pnames.str file. The differences in actual game play would be negligible.

The B17E is in the DAW folder, listed as B17F. Small error on my part but it doesn't affect anything unless a player wants to get his hands dirty and goes looking for the "E". The B17F and G are in the ETO folder.

I just did a test using the 1.2 default B17 flt file renamed. No CTD, the bombers welcomed our arrival, but the skin is a bit weird


Its the same in some other planesets too

I'll say.

Those are Japanese HK6's, not B17's. I'll check and get back.

Edit:

Yep, wrong file set in the skin folder. It's fixed and I'll upload a new SPAW set overnight.

Problem

You have given two options. Player 1 uses "B17F" and player 2 uses "B17G". They fly online together and get a "different aircraft data" error when the host tries to launch the game.
When that happens nobody can play. A patch is needed so that everyone gets the same fix.

No problem. I'll just use one flight model for all of the B17's and upload a patch.

SkyHigh found another problem and I've fixed that too.

When I upgraded the gunsights with the ones I found on Talley-Ho I was having odd CTD's with some of the German planes.

Turns out, after much trial and error, that the late war REVI gunsight was corrupt. I replaced it with an earlier sight and all was well. I must have missed replacing it in the G10 folder.

I've replaced it which seems to have fixed the problem.

I'll add it to the new upload but I'll wait a couple of days to see what else shakes out.

FWIW, found a few small typos in the plane sets. Nothing dramatic but some planes won't show up until you get the new ones. I guess with over 350 planes there were bound to be a couple of missteps.

So if you haven't D/L'd from Mediafire yet, hold off. If you have D/L'd you can play without any problems and wait a few days until I upload the patched versions.

I've fixed the planeset typos and uploaded a new version to MediaFire. Besides the typos I found a few planes that were not apropos to the dates they appear in so I made a few small tweaks to that aspect too.

I haven't uploaded the aircraft inventory packages yet because I'm waiting to see if any more problems surface.

You don't need to update the planeset files if you don't want to, all that happens with the old set is that a few planes won't be available. You can wait until I upload all the corrected aircraft inventory files and do it all at once.

What happened to the "SPAW_MB3-2"? It seems to be AWOL from the new set and it is a popular plane to fly at GameRanger

There are now two version, brown camo and gray camo but they've been moved to the ALT planes folder.

I didn't notice that it was left out of the new plane sets. Easily fixed.

If I fly the B6N2 I can have bombs or torpedoes.
If I escort B6N2s they are unarmed. They go through the motions of bombing a target but they have nothing to drop.

I have not tested, but there may be more issues like this, and it is even trickier in multiplayer.

I'll take a look at the loadouts.

Edit - Only thing I noticed is that the torpedo is set for "Underwing" not "Fuselage". Same for the B5N.

Does the B5N have the same problem?