"Only Experienced AI Pilots should attempt to fly this model

[Russell Irwin]

I may be wading into murky territory here, but here goes:

I've been downloading AI Aardvark's FSX native models and pairing them up with default virtual cockpits and third-party FDEs. Normally, this works well (E-Jets, DC-9, B767-400), but I've been unable to do it well with the 747 classic series. What I've been doing is downloading an old POSKY package and merging the two .cfg files (and keeping the POSKY .air files), leaving almost everything to POSKY but the contact points. What winds up happening, however, is that in some spectacular fashion, despite the positive affirmations from the FSX weight and balance window, the 747 will manage to tilt backwards, force its tail through the tarmac, and cause a "CRASH" message. I'm wondering if the problem is with the model itself, as my approach has worked well for all of the models mentioned above.

I can't write more right now; I'm on the road and WiFi (and time) is scarce.

Thanks much,

irwinrussell60

[Staiduk]

Odd. Can you provide info regarding the specific packages you are using and what exactly you did to combine them? You did well but without specific URL's etc. I may not be able to replicate your problem.

It seems to me that somewhere along the line your CoG has become horribly messed up; leading to the tail-heavy condition you describe. No airplane can fly if its Center of Gravity is too far aft. Who knows - it may me something as simple as a missing minus sign in the .cfg.
Point me to the exact models you are using and I'll try to replicate it.
(Edited to add: attaching the 'before and after' .cfg's would help too.) Cheers!
(Edited to edited to add...First; I should read the WHOLE post before responding. Second, you said this:

What I've been doing is downloading an old POSKY package and merging the two .cfg files (and keeping the POSKY .air files), leaving almost everything to POSKY but the contact points.

OK; sounds to me like you're trying to make what is effectively a completely different config file work for a different aircraft; even if the models are similar. That's a disaster in the making; the Config file determines how a flight model interacts with the FSX simulator. Thus trying to force a config file to work with a different - even similar - model and .Air file can turn into a bucket of worms flambe; which it looks like you're seeing right now.

Still upload the packages and the before-and-after .cfg's if you can; but my advide would be don't try to swap one .cfg for another - I gave up on that years ago. Instead begin working with the existing one bit by bit until the plane does what you want. It's a slow; often frustrating procedure but has much better results in the long run.

Cheers!