• 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 Model fails to compile

euroastar350

Resource contributor
Messages
863
Country
us-delaware
Hi guys,

I've ran into a small issue, hoping I can get it fixed. A couple days ago, my current project has been exporting and compiling fine with animations. Last night, I went to compile my latest changes and my model fails to compile.

I am suspecting it's the modeldef as I added new animation and visibility scripts for the overhead buttons and switches.

If it helps, all visibility scripts sit right on top of the stock EH101 animation scripts, while the custom scripts are added right above the visibilty scripts.

Any ideas on what's causing this not to compile?
 
Hi
Right click on the modeldef.xml file then "open with" and select a internet browser.....if there are any errors in your additions they will shop up in the browser..its a basic check but can be helpful tracking down errors..if the file opens and list all the code in the modeldef you can move on to find issues in the modeling program like remove the parts one at a time or grouped till you find the offending part
 
If you have setup to have a log file created, then it should tell you something.

Also, to test the modeldef, open up one of the tools, like animation manager or attach tool. If the code is really bad, these tools should not open, or have a major malfunction.

Make sure also you do not have too many polygons or parts using a single material. I cannot remember the limit, but having too many small parts on a main material will also cause this.

That log is your best bet. If you are using the DOS route, you can create a BAT file and that will auto-generate a log each time you export a model.

Here is a BAT file, but you would need to enter the names of your two files, plus the address location of the SDK on your drive;


COPY/////////////////////////////////////////////////

rem Move this file to C:\Program Files (x86)\Lockheed Martin\Prepar3D SDK 1.4.4747.0\Environment Kit\Modeling SDK\3DSM2012\Plugins\
rem Move LJ.x and LJ.xanim to same location.
rem Execute this file.
XtoMdl /XANIM /DICT:..\..\bin\modeldef.xml LJ.x > LJ.log
XtoMdl /XANIM /DICT:..\..\bin\modeldef.xml LJ_Interior.x > LJ_Interior.log
pause

END COPY///////////////////////////////////////////

Convert this to a TXT, then rename the text BAT, and put it in the folder where your XtoMDL.exe compiler is. Drop the MDL's in there and click this and it should make a LOG for you to check out.




Bill
 
I managed to get it working again. Turns out, the scripts cannot be too spaced out from each other or else it won't compile, well on my end at least.
 
Does not matter where you add your scripts in the modeldef as long as you have the GUIDS above and xml below.
What i think is causing your issue to export is the model is getting heavy and you need to restart your program when
you plan on exporting the entire scene. When i have a large scene and i have been working 2 hours, it needs a restart before exporting.

Some days your scene is different with wire frame to no wire frame in random windows. So a good trick is to just hide all parts
save project reload Gmax then export entire scene. This gives you more free memory to compile a large scene.:idea:
 
Back
Top