Heretic
Resource contributor
- Messages
- 6,830
- Country

I've not too long ago converted the remainder of my AI models from FS9 into FSX format. They look fine, they animate fine, but they do not behave fine.
MCX converted models tend to not stick to the taxiways at all. I first suspected a broken AFX file, but this wasn't consistent with my observations, as other models *not* converted with MCX tend to taxi just fine. For good measure, I've reverted my test airport back to the stock configuration, but this did not help.
It's only the experimentally converted ones that exhibit the very odd behaviour of (probably) missing a turn and then simply taxiing across the grass before missing another turn and taxiing on and on and on while never arriving at their destination gate.
"Drunk" AI aircraft are commonly attributed to messed up flight dynamics, but I haven't changed anything in that department. Anything at all.
The only attempt at an explanation that I have thus far is something related to the models' animations. During conversion, I've assigned the default Modeldef tags to all animated parts listed in MCX, so the code itself should be fine. A nonsuitability of said tags for AI use can also be ruled out, as FSX' default aircraft taxi just fine when used as AI.
So my question is: What is going on in FSX' programming routines that makes model behaviour dependent on anything stored in the model file itself?
Last I've checked, anything related to the physical behaviour is handled by the aircraft.cfg and .air file. Some AI aircraft models don't even have animated nosewheels and they still turn just fine. Heck, you could even have a mere cube as an AI model and it would/should behave however the .air file tells it to.
Any ideas?
MCX converted models tend to not stick to the taxiways at all. I first suspected a broken AFX file, but this wasn't consistent with my observations, as other models *not* converted with MCX tend to taxi just fine. For good measure, I've reverted my test airport back to the stock configuration, but this did not help.
It's only the experimentally converted ones that exhibit the very odd behaviour of (probably) missing a turn and then simply taxiing across the grass before missing another turn and taxiing on and on and on while never arriving at their destination gate.
"Drunk" AI aircraft are commonly attributed to messed up flight dynamics, but I haven't changed anything in that department. Anything at all.
The only attempt at an explanation that I have thus far is something related to the models' animations. During conversion, I've assigned the default Modeldef tags to all animated parts listed in MCX, so the code itself should be fine. A nonsuitability of said tags for AI use can also be ruled out, as FSX' default aircraft taxi just fine when used as AI.
So my question is: What is going on in FSX' programming routines that makes model behaviour dependent on anything stored in the model file itself?
Last I've checked, anything related to the physical behaviour is handled by the aircraft.cfg and .air file. Some AI aircraft models don't even have animated nosewheels and they still turn just fine. Heck, you could even have a mere cube as an AI model and it would/should behave however the .air file tells it to.
Any ideas?







