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

XtoMDL problem

S

Syltremb

Messages
9
Country
ca-quebec
HI

I have this message when I compile a .x to .mdl :

Code: 
(0): error : XToMdl.exe Unhandled Application Exception
(0): error : System.FormatException: Le Guid doit contenir 32 chiffres et 4 tire
ts (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
(0): error :    à System.Guid..ctor(String g)
(0): error :    à Microsoft.FlightSimulator.XmlToMdlLib.MDLProcessor.ProcessXmlS
tartElement()
(0): error :    à Microsoft.FlightSimulator.XmlToMdlLib.MDLProcessor.LoadFile(St
ream InputStream, XPartDict PartDictionary)
(0): error :    à Microsoft.FlightSimulator.XmlToMdlLib.XmlToMdlLib.Process(Guid
& ModelGuid, Stream AnimationData)
(0): error :    à Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInputs()
(0): error :    à Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(String[] args
)
(0): error :    à Microsoft.FlightSimulator.XToMDL.XToMDL.Main(String[] args)
(0): error :
Someone can tell me what it the cause of this ?

Thank all

Sylvain
 
Hi Sylvain,

My French is quite bad, but I think it says your GUID is not in the correct format. It needs to contain four dashes and the brackets.
 
Thank Arno

This message appear when I use XtoMDL.exe in a windows DOS mode. When I drop the file on it, the MDL are create without any error message.
I want to use the window Dos mode because I want to use the tag /XANIM for exporting an animation.

Can you help me ?


Thank


Sylvain
 
Why not look into the cause of the problem and see if you assigned the GUID correctly?

Also are you sure that when dropping the file on XtoMDL that you do get a valud MDL file (and not one of 0 kB in size).
 
Hi Arno

I Assign the GUID correctly in 3dsmax and when I dropping the file I have a valid mdl.

Thank for your answer.

I use scenecomp.exe and it work perfectly too. I continue to use it and I found it take consideration of .xanim on the conversion.

Thank for take time to answer to me.


Bye


Sylvain
 
I'm afraid I also ran into an xtomdl error.

I used xtomdl extensively in the last months but all of a sudden I get the attached message today - with all my previously working x-files. :(
 

Attachments

  • xtomdl1.jpg
    xtomdl1.jpg
    97.4 KB · Views: 577
Could it be that the update of the SDK has anything to do with this?
 
I thought so too. But DirectX? What has directX to do with SP1? And by the way: with the betas of SP1 it worked, this was the first time I used xtomdl since I installed the rtw of sp1.

Noone any idea? :(
 
Hi Thorsten,
it's only an idea, perhaps it works. Run the "ConfigSDK.exe" again and try it again.
 
No success with that. I sure seems to be a directX-issue. Why else should it be stated in the error message?

Anyone a direct-x-expert? :D
 
And it works again! :)

I reinstalled the latest update for DirecctX 9.0c and it works.
Don't ask why cause I used 9.0c before and didn't change anything on my pc (apart from installing SP1 rtw), but the error vanished. :)
 
You must log in or register to reply here.
Back
Top