need more data Default Livery

[GeoS72]

I lost count of the hours spent changing the livery on several spawn points. This reminds me of the bug that kept resetting sound files.

Can we please address spawn points resetting the livery from X to "DEFAULT"? As you can clearly see, this is not the default livery. Yet the ME seems to randomly (or universally) reset any livery for any aircraft to "default".

Is it possible to use the same method of saving sound file in the trigger system to have the same effect on liveries?

[BIGNEWY]

 

please include a track replay and a step by step guide to reproduce the issue 

 include a track replay example and your dcs log from the session.

thank you 

[GeoS72]

@BIGNEWY, this is an issue more associated with the Mission Editor. How would a track file & log help in this regard? I'll work on it but the results may appear disjointed.

 

[Derbroomaster]

On 10/3/2025 at 3:58 AM, BIGNEWY said:

 

please include a track replay and a step by step guide to reproduce the issue 

 include a track replay example and your dcs log from the session.

thank you 

lol wut

[GeoS72]

@BIGNEWY, I worked exclusively in the Mission Editor today for 6+hrs converting static slots into dynamic slots. Here are plenty of screenshots to review. The Red Boxes/Arrows show the wrong livery upon first access. The Green Boxes/Arrows show the proper livery after selecting it. There were more instances but I am exhausted from staring into the ME & using Paint.net to highlight. My DCS log is also attached. Not sure if that will confirm the problem. What do you see?

dcs - 2025-10-04.log

[Nealius]

Continuation of this issue:

In some situations the issue has been resolved, but it still exists with certain unit/livery combinations.

[GeoS72]

@Nealius, thank you for reminding us of your thread back in 2021! I was surprised to see one of my posts in this thread. Yes, it still happens.

@BIGNEWY, should these 2 threads merge?

Additionally, this link discusses the problem & fix for the ME Removing Sound Files from Action Trigger Section. Perhaps a similar method could be applied to the method of saving liveries?

[GeoS72]

Here is the DCS Log, the track file is too large to attach right now. There was a bug when I opened the rearm menu in the Apache. It showed the F/A-18 livery in the pull-down list. I wasn't able to recreate my initial discrepancy because the base from which this was observed was not captured yet.

However, refer to the screenshots from the Mission Editor. That is more of the tell than any track file or log could show.

dcs - PG Livery Issue.log

[GeoS72]

Here are 2 screenshots that has 1 minor livery discrepancy and 1 major discrepancy. The Apache rearm screen shows "Item 1" in the drop-down menu for liveries. It should read "Apache Desert". I also confirmed the livery ID from the MIZ file.

The Tomcat livery should be the "default", 01 - VF-102 Diamondbacks 1996 livery. Instead, I get the VF-103 Jolly Rogers. Now, this is where the problem gets strange. In the MIZ file, the livery id shows up as VF-103 Last Ride. However, in the Mission Editor, the livery should be 01 - VF-102 Diamondbacks 1996.

The livery IDs are messed up bigger than a soup sandwich.

Here is the Item 1 choice on the rearm menu.

Here is the VF-103 livery, when it should be VF-102 livery.

[GeoS72]

Here is a link to download the track file for this livery bug. I'd like to repeat this is more of a Mission Editor problem. The track file will only show the effect of the problem, where as ME screenshots point to the cause.

PG Map Livery Issue Track File