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

.X and .XAnim

Osian

Resource contributor
Messages
417
Country
netherlands
Hello everyone,

I want to export my airplane from blender to FSX and I have a problem.
When I export it I get two files .X and .XAnim now I know that i have to use XTOMDL.exe and I tried with this UI version I found here and when exporting the /Anim tag active but when I open the model in FS or Modelconverterx there are no animations on my plane.
I've used the proper tags in blender and followed multiple tutorials but I cant get it right.

Please help
Thanks in advance.
 
No, you do not need to use XtoMDL since the Blender2FSX toolset can export to MDL directly.
 
I know I can export MDL's directly but i get this error and even though I read a lot of tutorials and watch some tutorials on YouTube I can't fix it
But I want to learn so :P
 

Attachments

  • 1b832ed7dcc38a9e0addad0232ee3dac.png
    1b832ed7dcc38a9e0addad0232ee3dac.png
    85.4 KB · Views: 670
It is the same one as I got, and still no solution (I have tried a lot of things with Dutcheeseblend).
Do you have Windows 8?
 
Have you installed the FSX SDK?
Have you initiated the toolset?
Have you tried it with a simple cube?
 
On all your questions the answer is yes.
With a simple cube I have the same error :\
 
What is the specific error you are getting please? I'm not asking about the error above,... I'm talking about Xtomdl error.
 
I have placed a screenshot in a post earlier.
 
Last edited:
It appears that the path for the file is not correct or the file doesn't have write permissions. Goto the location of file and right-click... Click on properties tab... Look for read and write permissions
 
Which version of 2.75? There are 2.... a and b... There are 2 versions of 2.76 as well now... Which version @Osian are you using?
 
For reference you can drag and drop the x file onto a shortcut to xtomdl if you do the following:

Make a windows shortcut to xtomdl.

Right click on the shortcut and select target and add something like the following:

"C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\XToMdl.exe" /XANIM /DICT:modeldef.xml /NOCRASH /BMP2DDS

The modeldef.xml needs to be in the same folder as xtomdl. You can change the locations of these if you like.

/XANIM tells xtomdl to use the .xanim file

/NOCRASH stops making a crash box, you should remove this for aircraft.

/BMP2DDS changes any references to BMP to DDS

Now all you need to do is drag and drop the .x file onto the shortcut and oingo boingo xtomdl will take the .x and .xanim and modeldel.xml files and make you a .MDL file and put it in te same folder as the .x file.
 
I FIXED IT !!!! ahaha the .XANIM file was names wrong by Blender and is was called TU334.x.xanim i had to remove the .x part.

Thanks guys
 
Ok... That sounds like a bug in the blender2Fsx then. If so... We need to verify that.
 
Back
Top