Decals (Animated) Produce Duplicate Static Mesh Visuals

Version:
1.5.1.0

Frequency:
Consistently

Severity:
Blocker

Similar MSFS 2020 issue:
None

Bug description:
Animated decals in MSFS 2024 seem to create a “duplicate” decal mesh of some sort, as if there are multiple instances of the mesh model, when there are not. For example; with an animated decal over the front cargo door, when the door is opened, the decal animates with the door just fine — however, the sim seems to yield a second “duplicate” of said decal that does not animate with the door.

Photos below attached from my decal livery for reference;







And photos below attached from the default CJ4 livery for reference;


Aside from my livery and the default CJ4 livery, this behavior is exhibited across a multitude of other default aircraft in MSFS 2024… After consulting elsewhere, someone mentioned the following;

I had this same issue and it took me the longest time to figure it out. I had a livery decal model that was only for model.airframe but inside the airframe attachment, I had multiple models in the same directory. In that case, the livery model was applied to each of the sub models. To fix it, I just separated each model into it’s own directory and each one has an attachment.cfg with unique tags.

Your problem might be different but inspect all your tags and consider if the livery stripes can get duplicated onto more than one attachment model.

Considering this, I went and dug through the CJ4 in the VFS and found that while there were no instances of multiple different models within a single part.xxx of the relative parts, there were instances in which different parts shared the same tag, such as part_exterior_fuselage and part_exterior_dirt, which share the fuselage tag. Granted, I am not sure if this is the root cause here or not, but nonetheless, this issue has been present since the launch of MSFS 2024 and is a blocker for animated decals, both in third party applications, and in default core-sim aircraft applications.

What the fix is, I’m not sure, but undoubtedly a fix or alternate workflow would resolve this across the host of default aircraft/default liveries that exhibit this issue.

Repro steps:
Repro Option 1

  • Create a mesh livery/decal, parent it to the base-aircraft’s animation empty for that node, and view in sim.

Repro Option 2

  • Look at either my example decal livery (file attached below), or look at the default CJ4 blue stripes livery in sim.

DevSupport Decal Example.zip (10.4 MB)

If you need any further clarification, please let me know.

Thank you,
Zach

1 Like

Further examples for reference;

Default Twin Otter




Default Citation Longitude

Hello @ZachB

Thank you for the detailed report and providing the repro package.

You are talking about “animated decals” but are you actually creating animation keys for your decal object?
If so you should not.
The part of the decal that is supposed to follow the animated part needs to be cut out and added at the same level of the hierarchy (in your case, using a dummy with the same name) and exported as a submodel.
Dynamic Liveries

You can find an example of this on the Da62 SDK sample

Also, you livery package does not seem to fully match the CJ4 modular hierarchy?
You only have a model.fuselage folder but the CJ4 has nacelle and tail parts so some parts of your decal might be associated to the wrong part.

If this does not work or produces the same problem, we’d be interested to have a look at your .max/.blend file as well.

Edit: we are also having a look at the base aircraft you mentioned that demonstrate the issue, to check if an issue on our side could trigger this behavior.

Regards,
Sylvain

Hi Sylvain!

My apologies for the late response — been away from home for Memorial Day weekend.

Thank you for taking the time to look into this — by “animated decals”, yes, I am parenting those meshes to an “empty”/“dummy” from the base model (CJ4 in this instance) per the SDK and DA62 sample — not animating them on their own.

At this time I have my decal model attaching to model.fuselage for testing, later on to be broken up into LODs and model.fuselage, model.tail, etc. For what it’s worth, I did try splitting parts into the various .[tag] structures last week, similar to the default CJ4 livery, but just like the default CJ4 livery, the “duplicate” decals still remained.

Attached below is my Blender project for one of the liveries pre-LOD and pre-split, just singular, if that helps at all.

Thank you! :slight_smile:
Zach

N411NK DevSupport Example.zip (7.9 MB)

1 Like

Hi @FlyingRaccoon , just checking in to see if there has been anything further on this.

Thanks! :slight_smile:
Zach

Hello @ZachB

From the information I gathered, the issue is not on your side.
The problem comes from the configuration of the aircraft itself.
The issue is tracked internally, and we’ll need to see it fixed first and default liveries behave as they should before we can confirm this solves the problem for you as well.

Regards,
Sylvain

2 Likes

Hi Sylvain,

Thank you very much for the update!

  • Zach

It seems the Stock 747 also suffers from this Bug

1 Like

Are there any updates on this? Still seeing this issue in SU4 Beta on the DHC6-300 and it’s a real pain.

1 Like