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

Exporting issues

When I compile the model and open it in sim the model is there, but the animations are frozen. Like how the animations are 0-100 key frames, they are all stuck in the 0 key frame. I only know that there is a duplicate animation because when I open it in MCX there are two animation tags for each animation instead of one single one.
 
I always have multiple entries for the same animation in MCX, no matter whether it's a FS9 or FSX model.
 
It just occurred to me that all the duplicates for an animation which are shown in MCX instances of rotation and translation animations for an animated part. If you import a model into MCX that has, e.g. three parts that use c_gear and each part has rotation and animation type keyframes assigned (regardless of whether they actually translate or rotate), you will end up with six instances for c_gear in MCX' animation manager.
So if you want to cut down the list of duplicate animations, only assign keyframe types that are actually used by the part.
 
It just occurred to me that all the duplicates for an animation which are shown in MCX instances of rotation and translation animations for an animated part. If you import a model into MCX that has, e.g. three parts that use c_gear and each part has rotation and animation type keyframes assigned (regardless of whether they actually translate or rotate), you will end up with six instances for c_gear in MCX' animation manager.
So if you want to cut down the list of duplicate animations, only assign keyframe types that are actually used by the part.
The OP has not posted the fix for some reason. It turned out to be caused by the Mirror Modifier.
 
Back
Top