Converting 2020 liveries to 2024

User Support Hub Aircraft & Systems
, ,
1

Hi,
quick question I’m sure some know answer to.
In the most simple terms possible, as I’m not a content creator but love to fiddle around.
What are the prerequisites in the aircraft.cfg in both 3rd party base plane and in liveries to show in the proper menu in 2024, in the Livery menu in aircraft selection, not in the Variant menu, or sometimes even as it’s own airplane? The liveries are most likely abandoned never getting update and editing just this file doesn’t/shouldn’t break their compatibility with 2020.

So far I figured deleting almost everything in the livery aircraft.cfg and leaving in just the “title”, “ui_variation”, “model”, “texture” in [FLTSIM.#] puts it under the same plane as base.
I can’t figure out the rest by testing. The plane (FBW A320) comes with two liveries, both in their own folder, and the choice between them is correctly in the Livery menu, not Variation.

1 Like
2

I have found that for 3rd party aircraft you need to match the ui_type, ui_createdby and ui_manufacturer fields to exactly match those fields in the source aircraft’s aircraft.cfg. The livery will however show up in the Variant tab and not under the livery tab of the main aircraft, but at least it is there and selectable.

Haven’t been able to pin down the method used to sort the liveries within an aircraft. Sometimes adding a space to the start of the title field moved the livery to a position after the source aircraft’s livery. I found this worked for a V35 Bonanza livery but didn’t work for a CS C-130H livery. One thing I do know is that the sorting in not controlled by the method 2020 uses.

We should be able to work out more once we can get access to the default aircraft after Asobo enabled the local storage option.