What determines the display order of liveries?

As I install more and more liveries, I’m noticing a lot of the livery name are out of order. It seems the game is doing it by alphabetical order in general. However, it would end up with several groups of these alphabetical orders. Like it would start with Air Canada, Lufthansa, etc…then the default livery, and then start with American Airlines, British airways, etc. again (majority of the liveries fall into this group). And then I may end up with a Delta at the very end of the list after United, Wizz, etc…

I looked into aircraft.cfg and could not find anything obvious on what’s causing it. And I also noticed, when a livery is somehow displayed before the default livery, then every aircraft I fly, regardless of livery, in the flight log will show up as that livery variation. For example, I could be flying a United 787 livery, but in my flight log it would show 787-10 Air Canada, since that aircraft appears before the default livery, and is the default at aircraft selection screen.

1 Like

It’s so funny you write about that Air Canada 787 livery. I have that same livery and it shows up instead of the default livery at the aircraft selection menu and it triggers my OCD. I haven’t been able to figure out why it is listed first before the default livery. It bugs me every single day.

Haha, yea I mentioned it because it sits at the beginning, but I can see I got several more liveries after it that all appear before the default aircraft. If I remove that AC livery, the next in line would show up…
I even tried completely replacing the aircraft.cfg with one from a livery that is ordered correctly after the default livery, and it changed nothing. I also tried renaming the model folder, and texture.cfg looks the same for everything.

This happens to the A320 too for me on certain liveries. Right now I got a Jetblue sitting there in the beginning…they must all have the same cause. And I’m sure this will apply to the 747, except I don’t have much liveries there because of the text mirroring.

1 Like

The config file determines the order as far as I know.

what part of the aircraft.cfg? I swear I cannot tell any difference between the ones that are behaving correctly vs incorrectly…

1 Like

Me too. I did a comparison and couldn’t see what was different.

I think I found the folder name inside the “Airplane” folder may be what’s causing it. The Air Canada livery for example starts with “787”, the others that display correctly starts with “Asobo_B787_10” , which would certainly make sense, because 7 becomes before A in sorting.
Now after I changed the folder name, the livery stopped showing up completely…which left me baffled. I don’t think there’s anything in the cfg files that is linked to the folder name…

1 Like

Is it the registration number? That’s what does it in my fleet list in SimBrief. I haven’t checked but I’ve wondered as well. Most of my newest seem to be towards the end.

When you change the folder name inside the Airplane folder, it doesn’t show up because the reference from the layout.json file now has a broken reference. You have to open the layout.json file, and change the filepath names for each line to your new folder name.

1 Like

Yup! This is it! You beat me to the reply! Took me the entire day to figure this out but it’s working now.

So it is the folder name inside the “Airplanes” folder that causes it for sure.
So taking that Air Canada 787 for example, it’s the “…\Community\Asobo_b787_aircanada\SimObjects\Airplanes\787_ACA” folder name.

To make it work properly, it needs to be
“…\Community\Asobo_b787_aircanada\SimObjects\Airplanes\Asobo_B787_10-ACA”
What comes after the 10- doesn’t matter, but it must start with “Asobo_B787_10-” to make it appear AFTER the default aircraft.

Then you need to edit the path name inside the layout.json file under “…\Community\Asobo_b787_aircanada” to the new folder name.

Just finished going through my entire 787 livery stack, now my A320 liveries…

2 Likes

Good find… I’ll bookmark your post so I can restructure my livery library accordingly as well.

This is great. Thanks so much for finding a solution.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.