I have many liveries installed and working. All I do is drop the livery folder in the community folder. But a couple of liveries do not show up in the in-game livery selection menu. Problem seems to be from my end because the livery has many 5 star reviews on flightsim.to.
Anyone know what could be causing this and how to fix it?
Also, on the aircraft selection menu, a livery is shown instead of the default aircraft livery. Anyway to change this to default on this menu?
Possibly the liveries are "double packed’ where the folder structure isn’t correct in the zip file? Perhaps they’re 1 level deeper than they should be. That’s all I can think of without knowing which liveries in paritcular you’re referring to. Be sure to read any instructions that come with said liveries. Sometimes if there’s a multi-pack, you have to take extra steps to install them correctly.
As for the default, there are 2 times I can think where it wouldn’t be the default livery showing in the plane selection - if you just chose a livery for a plane, or if you have a mod for the plane that comes with a livery. For example, I have the Turbo Bonanza mod installed, and it has a custom livery. Ditto for the JMB VL-3 915 mod which now appears with a custom livery in the selector by default.
Again, without knowing any specifics as to what planes you’re talking about and what aircraft mods you may have installed, it’s hard to say.
Agreed. I’ve had this happen with sceneries as well. I’ve learned from assuming that the folder I see on my desktop after extracting it is indeed the content folder, only to find out there is a folder/folders within it that is actually what I need. This is especially true with packs that contain multiple liveries within one download.
Exactly what I was getting at. it will have folder structure like
base
If you install the base into your community folder, it won’t work. You have to go into base and install those folders into Community.
Well, let’s be careful here. The telling point is there should be a manifest.json and a layout.json in the root directory (IOW right inside the livery folder) of the livery. A livery can contain multiple livery folders (see my Daniel Webster College C172 liveris for example).
But, yeah, I just ran into that the other day, and I didn’t pay attention there were no json’s in the root till they didn’t show up and I did a facepalm.
You’re correct. You can have multiple liveries in 1 package as you described. The original Liveries Megapack releases were like that.
There are several multi livery packs on flightsim.to that are packed the way I described. The zip file contains a folder which contains the separate liveries without a the layout and manifest json files in the root. I’ve personally encountered 2 such packs so far. And like yourself, it left me scratching my head as to why they didn’t work until upon closer examination I realized what I’d done.
Live and learn.
Thank you everyone for your help.
Regarding issue 1: The root folder looks normal, it looks like any other livery that works. It’s not a multi-pack either. I just got rid of the livery and installed another one that is similar and saved myself the headaches. If you’re curious, this is the livery, the 8k version:
https://flightsim.to/file/5225/a321-air-canada-8k-4k
Regarding issue 2: The livery shows up as my “default” livery every time I restart the sim, even when I unselect it. It seems that this livery places itself first in order (left most livery) and perhaps that is why it is selected by default. Have not been able to find out how to change/fix this order. This is the livery in question if you’re curious:
https://flightsim.to/file/601/air-canada-787-10-ultra
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.