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

compile errors

S

Straw

Messages
5
hey all
having a bit of trouble compiling with xtomdl thru fsds 3.5
tried low an high polly models as well as a simple object i get the following log


OutputFile: _temp.MDL
Output file after modification: _temp.MDL
Creating output MDL file: _temp.MDL
(0): error : XToMdl.exe Unhandled Application Exception
(0): error : System.IO.FileLoadException: Could not load file or assembly 'Managed_CrashTree, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

(0): error : File name: 'Managed_CrashTree, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.IO.FileLoadException: Could not load file or assembly 'Managed_CrashTree, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

(0): error : File name: 'Managed_CrashTree, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

(0): error :

(0): error : WRN: Assembly binding logging is turned OFF.

(0): error : To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

(0): error : Note: There is some performance penalty associated with assembly bind failure logging.

(0): error : To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

(0): error :

(0): error : at Microsoft.FlightSimulator.XToXmlLib.ModelProcessingContext.BuildCrashTree()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.ModelProcessingContext.Optimize()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.ProcessAllFiles()

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInputs()

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(String[] args)

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.Main(String[] args)

(0): error :

(0): error :
(0): error :
(0): error : Could not load file or assembly 'Managed_CrashTree, Version=10.0.60905.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
(0): error :
(0): error : Stack Trace:
(0): error : at Microsoft.FlightSimulator.XToXmlLib.ModelProcessingContext.BuildCrashTree()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.ModelProcessingContext.Optimize()

(0): error : at Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.ProcessAllFiles()

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInputs()

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(String[] args)

(0): error : at Microsoft.FlightSimulator.XToMDL.XToMDL.Main(String[] args)


Now im running a fresh install of FSX Acc with the correct sdk, using xtomdl.exe,mdlscan.exe from 3dsm7 in lu of 9.
net framework is 2.0,zone securities set to full trust,logged on as administrator and regional settings set to dot.
objects compile but byte size of mdl is zero i get no errors during compile but log shows its gone south.

when using 3dsmax 2008 i get this

unable to open the file named 'C:\Documents and Settings\Owner'. it may be locked

then notification of mdl failure


im hearby open to sugestions as my brain is about ready for a defrag


regards
Straw
 
Hi
Ok at least its not a vista thing
Have you installed any of the sdk's or fsds in a non default location or folder?
Have a look in the root folder of fsds3.5 for CreateMdl.bat
right click on it then edit and cut and paste the contents here.
cheers
Wozza
 
the notepad file after edit is blank nothin to paste.
the sdk installation is in the default location nothing has changed i first installed fsx then the sdk off disc 1 then installed accelration then sdk updates off accelration, then copied the xtomdl.exe an the mdlscan.exe from the 3dsm7 to the 9 plugins folder my installation of 3dsmax 2008 would ctd if using the 9 exe's
when launching fsds 3.5 i had to direct it to the 3dsm9 folder for the xtomdl.exe followed by the bgl comp as well as the model def.xml all the paths are still the same.

i did notice that the file size for the create mdl bat file is 0 is this normal?


regards
Straw
 
Last edited:
Hi
Nope thats not normal the file should look something like this (only if your compiling for FSX)

"C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\XToMdl.exe" _temp.x /keep /xanim /dict:"C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\modeldef.xml"
"C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\XToMdl.exe" _temp_interior.x /keep /xanim /dict:"C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\modeldef.xml"
copy _temp.mdl "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\T-6\Model\t-6.mdl"
copy _temp_interior.mdl "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\T-6\Model\t-6_interior.mdl"

:)
looks like some config is wrong maybe inside fsds...are you compiling for FS9 or FSX?
run fsds and check the compile options are set up correctly for the sim your compiling for and make sure all the paths are correct.
Cheers
Wozza
 
Last edited:
No no you dont get of that lightly :)
tell us what you did to fix it
:D
Just in case somebody else has a similar prob they can search and try before they post;)
Cheers
Wozza
 
Quite frankly, I found the entire exchange rather confusing...

He's talking about Max9 and FSDS at the same time... :rolleyes:
 
Ok guys ill try an clarify i have fsds 3.51 as well as 3dsmax 2008 both have given me errors.
im runnin fsx acceleration updated the sdk to the latest version that were on the disk.
Both programs failed to compile via the xtomdl.exe,mdl scan.exe in the 3dsm9 folder after the sdk updates,so i copied the signed ones from 3dsm7 to the 3dsm 9 folder 3dsmax 2008 found everything right off an i directed fsds to the 3dsm9 folder with the 3dsm7 executables.
This setup gave me no joy.
Ive since corrected the path in fsds as follows

"C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\3DSM7\Plugins\XToMdl.exe"

With this path xtomdl does compile a mdl thru fsds with a file size now,
As for using 3dsmax 2008 i have stopped trying to compile via the export menu by selecting flightsim model(*mdl) option.
Ijust export the xfile xanim and run xtomdl via commandline an an wada ya know it works.

i couldn't have done it without the help of you guys here on FSDeveloper your the greatest.

Straw
 
FelixFFDS said:
So, the MAx9 gamepack at fault (again)
Click to expand...

But that is no news anymore, these EXE files are not signed and that will remain the case for a file. It's a pity MS does not fix this, as it gives a lot of frustration.
 
arno said:
But that is no news anymore, these EXE files are not signed and that will remain the case for a file. It's a pity MS does not fix this, as it gives a lot of frustration.
Click to expand...

Arno - Maybe we should start a list of FS-X modelling absolutes:"

I. Max9 - Thou shalt banish the Max9 gamepack/tools to oblivion, and use the Max7/8 tools given.

II. gmax - Thou shalt not use the mirror tool to mirror a part that will end up in the model. Thou shalt apply a mirror modifier instead.

etc....
 
You must log in or register to reply here.
Back
Top