Livery chaos
-
Hi,
I've spent some time trying to organise my Fokker liveries, but to no avail. My Fokker 100 liveries are divided over 9 variant groups, that each have 1 or multiple liveries in them (screenshot shows the variant grouping):
How can I regroup them to just 4 variants (as should be?)?
Stefan
-
-
I have some requests about the livery organization and naming scheme (in 2024), as well.
-
IMO it would be a better experience for the user if the listing started with the airline name (AKA Malev | F70, or F70 | Malev), followed by the rest of the information -- ALL of the F70 listings are "Integral Airstairs | Large Cargo Door," so that's not the thing that sets them apart -- the airline is. And if you don't already know the livery on sight, you have to hover over each livery and wait until the text side scrolls far enough to see what that particular livery is. This isn't Just Flight's fault, it's Asobo's for their poor UI design. But as a customer, I'd just like it fixed.
-
Please merge the Just Flight liveries into the other liveries, so they don't show as two separate variants. They're the same aircraft. Again, this is a problem created by Asobo's bad UI -- but I doubt they're going to fix it any time soon.
I understand that Asobo has created challenges for devs with a new file structure and an unfriendly UI, but we customers are the ones stuck in the middle trying to sort through a mess of variants and liveries. It's not a good experience.
-
-
Sadly, there is little we can do to improve this, as it's a limitation of using MSFS 2024 native (but non-modular) packages in MSFS 2024.
Every livery "package" is listed in the sim as its own variant. The Just Flight house liveries are included in the main aircraft package, the Livery Manager liveries are included in their own package, and third-party liveries are included in their own package(s). The only way to combine those is to combine them all into one single package, which brings about its own separate issues.
The livery names themselves are not something we would commit to changing at this stage, as there are other aspects of the product, as well as other creators' third-party liveries, that are dependent on those livery names (for example, the livery_config.ini files which set the external equipment configurations).
We do have all this feedback logged though, and it is something we would like to improve if we can find a better solution.
Mark - Just Flight
-
Thank you for your answer. I was able to reduce the number of packages a bit by placing third-party liveries in the Livery Manager's folder and regenerating the layout.json file. This yields 8 packages at most for the F100, which is an improvement over 10 :-).
-
Sorry to semi-hijack thread, but I can't get liveries from Flightsim.to to sow up. I use addons linker, but putting the F100 and the liveries in folders in linker, the FS.to ones did not show. Putting the F100 and the liveries directly into Community resulted in a couple of them showing up, but not all.
I'd liked to keep the aircraft in addons linker, is that possible and could I use 3d party liveries that way?
-
The door issue with third-party liveries looks to stem from livery artists using a different format in the Title= entry of the aircraft.cfg compared to our own liveries. If the Title= line does not include the door variant, then the correct door logic will not load in the simulator.
We're investigating this on our side to see if there's anything else we can do to detect which variant it loaded in the simulator, but for now, the quickest solution would be for livery artists to update the aircraft.cfg Title= entry so that it is in the format of:
[Aircraft Type] | [Pax Door Type] | [Cargo Door Type] | [Airline]
Mark - Just Flight
