• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA AI Models -> AI Behaviour

Heretic

Resource contributor
Messages
6,830
Country
germany
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?
 
Something to do with the resulting bounding box and the contact points? Perhaps they are not registering as having their wheels on the ground?
 
FSX uses more from the aircraft.cfg than FS9. Try substituting an FSX aircraft.cfg (keeping the lights and contact points) and using an FSX .air file.
 
Something to do with the resulting bounding box and the contact points? Perhaps they are not registering as having their wheels on the ground?

That's another train of thought...



FSX uses more from the aircraft.cfg than FS9. Try substituting an FSX aircraft.cfg (keeping the lights and contact points) and using an FSX .air file.

That would be one heck of a weird twist if it worked.
 
Hi
In the original thread - this was my post on 18 Sept.......

Hi
I have found that when the ai FS9 aircraft mdl's are converted to FSX ai aircraft mdl's, their behaviour is odd. They often push back much further than they should and then wander off like naughty children!! It could be my 'test' traffic bgl, but I don't think so......
Cheers
Jont

Now.......

I think I must have done all sorts of mixing with the FS9 and FSX cfg files - but no luck so far.......

Cheers

Jont
 
I think also - we need to be mindful that MCX cannot even export FS9 aircraft mdl's successfully at the moment (try this - import an FS9 aircraft mdl - make no changes and then export it - save the file as an FS9 aircraft mdl - import this mdl back in and you will see what I mean) - so any attempt to go one further and convert it to an FSX aircraft mdl is also bound to be fraught with difficulties......

I guess the starting point for MCX would be the successful importing and exporting of FS9 aircraft mdl's first...

Cheers
Jont
 
Last edited:
Modelconverterx can export FSX mdl files fine. And there is no difference between scenery and aircraft any more.

For Fs2004 this is indeed not the case. It is not even possible to export a Fs2004 aircraft mdl at the moment.

Some Fs2004 aircraft mdl files load fine. And before exporting to FSX mdl the animations would have to be checked, else there can be problem.

If there are specific issues with aircraft I would like to know so I can improve the x code written. So I'll keep an eye on this thread.
 

I must've overlooked your input in the other thread. Sorry!

Your confirmation that .cfg and .air file changes do not alleviate the problem, however, saves me a bit of hassle. So thanks for that in any case!
 
Here's a comparison between the model in MCX. FSX version to the left, FS9 version to the right.



The bounding boxes and animations themselves show no difference.

Something that *is* different, however, is that there are entries named "custom_anim_[RIGHT/LEFT/CENTER] WHEEL ROTATION ANGLE_0X len=100" in the FSX model's animation list, whereas the FS9 model has "[c/l/r]_tire len=100" entries.

The entries in the Modeldef used for export in FSX format are simply copies of the default entries - "[l/r/c]_tire_[blurred or still]_key" - renamed to "[c/l/r]_tire", so that MCX can parse them automatically upon exporting.

It *could* be that MCX fails to parse the tire animations properly due to a lack of keyframes, with the bug cascading all the way down to FSX' handling of the model.


- Edit:

Tests in FSX.


Here's a converted model (AIM's DC-10) going haywire and slicing a 727 in half.




For this Skyvan, I have removed my Modeldef entries for "[c/l/r]_tire" and reconverted the FS9 version. The current version of MCX seems to guess animation names just fine, as the converted model shows a correct "[c/l/r]_tire" entry in the animation list. This does not help in the simulator though.




The problem affects every model I've touched with MCX. Aircraft built from source, e.g. AIAardvark's FSX models, which work just fine.



- Edit 2:

Another observation: Planes that do not have tire animations at all work just fine as well.



- Edit 3:

Going "Fix Selected Animation" on "[c/l/r]_tire" in MCX made the entries for the tags diappear from the list. An export produced a smaller model (because of the missing tire animations), but the problem persists in FSX.
 
Last edited:
How does a FSX mdl without any animations behave? That might help to see if it is the animations or something else.
 
Hi Arno
Yes - this may all be about animation - I use the FS9 TFS A380 as my 'test bed'.
If I import the mdl - make no changes to anything - then export it as an FSX mdl - in FSX the A380 looks all messed up and behaves badly on the airfield.

If I go back and again import the original mdl into MCX and then, in the Animation Editor, select ALL the animations and click on Fix Selected Animations - the re-saved A380 FSX mdl is complete apart from the undercarriage. It also behaves normally in the sim - push back, taxi, takeoff, climb, cruise, descent and landing are all good, but minus the wheels and all other animation. What I did notice however is that both the two ailerons and the two elevators were left in the down position by MCX. I wonder if the tire animation is not the only problem here......
Arno - if this could be sorted (converting FS9 ai aircraft mdl's to FSX ai aircraft mdl's) it would be a superb addition to an already very, very impressive program.
Cheers
Jont
 
Last edited:
Just loading a Fs2004 mdl and then directly saving won't work. You need to manually check all animations if they are assigned the right type.

I hope to make that more automatic in the future, but not sure if it's possible.
 
I really shouldn't put my nose in this tent, but I have no other tent to invade at the moment. :)

George above wrote:
FSX uses more from the aircraft.cfg than FS9. Try substituting an FSX aircraft.cfg (keeping the lights and contact points) and using an FSX .air file.

I think this is well worth attempting just as an experiment. It's been a long time since I did anything with AI aircraft (i.e., CFS2), but I've always thought that FS does not use the .mdl file for flight dynamics at all. Lately I've been attaching .air/aircraft.cfg files from other aircraft to my test plane in FSX just to look over things in their flight dynamics. (My test model has a digital flight data panel that I like.)

I just searched the aam.ini file for "FSX" and it is reported that there are lots of entries in the .air file that were used in previous versions of FS but now are controlled by entries in the aircraft.cfg file in FSX.

Could it be that your FS9 version has entries in the .air file that should be in the aircraft.cfg file in FSX? This is at least where I'd start.

I could be all wet on this, but it's worth a quick experiment as George suggests.

Steve
 
Well sir, I don't know. I would be interested to know more of what jont did exactly. I simply agree with your earlier statement:

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.

How about this for a test: Take the FS9 .air and aircraft.cfg files [=FD files] from your converted aircraft and attach them to a native MS FSX aircraft with its .mdl (making the contact point adjustment, of course) and see what happens. If the MS .mdl file behaves on the ground with your FS9 FD files then the problem is in your converted .mdl file. If it does not behave, the problem is narrowed down to the .air/aircraft.cfg setup.

Just trying to be helpful, not a pest. . . . :D

Steve
 
Hi Steve
I'm pretty sure the problem lies in the converted mdl file and around the animations - but great to have your input.
Cheers
Jont
 
Last edited:
It most certainly does Steve - but if Arno could pull off MCX successfully converting FS9 aircraft mdls to FSX aircraft mdls, it would be a stunning achievement.....
Cheers
Jont
 
Probably difficult to implement, but if we could move parts around in the hierarchy viewer, we could try temporarily merging in working wheels/tyres from a fsx native plane and try to isolate the problem. In theory I think this could be done by editing the .X file, replace the relevant frmpart etc. More difficult than it sounds.
 
Back
Top