• 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.

Conversion Problem: MCX A320Neo FSX to FS9

super80

super80

Messages
12
Country
italy
Dear Arno and members of the FSDeveloper community,
I'm asking for help because I can't find a solution after numerous attempts. A few weeks ago, I managed to convert the Project Airbus A320Neo Iberia EC-NTP and fix, from FSX to FS9 with MCX (simviation.com/1/more-images?file=62864). However, after applying MCX, the conversion no longer works (I'd like to convert other A320Neos and 321Neos with PW and CFM engines). The problem mainly concerns the engines, because the conversion reproduces them with a strange hole in the center, or, even when they are turned on, the blades remain off. How can I solve this?

(I've attached some images)
Thank you very much.
Ivano
Ivano
2026-07-23_131415.jpg
 

Attachments

  • 2026-07-24_184121.jpg
    2026-07-24_184121.jpg
    55.2 KB · Views: 36
I guess the cone in the center is missing. If you load the converted MDL file can you see if it is really not there or is it maybe transparent?
 
Basically, when I reload the converted mdl file, the cone isn't there; they have no shape, and are transparent (cfm/pwn1_fast or cfm/pw_blur textures). So it flattens. When I turn off the engines (Ctrl+F1), the cone appears (it takes the cfm/pw_engine textures, I think). In FS, I can't see the engines depending on the A320Neo...etc.
Best regards
 

Attachments

  • 2026-07-24_184121.jpg
    2026-07-24_184121.jpg
    58.8 KB · Views: 35
Load the original model into MCX and open the Animation Editor. If any are red they will be removed from the model. They have animations MCX does not find in the model or modeldef.xml file. The fact that others do not turn suggests problems with animation.
 
Besides checking the animation as Tom said, you can also check if they have a visibility condition assigned to them. The fact that they appear when you shut the engine off could also mean that there is a visibility condition involved.
 
Hello.
The Animation Editor doesn't highlight objects in red. The Object Hierarchy N1 visibility condition for Blur and Fast.
...I load the A320Neo into FS9 and it already appears to have holes in the engines. Then in FS it appears with holes (engine cone without fans) and then with engines with fans off. It seems that FS9 doesn't recognize the animation when converting the aircraft. The strange thing is that the first A320neo worked, but then it didn't anymore (I've attached images).
 

Attachments

  • Load on FS9.jpg
    Load on FS9.jpg
    83.3 KB · Views: 47
  • A.jpg
    A.jpg
    135.3 KB · Views: 54
  • B.jpg
    B.jpg
    85.5 KB · Views: 49
You might want to check which variable is used by the animation in the modeldef.xml editor. Maybe it's a variable that FS2004 does not have.
 
The modeldef.xml editor is the original one: FS2004 CD (Gmax plugin folder). I've tried others, but I'm not sure which variable is correct. What is the current variable?
Thanks
 
When you load the FSX model it will show the variables as read from the MDL file, not those from the SDK.
 
I don’t believe that modeldef.xml is from FS9? It uses something like model.parts.xml. But you should use modeldef.xml since MCX uses that. But Arno is right, FS9 doesn’t understand all of those, but a large majority are OK.
 
Yes, MakeMDL.parts.xml is present in the FS9 SDK; it was a error in my previous post.
So, converting from FSX to FS9 removes the fan functionality, which is associated with the blur and fast textures; sometimes, when reloading the converted aircraft in MCX, these textures are missing. In short, it's a big problem.
 
It worked! I set the SDK as the attached images. The engines cowling textures are still in Blend Zero-One.
 

Attachments

  • zero one.jpg
    zero one.jpg
    9.6 KB · Views: 47
  • FSX_load mdl from FSX.jpg
    FSX_load mdl from FSX.jpg
    64 KB · Views: 33
  • blend.jpg
    blend.jpg
    15.2 KB · Views: 48
  • A320Neo_Iberia_FS9-ezgif.com-video-to-gif-converter.gif
    A320Neo_Iberia_FS9-ezgif.com-video-to-gif-converter.gif
    4.9 MB · Views: 51
  • 2026-07-28_144502.jpg
    2026-07-28_144502.jpg
    71.7 KB · Views: 36
I'm not exactly sure what all your screenshots show. The fact that you had errors loading the makrmdl parts.xml as shown by the res log entries , might indicate your xml file has some invalid entries.

But did I understand you correctly that you got it working now?
 
Yes, it works, meaning the A320neo is now acceptably flyable for me in FS9.
Even though there are errors when loading the model, the conversion yielded good results (in addition to the fans running, the taxi and landing lights are also working; only the left front door opens; for the others, I'll use a suitable gauge in the panel.cfg. Finally, it doesn't have wings view, but that's not a problem). My exhausting experiments end here.
Thanks for everything.
 
1785551865802.png


Im getting this error, or an asm error Arno. using latest mdlx v1.8 from the site. Using run as admin settings.
 
You need to use the latest development release (version 1.9) to have the unlimited export. With version 1.8 you can only export models with up to 65536 vertices.
 
You must log in or register to reply here.
Back
Top