FSX:SE Blender woes

[virtualpilot1460]

I've spent most of the day trying to get to the bottom of this issue........ Exporting to a .x file is OK but cannot produce .mdl file this is the error I keep getting and I have tried the infamous decimal point fix to no success


Traceback (most recent call last):
File "C:\Users\natha\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Blender2P3DFSX\func_export.py", line 351, in Export
spawnv(P_WAIT, XToMdl, ['XToMdl.exe', additional, '"%s"' % (Util.ReplaceFileNameExt(self.config.filepath, '.x'))])
OSError: [Errno 0] Error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Users\natha\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Blender2P3DFSX\ui_export.py", line 204, in execute
Exporter.Export()
File "C:\Users\natha\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Blender2P3DFSX\func_export.py", line 357, in Export
raise ExportError("Export to .MDL failed. XToMdl.exe returned an error.")
Blender2P3DFSX.li_export.ExportError: Export to .MDL failed. XToMdl.exe returned an error.

location: <unknown location>:-1


Would appreciate a Guru's help

Cheers

 

[Pyscen]

Hello...

This is the 2nd time in seeing this OS Error but not me personally. It is really hard to determine what is causing this error, without seeing the blend file. What SDK are using for Blender and FSX: SE?

Is there a reason why you haven't updated to LTS V2.93?

 

[virtualpilot1460]

I'm using SDK version 1.2 and didn't think the tool set would work with 2.9

Sent from my Pixel 6 Pro using Tapatalk

 

[Ronald]

Here's my viewpoint on this error, seen from a more computer-admin related viewpoint:
When looking at this error: ['XToMdl.exe', additional, '"%s"' % (Util.ReplaceFileNameExt(self.config.filepath, '.x'))]) OSError: [Errno 0] Error

{EDIT:} Added the above Python source-code fragment, around which line your error occurs

1a. Could this error possibly be caused by an Operating_System level / File_Systems level access_rights issue? (and not an internal Blender export script flaw?)

EDIT:1b. Did you [Initialize the toolkit] properly - before - attempting to export your model?
Why? If this is not done, the export script does not know where to look for the XToMdl.exe file and is able to crash on this error.


2. Have you tried the following work-around / trouble-shootings approaches already:
2a - Start all applications with the [Run-As-Administrator] option from the start?
This solves "the not-having-enough-file_system right issues", since administrator_level login accounts should (by default) be able to save everywhere on the computer they can login too.

2b - Tried to save your Blender exported .X-file to a location (for example your Windows Desktop) where you know for 100% sure that you can create / add / delete / modify all files there?
If the Blender export script can not create a new file and/or modify an existing file (due right_issues), this can crash the export script.

2c - Get the .X-file imported / converted manually without the use of the Blender Python based export script?
- So save your Blender project file in native blender format first (to have a backup).
- Then export your Blender project file out of Blender first - into - for example a folder on your Windows Desktop
- Exit Blender.
- Go to the Windows commandline and manually import your Blender-exported file into XtoMdle.exe via its commandline options?

2c.1 - How to find the location of XToMdl.exe on your own computer from the Windows(10) commandline

2c.2 - How to show the available options of XToMdl.exe from the Windows(10) commandline.

3 - Also take a look at the FsDeveloper Wiki for more background on XToMdl.exe over here:
-https://www.fsdeveloper.com/wiki/index.php/XtoMDL

Why? This manually import approach enables you:
- to see at the Windows commandline_level: possible error(s) generated by XToMdl.exe, which do not might get processed correctly by the Blender export Python script
- to determine what is the /root cause of this export challenge can be:
-- an internal Blender Python level export script error
-- an external XToMdl.exe iput error
-- option 3,4, n


4. Have you manually been able to check if the Blender exported .X-file is 100% good of got corrupted somehow?
// I do not (yet) know any commandline methods or tools to help you with this process.
Since... If the Blender into .X-file export got corrupted, the XToMdl.exe tool can simple choke on it and refuse to further process its given input file

I hope my insights can help you to determine: Where, What goes wrong and Why.

 

[virtualpilot1460]

all the above has been done and still having issues - I'm stumped completely (going to try 3ds Max) but I'd rather use blender. I swear the hanger I'm building is going to be the death of me

 

[Ronald]

all the above has been done and still having issues

This line above alone is not very usefull if you want others to assist you in any way.
1. With who or what (else)? What kind of error_messages from which (other) programs do you encounter currently?

I'm stumped completely (going to try 3ds Max) but I'd rather use blender.

I swear the hanger I'm building is going to be the death of me

2. Sometime - when getting stuck - It can also very help-full to start from scratch again.

3. TIP: Start (very) simple first, Learn the Blender Basis and then work your way up to your hanger.
-

..
-

..
-

..
-

..
-

 

[virtualpilot1460]

The eorror is the same as at the top I will try again my laptop later today

Sent from my Pixel 6 Pro using Tapatalk