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

MCX xtomdl error when using LODs

Rotornut44

Rotornut44

Resource contributor
Messages
671
Country
us-florida
@arno

For some strange reason, in the latest (and previous) dev version of MCX, if I add a LOD to an object, I get the below error when attempting to compile a FSX (or P3D) MDL file.

At first I thought it had something to do with the model, but if I remove all LODs, my model will compile correctly. If I even add as much as an empty LOD, I get the below error on MDL compile.

Further adding to the confusion, I just added LODs to a building model a day or two ago without any problems. Could this just be a bug or likely still something with my model?

mcx_lod_error.PNG



Edit: When attempting to compile a BGL from my MDL, Library Creator XML threw an error as well. So, something is messed up on my model, but I'm not sure what it could be. This isn't the first vegetation grouping I've made. I even have a texture setting preset setup for my vegetation models..
 
Last edited:
Do you have the decimal separator set to a comma (,) in your Windows Regional Settings? Sometimes this can be a problem. Try setting it to a period (.).
 
Looking at the MCX errors in the event log, one of the first lines states:
1:32 PM XtoMDL Error (0): error : System.Xml.XmlException: An error occurred while parsing EntityName. Line 2767, position 126.

Looking that line up in the generated XML file, I see:
<AnimationFileRef File = "F:\scenery\Emerald Object Library 2.0\LIBRARY PROJECT FILES\Vegetation\New Grass\Weeds&Wildflowers\fsx\_MCX_temp.xANIM">


Edit: The issue was hiding in plain sight. I used an "&" as a separator in one of the directories in the path. Replacing this character cleaned everything up.
 
Last edited:
Glad you found it. In all FS work, avoid any odd characters except the underline. Many compilers will crash.
 
XtoMDL is indeed very picky for special characters in the path, this is often the reason of weird crashes. Glad to hear you have solved it.
 
You must log in or register to reply here.
Back
Top