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

FSX Error exporting mdl object, need help please

L

lumat

Messages
342
Hello

I would like to export an object to mdl. This object was created for MSFS and I would like to export it in a Prepar3D format

To do that I use Blender 2.83 to import and rework the object (especially material and textures) to make it compatible FSX. I installed the plugin "Blender2P3DFSX" 0.98.21

I have FSX Steam with the Prepard SDK 1.4 (I tried before with FSX sdk, box version, with the same problem)
In the P3D/FSX file properties, I checked "Autodetect SDK", I generated a GUID and a friendly name.

I dont'understand why I've this problem. Apparently something to do with XtoMDL ....

I join a picture with the error

I thank you for help :)
 

Attachments

  • Export.jpg
    Export.jpg
    171.6 KB · Views: 208
It could be the period in your folder name (2.83), or it could be your path is too long. Or something else...
 
Xtomdl can be quite picky with characters or long paths indeed. Unfortunately the error you show is the blender error and not the error message from xtomdl itself.

What filename did you use for the mdl file?
 
Thanks

The name is LFBR_C_Ader, simply.

But yes sorry, it's a blender problem, not mcx.
I post on the blender forum
 
I have moved your question to the Blender forum now.

The file name should not be the issue. Do you export to a folder with special characters in the name? Do you have the decimal character set to dot on your machine?

I don't know if you can save the X file easily from Blender, then you could try to run XtoMDL manually.
 
That is not a blender error. It is referring to XtoMDL returned an error. Either the filename, including the path is to long or the folder names within the path have special characters within it.

What is the full pathname used?
 
It would be more useful if the Blender plugin would show the actual error that XtoMDL gave, instead of just saying it returned an error. The XtoMDL output usually gives a hint where the issue is.

Like Doug says, long paths, special characters in the path or even special characters in the name you set for the object can all cause XtoMDL errors.
 
I've made a simple object to try. I can't export in mdl format from Blender. The export in the x format seem to work.
MCX can load the x object properly.
But problem : Like Blender, MCX can't export it in the mdl format. Always a problem with XtoMDL it seem
I attach the folder, if you have the time to take a look
Thank again for your help :)

NB : I use Blender 2.83.16 with the toolset 0.98.21
 

Attachments

Last edited:
What kind of error do you get when you export with MCX?
 
Hello.
Ok it seem that the name of the folder is the cause of the problem.
I tried to move the files in a new folder but at the root of the disk and all seem to work.
Maybe a path too long ?

Strange. I never had this problem before. Maybe the new toolset with Blendezr 2.83.16 ?

EDIT : I think it's due to a folder with a name containing a "é" instead of a "e". I never name the folders with that !!! Sorry :)
 
Last edited:
Yes, like we said xtomdl is very picky for special characters, so a é in your path can surely give an error.
 
No problem. This happens very often. I wonder why Microsoft made xtomdl such that it throws an error in that situation. But that's not something we can change.
 
You must log in or register to reply here.
Back
Top