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

FSXA FS9 to FSX Conversion : Using MCX event log to update animations

Kekelekou

Resource contributor
Messages
226
Country
france
Hello,

Following my issues with a FS9 port-over, I am trying to use the AI method to convert the MDL to the FSX standard.
I open the FS9 mdl, then export it as a FSX mdl.
The eventlog shows several failures :

15:49 XtoMDL Information CRASHTREE completed in 00:00:00.0849609
15:49 XtoMDL Information <!-- ++++ Processing Animation : lever_stick_fore_aft ++++ -->
15:49 XtoMDL Information <!-- ++++ Processing Animation : Ambient ++++ -->
15:49 XtoMDL Information <!-- ++++ Processing Animation : c_gear ++++ -->
15:49 XtoMDL Information <!-- ++++ Processing Animation : elevator ++++ -->
15:49 XtoMDL Information error :
15:49 XtoMDL Information error : Failed processing animation file!!
15:49 XtoMDL Information error :
15:49 XtoMDL Information error : System.FormatException: Le Guid doit contenir 32 chiffres et 4 tirets (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). //GUID IS 32 DIGITS AND 4 DASHES ONLY
15:49 XtoMDL Information error : … System.Guid..ctor(String g)
15:49 XtoMDL Information error : … Microsoft.FlightSimulator.XAnimToAnimLib.FileExporter.WriteGuid(String S)
15:49 XtoMDL Information error : … Microsoft.FlightSimulator.XAnimToAnimLib.ANIMProcessor.WriteGUID(String GUID)
15:49 XtoMDL Information error : … Microsoft.FlightSimulator.XAnimToAnimLib.ANIMProcessor.WriteANIM(XmlNode node)
15:49 XtoMDL Information error : … Microsoft.FlightSimulator.XAnimToAnimLib.ANIMProcessor.WriteANIMLib(XmlNode node)
15:49 XtoMDL Information error : … Microsoft.FlightSimulator.XAnimToAnimLib.ANIMProcessor.GenerateOutput(FileExporter Exporter)
15:49 XtoMDL Information error : … Microsoft.FlightSimulator.XAnimToAnimLib.XAnimToAnimLib.Process(Stream OutputStream)
15:49 MDLXWriter Information Finished writing of file X:\FSX\SimObjects\Airplanes\....MDL

Are the 4 processed animations failed? Are they the ones for which I have to add the bits in the modeldef.xml? Is the error only related to the GUID format? How to work my way to the GUID to correct it? (I have tried to edit the GUID in the Object Info, to no avail).

Thanks for undestanding these noob questions.
 
Last edited:
The GUID seems to be in an incorrect format.

GUIDs in the modeldef's animation headers have to look like this (32 characters and 4 dashes):
Code:
guid="625fe63a-b27c-4a6c-ad18-cec4c4054f2d"
 
Thanks for your help Heretic! I had a look at the GUIDs in the modeldef.xml to look for a typo, but I couldn't find the "elevator" animation tag. I have added the elevator code you posted in your "AI FS9 convertion" thread, retried to export, and now "elevator animation" can be processed. But I still got a "information error" with another animation, which is just below elevator in MCX animation editor's list.

From what I have inferred :
The animations are processed in the order they appear in the animation editor in MDX.
If an animation is not assigned/built correctly, the the "XtoMDL information error" line will appear just after the "<processing animation : faulty animation>" line.
A bit tedious, but now you know what to work on.

Is there an easier way to know which animations are not assigned?

Edit : Rewriting of the post...
 
Last edited:
Cross-check the animations listed in the Animation Editor with the ones listed in MCX' output log.
 
Will try it tonight, thanks again. And I have just figured out than I should use MCX development release. Yes, I know I am a low-watt bulb :laughing:
 
Heretic you are the man! I have managed to run a FSX native version thanks to your tutorial, your thread and your help (thx to Arno for the MCX too)!
Still many things to fix, but modelling is such a blast! THANK YOU
 
Just as an after note, the stock elevator code has a left and right. Maybe that's why you couldn't find it.
 
I'll look at the modeldef.xml for these two elevator codes Paul. Thanks for sharing.
 
Back
Top