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

Error with ToolSetFSX and Blender 2.76

  • Thread starter Thread starter l52
  • Start date Start date
L

l52

Messages
125
Hi,

I have a problem about export function in Blender for FSX.

When I export my object for FSX, from Blender 2.76-rc1-win64.msi version, and tick in MDL format option, I get this error:


Error_MDL_Export.png


I use toolset Blender2FSX_084 (But the Problem occurs with Blender2FSX_0703 also)

Otherwise with Blender Vers. 2.75a , if I export the same file with the same option engaged, it’s all ok.



Can you help me?



thanks

L52
 
Hello again,
Blender error messages are hard to understand as we see, so the only way is to work the checklist:

1. Does each object have a material?
2. Does the model have a guid and a friendly name?
3. Is the toolst initialized?

Hope this helps.

Dave
 
Yep, this is the correct troubleshooting. Also, try to export a simple cube for example.

What I understand of your error message (just my interpretation), is that the .x file can't be found.
 
dave hoeffgen said:
Hello again,
Blender error messages are hard to understand as we see, so the only way is to work the checklist:

1. Does each object have a material?
2. Does the model have a guid and a friendly name?
3. Is the toolst initialized?

Hope this helps.

Dave
Click to expand...
1. yes;
2. yes;
3. yes;

Dutcheeseblend said:
Yep, this is the correct troubleshooting. Also, try to export a simple cube for example.

What I understand of your error message (just my interpretation), is that the .x file can't be found.
Click to expand...

...

Do you use Blender 2.76 version? I get error only when I export the object with the MDL option engaged ... If I export only as .x format it's all ok
Whit Blender 2.75 it's all ok (MDL and .x format)
 
I don't use 2.76 yet. If this problem persists, I recommend to stick to 2.75 for the time being.
 
Thanks.


anyway, at this time, I go back to using Blender 2.75 .... waiting for the final version of Blender 2.76
 
I'm getting this error as well. In looking closer at the text of the error report, I noticed that the expected name of the MDL that's being exported (when export MDL is selected) is "[modelname].x.MDL - note the inclusion of the ".x" before .MDL. Curiously, even though this error is thrown, a correctly named MDL is actually exported, with what seems to be the correct file size. I tried exporting a ground poly that I had recently done in Blender 2.75 and when I tried to open the resulting MDL in MCX, it couldn't find any of the textures used. It seems that they too had been incorrectly named. If, for instance, I had used a texture called "myTex_01.tga" in Blender, the file that MCX was looking for was now "myTex_01.tga.dds". Again, rather than giving the textures the correct extension, it simply appended the extension onto the full existing file name.

Does that help as far as troubleshooting goes?
 
Hi all,
I have recently switched from Blender 2.74 to 2.77 and I too have started encountering the above problem and also noticed the issue with the added extension to the texture files as mentioned by Bill. I don't know if anyone has solved this but I actually managed to find a workaround for the texture issue since it can be a pain having to rename the texture files again in MCX especially if you've got quite a few.
So what I did I had a look into the plugin file export_fsx.py. which you can open with notepad just to see what could be causing the issue. Mind you I have no experience with python at all. Just search for the text "dds" in the file export_fsx.py and delete the word dds. Leave the inverted commas there and save it. I also left a space between them. Make sure you close and open blender when you make the changes to the file before trying it out. Try to export something and hopefully this should solve the issue with the double extension.
I suggest making a copy of the export_fsx.py file before doing the changes just in case.

Just a small correction, this will only work if in blender you use either bmp or dds textures.

Regards
Daniel
 
Last edited:
You must log in or register to reply here.
Back
Top