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

Visibility tags breaking animations - solution!

Deano1973

Deano1973

Resource contributor
Messages
384
Country
unitedkingdom
Hi folks,

While working in Blender, using Blender2FSX, I came across a solution to an oft-found problem where adding visibility conditions ( in my case, weapons and their pylons ) would break animations ( in my case, the catapult launch bar ).

In brief, the solution was that all visibility-conditioned objects were required to be parented - once this was done, the launch bar once again animated without issue. I have no idea why this would happen and can only assume it is some kind of minor bug. Interestingly, visibility-controlled tie-down chains did not affect the launch bar.

I parented the weapons to the pylons, and the pylons to the wings ( each had differing visibility conditions; pylon visibility, and individual weapon visibilities depending on type ). Problem solved.

While this will not assist in ModelConverterX conversions of older airplanes ( which requires re-importing to overcome the issue ) I thought it worth sharing here to avoid further hair-pulling for folks on future projects :)
 
Often animated parts need to be parented as well to work properly. MCX usually does this automatically.
 
You must log in or register to reply here.
Back
Top