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

FS2004 Retrieving code for custom anim, visibility from MDL

Kekelekou

Kekelekou

Resource contributor
Messages
226
Country
france
Hello,

I am contemplating converting Nemeth Design's Ka-26 and Mi-2 VC from FS9 to FSX, but these models make use of custom anims and mouse rects for several switches.
Just like ModelConverterX gives the opportunity to retrieve the codes for custom anims, visibility conditions and mouse rects in the Modeldef.xml visualisator, is there any way to get the same data from a FS9 MDL?

Thanks in advance!
 
I have the source files for the KA26 and MI2 sent to me by Tamas for FSX conversion. I have the exterior and interior already in FSX with switch codes and other animations only left to do for both interiors. Basically the custom animations ares based on the provided 2D gauges which can be translated into 3D code.
KA26.jpg
MI2.jpg
 
If you load a FS9 model in MCX, one of the first items sent by MDL9Reader into the log console at the bottom will be things like:
23:05 MDL9Reader Warning Failed to find animation name for parameters #100#(A:TURB ENG2 REVERSE NOZZLE PERCENT, percent) 1 > if{ 100 } els{ 0 }
Click to expand...

This only contains animation code though. Right clicking the entry will copy the message's content to the clipboard. All that needs to be done then is turning the code into a new animation tag for use in the Modeldef.
Since switch animations are also parsed, you can at least find out what L: var is used by the switches.
 
Thank you, I’ll give it a try. MCX features are truely impressive.

Euroastar350 : these two birds look really good in FSX. I’d be glad to guve you a mittle help, but with no commitment on any timeschdule : my DamageMod for the BN-2 has to be finished first.
 
It's still on my wishlist to let MCX convert between FS2004 and FSX animation definitions, so that they can be mapped automatically. But lack of time has prevented real progress on this until now.
 
arno said:
It's still on my wishlist to let MCX convert between FS2004 and FSX animation definitions, so that they can be mapped automatically. But lack of time has prevented real progress on this until now.
Click to expand...

This is possible?

What about generating a Makemdl.xml from a FS9 model file for a start, just as can be done with the Modeldef.xml.

Are mouse rectangles and visbilities retrievable from model files? That's kind of the biggest hindrance when trying to convert models.
 
Hi,

It's some time ago I looked at it, but extracting the mouse rectangle and animations should be well possible. My idea is to store it in the internal modeldef.xml. On export to FS2004 it would have to be saved as makemdl.xml.
 
arno said:
It's some time ago I looked at it, but extracting the mouse rectangle and animations should be well possible. My idea is to store it in the internal modeldef.xml. On export to FS2004 it would have to be saved as makemdl.xml.
Click to expand...

If you can convert them directly, it would be even better.
 
Heretic said:
If you can convert them directly, it would be even better.
Click to expand...
Yes, the idea is to convert on import. Try to find a matching animation or else create a new one.
 
Whaaa, that would be fanstastic. But it would also take all the fun out of it. :duck:

A modeldef.xml-like file with all animation, mouserect and visibility code would be just great, and maybe quicker to develop.

Thanks as always for your consideration toward our requests and comments Arno
 
You must log in or register to reply here.
Back
Top