posted 09-25- 10:41 AM               

From what I gather:
Airfoils were in startup.ppf OK. (with carriage return at end)
No unknown objects in missions.

Is there something I did wrong? Could it have anything to do with the type of renderer they are using? Maybe it is the colour depth of the skins?

While were on the topic, does anybody have any idea why the autopilot hates me so much? All I did when I made the aircraft:

1) Start with Whirlwind's model, export LODS into Max.

2) Spend many many hours figuring out max, texturing, exporting, resizing.

3) Import new LODs into OPS. Moving many things around. (Damage visuals, etc.)

4) Repeat 2&3 a million times until satisfied. (Importing bits and pieces from Mosquito (rocket and bomb rails), Dauntless (props). I thought I ensured that there were no texture references to non-standard planes (Does the Plane pack change the .tif reference locations? ie ju88->ju88a?... would it matter?)

5) downloaded airfoil coordinates from uiuc database. (changed one to 18% chord) imported into Java applet at DLR. Combined results in Excel with the current Ju88a airfoil. Saved as .ppf file.

6) Changed all airfoil/engine/prop/weight, etc. values and airpt locations to represent beaufighter as accurately as possible (not much data though).

7) Change prop and drag values until fly seemingly well......also spent a day or two making sure that the plane was balanced. (this is how I got the AI planes to fly, although the changes made for Version2 seems to have disturbed this a little)

7) Play with shadow coordinates for each object until acceptable (still not happy).

8) Copied and pasted Pe-2 damage model, changed object references where necessary.

Where could I have gone wrong?

Help!

posted 09-26- 02:25 AM               

I believe that they use the 1.5 patch but haven't asked about pp5.3.

(or do you mean what other planes have they added?)

posted 09-26- 04:10 AM               

I seem to recall there were some problems with a model reference in the SM which got fixed early on. Some fixes were released. Could be the problem.

Otherwise,the most common erason for a CTD is that there is a reference to a model part that has a wrong name or is missing, or a texture that is missing. Bad geometry in a model LOD is another, but this would not be an intermittent thing.

Did you reference parts or textures from another plane in the Beau?

posted 09-26- 10:20 AM               

I sent out a message and am waiting for a response.

One of them already tried to make a fresh mission and it was a no go.

I tried to make sure that all the part/texture references were from the original planes, but I wouldn't put it past myself to have missed one.

If you look at the texture list in OPS you will see that there are a million of them. Early attempts to erase unused texture names resulted in OPS crashes so I resolved myself to have a very large confusing list.

When I get a response I will let you know.

Thanks,

Bishop

PS. How long until I get to be a pilot? My cadet's uniform is riding up.

posted 09-27- 02:58 AM               

I just received a message from one of the crash victims. Apparently, he is flying now. His problem is now with a DMC mission with the Spit and Typhoon where the gun sounds sometimes work and don't.

As far as I know, this shouldn't be a problem in the .sm file and is more likely his hardware setup.

By the way, he had pp5.3, Nations, etc... (to quote: "everything") so the fact he is flying now seems to point to a problem with referencing something in one of the other planes (probably pp5.3). If the other guy reports back I'll let you know.

Thanks for your help.