• 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

Arno also acknowledges that MCX can't EXPORT FS9 aircraft mdl's successfully at the moment - so we must be a long way from converting them to FSX.
Cheers
Jont
 
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.

AIAardvark's FSX models use their FS9 FDE filesets and work without a hitch, so the FDE can't be the culprit.


Still, thanks for the input.
 
As I say - I'm pretty sure the problem lies with the animation(s). I get normal behaviour from the converted mdl files if I 'fix' all the animations in MCX before the conversion. IMHO I don't believe it has anything to do with the cfg and air files. However, I am not an expert and I very much value other people's thoughts on this.....
Cheers
Jont
 
Could it be....radius ?

Pardon me for butting in with my first post here, but I've been following this situation a bit having just migrated over to FSX from FS9 in the past months.

After reading about your experiences after attempting to convert FS9 models over to FSX, namely AI models, I decided to give it a shot myself, and of course I saw the same results as you all have.

It just doesn't make any sense though, that animations or any bad translations thereof could cause what we are seeing. So digging further I found something that might be of interest:

The model radius of all FS9 models converted with MCX is set to an extremely high value, IF one takes the time to reassign all animations. It also will create an enormous crashbox.

On the other hand, if one just simply clicks the "Fix Animations" button, which of course strips out the animations, the resulting model retains the radius value it was imported with. This would explain why, when we don't fix the animations, and just export, the behavior is normal, but of course the animations are missing.

I know that the radius value is not set in the same manner for an FS9 model vs an FSX model, and I am also aware the wingspan is used for selection of parking, but that is really all wingspan is used for (other than flight dynamics of course), radius is still used for determining ground movement, spacing, etc of AI->AI and AI->User aircraft.

Looking further, I decided to have a look at what the native (or at least properly converted) FSX AI models were showing for radius values. Sure enough, both the Aardvark FSX set, and the TFS models from UT2 (I only use the models :D ) show correct radius values, or at least, the values that were most likely set for FS9 before conversion.


Some examples:

This is the resulting radius after reassigning all animations for the AIM ERJ-145:

Code:
            <FriendlyName>AI Malcontent ERJ145</FriendlyName>
            <ModelGuid>{aeae3732-8a2e-4d60-b0b3-36a7861db59d}</ModelGuid>
        </Header>
        <ShadowMapReady>FALSE</ShadowMapReady>
        <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
        <!-- Exterior model -->
        <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
        <Exterior>
            <BoundingBox>
               <Min>-2252.8,-1106.944,-833.5361</Min>
                <Max>2252.8,1506.304,862.209</Max>
            </BoundingBox>
            <Radius>2270.39665115261</Radius>[

The resulting radius of 2270 and bounding box is so large that it is entirely likely that the sim has no idea what to do with it.

Here is the A340-600 from UT2:

Code:
            <FriendlyName>TFS_A340-600_FSX</FriendlyName>
            <ModelGuid>{3f0e06e7-296f-417a-b5fe-d58820246b00}</ModelGuid>
        </Header>
        <ShadowMapReady>FALSE</ShadowMapReady>
        <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
        <!-- Exterior model -->
        <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
        <Exterior>
           <BoundingBox>
                <Min>-31.8468,-15.40641,-38.63084</Min>
                <Max>39.90355,11.50554,36.69958</Max>
            </BoundingBox>
            <Radius>40.4233997058418</Radius>

No issues there, that is right where it should be, 40 was it's FS9 radius IIRC.

Finally, here's the ERJ again, same source model, but this time I didn't reassign the animations before exporting:


Code:
            <FriendlyName>AI Malcontent ERJ145</FriendlyName>
            <ModelGuid>{ee597e8a-df0a-436d-914f-27020e896d98}</ModelGuid>
        </Header>
        <ShadowMapReady>FALSE</ShadowMapReady>
        <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
        <!-- Exterior model -->
        <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
        <Exterior>
            <BoundingBox>
                <Min>-10.148,-0.784,-14.684</Min>
                <Max>10.148,5.184,15.18</Max>
            </BoundingBox>
            <Radius>15.9417127119823</Radius>

Again, no issues, 16 was it's FS9 radius, but obviously there wouldn't be any animated parts left.

Could that be it ?
 
Last edited:
The model radius can be edited with Arno's RADitor tool (included in the ModelConverter download), so that isn't much of an issue.

(This makes sense, btw. With an awfully large radius, FSX' AI system seemed to just go out of its way to keep the model away from other planes. Hence the drunk taxiing all across the field.)

I don't have time right now, so...any volunteers? :)
 
If I would have known about RADitor last night you wouldn't have needed to wait for an answer :D

Yes, it seems to work just fine now, after readjusting the radius and bounding box.

It does not help with the crashbox size though, so I have been exporting with nocrash set to true.
 
Last edited:
Certainly seems to.

Looking through the hierarchy you can see that many of the individual parts likely are responsible for the huge radius/bounding box being set for the entire model on export, but, making RADitor adjustments back to original values and all seems well. As I said though, I am exporting with nocrash=true.

The only things "lost" other than the incompatible animations, seem to be the attached landing/taxi lights and ground splashes. Everything else seemingly remains intact, and performance in-sim is definitely improved over the original models.

All of my regional jets were subbed by ejets until now since I refused to use models that weren't recompiled. Nice to have the CRJs/ERJs back ! :D
 
The only things "lost" other than the incompatible animations, seem to be the attached landing/taxi lights and ground splashes.

And prop disks for propeller aircraft.

(By "incompatible animations" you mean anything with custom XML code, right?)


Nice to hear that it's working. Need to redo the conversion of the most widely used models once I have the time.
 
Back
Top