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

ACK! XTOMDL compilation problems

Messages
20
Country
us-texas
Hi all! Running into some problems compiling.

My system:
Vista x32
3D Max 9
FSX Acceleration

I can create the x file and view it with the DirectX viewer (Nov 2007 DirectX SDK)

problem is XtoMDL....


Here is the shortcut target I am using: ( Have xtomdl.exe and modeldef.xml in the C:\Build folder)

%windir%\system32\cmd.exe /K c:\BUILD\xtomdl.exe /DICT:c:\BUILD\modeldef.XML /XANIM
here is the error I get:


Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl
y 'XToMdl, Version=10.0.61637.0, Culture=neutral, PublicKeyToken=31bf3856ad364e3
5' or one of its dependencies. Strong name validation failed. (Exception from HR
ESULT: 0x8013141A)
File name: 'XToMdl, Version=10.0.61637.0, Culture=neutral, PublicKeyToken=31bf38
56ad364e35' ---> System.Security.SecurityException: Strong name validation faile
d. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was:
MyComputer




Anyone seen this issue??:eek:
 
Last edited:
Hi,

The error is a bit cryptic, but it sounds like some security problem. Could it be that there is some network drive or so involved?
 
Not sure about vista or if this will fix it, but on XP its
Control Panel/Administrative Tools/Microsoft .Net 2.0 Configuration

Click on Configure Code Access Security Policy
Then on Adjust Zone Security

"My Computer" zone should already be at full trust, but it may be worth increasing intranet to full trust too.
 
I am using XP Pro, and am having the same problem when trying to export anything. It sucks so much! I am stuck, I tried the above fix, but they were already on full trust. I don't know what else to do!
 
Here is the shortcut target I am using: ( Have xtomdl.exe and modeldef.xml in the C:\Build folder)

%windir%\system32\cmd.exe /K c:\BUILD\xtomdl.exe /DICT:c:\BUILD\modeldef.XML /XANIM

Unless you've manually changed a bunch of Registry entries and .ini files, you should NOT move either the xtomdl.exe or modeldef.xml files from their precise locations in the installed SDK path.

There are other - internal - dependencies coded in xtomdl.exe that require that it remain where the Registry thinks it is, otherwise you will encounter occasional odd problems.
 
Negative. Still doesn't work.
Even if i open up cmd, then cd to the folder in which XToMdl.exe is in in the SDK folders, it gives the error.
 
Last edited:
Hey whatdo you know, the XToMdl in the 3dsmax7 work fine... I wonder why the 3dsmax9 version is broken...
 
Hi,

I have also seen this, from the command prompt the GMax and 3DS7 version work. But the 3DS9 one seems not to work standalone.
 
Hey whatdo you know, the XToMdl in the 3dsmax7 work fine... I wonder why the 3dsmax9 version is broken...

Actually, there should be no difference whatsoever between the two instances of XtoMDL.exe at all!

Aside from the .ms scripts files, the only other difference is be the Max9_FSModelExp.dle export module... :eek:

Ah! I see the difference now. Both versions of XtoMDL.exe are v10.0.61637.0 but...

...ACES forgot to Digitally Sign the Max9 copy of the program! :censored:

Without the Digital Signature, Vista32 is treating it as a "threat..." :tongue-ti
 
Ah! I see the difference now. Both versions of XtoMDL.exe are v10.0.61637.0 but...

...ACES forgot to Digitally Sign the Max9 copy of the program! :censored:

Without the Digital Signature, Vista32 is treating it as a "threat..." :tongue-ti

Ah, that would explain it, good catch. I was a bit surprised already that XtoMDL was different (file size also is). I guess a solution would be to just copy over the other one, as they should be the same anyway.
 
Back
Top