• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS [GUIDE] Creating Livery Packages for MSFS

Creating Livery Packages
GONE are the days where the end user had to modify the aircraft.cfg and carefully renumber the FLTSIM.X record, Asobo have created a truly wonderful way to package liveries as a VARIATION.

And it’s really easy to do.

Create a folder called: myname-livery-livername
Inside that folder create the following structure:
SimObjects\Airplanes\aircraft_liveryname\texture.myawesomelivery\
SimObjects\Airplanes\aircraft_liveryname\aircraft.cfg
layout.json
manifest.json


The manifest.json has this content:
JSON:
{
  "dependencies": [],
  "content_type": "AIRCRAFT",
  "title": "Livery Name",
  "manufacturer": "Aircraft Manufacturer",
  "creator": "Your Name",
  "package_version": "0.1.0",
  "minimum_game_version": "1.7.12",
  "release_notes": {
    "neutral": {
      "LastUpdate": "",
      "OlderHistory": ""
    }
  }
}

The aircraft.cfg has this content:
Code:
[VERSION]
major = 1
minor = 0

[VARIATION]
base_container = "..\<<Aircraft Directory>>"

[fltsim.0]
;your FLTSIM definition

The important thing here is the base_container should point to the name of the aircraft directory your livery is for.

Ensure also that your texture.cfg also has fallback to the root texture of the aircraft
Code:
fallback.1=..\..\<<Aircraft Directory>>\texture
 

=rk=

Resource contributor
Original System
Copy/Paste aircraft.cfg entry
Change entry number
add "myawesomelivery" to the texture entry

Asobo System
Create a folder called: myname-livery-livername
Inside that folder create the following structure:
SimObjects\Airplanes\aircraft_liveryname\texture.myawesomelivery\
SimObjects\Airplanes\aircraft_liveryname\aircraft.cfg
layout.json
manifest.json


The manifest.json has this content:
{
"dependencies": [],
"content_type": "AIRCRAFT",
"title": "Livery Name",
"manufacturer": "Aircraft Manufacturer",
"creator": "Your Name",
"package_version": "0.1.0",
"minimum_game_version": "1.7.12",
"release_notes": {
"neutral": {
"LastUpdate": "",
"OlderHistory": ""
}
}


The aircraft.cfg has this content:
[VERSION]
major = 1
minor = 0

[VARIATION]
base_container = "..\<<Aircraft Directory>>"

[fltsim.0]
;your FLTSIM definition

The important thing here is the base_container should point to the name of the aircraft directory your livery is for.

Ensure also that your texture.cfg also has fallback to the root texture of the aircraft
fallback.1=..\..\<<Aircraft Directory>>\texture



:eek:
 
Disregard.. It was the layout.json file getting me -- wish we had script or app to just autocompile that.
 
Added a basic-template livery, but the texture isn't showing up in the liveries. (Still only A320N Basic Skin in menu)
Attached my try of this, so if someone would like into/take it as base to try on own.
 

Attachments

  • revyn112-livery-a32n-easyjet-berlin.zip
    4.1 MB · Views: 147
Last edited:
Can't get this working either. :( I either get the default A320 livery, or the A320 disappears entirely! I feel like I'm missing something obvious.
Has anybody got a working setup they can share?
 
@Revyn112 There's quite a few issues with your files if you are basing it around the new method.

I'm not sure what I did specifically to make it work (I'm new at this too), but I have a feeling it was folder name related. Either way, here is a working version for you. I basically just copied what I did for my own livery and put in your details.
 

Attachments

  • revyn112-livery-ejberlin.zip
    4 MB · Views: 96
Appreciate the credit there @Revyn112 however there's all sorts of wrong in that FLTSIM section.
I'll create a better template for you later tonight and post here. Actually I'll just make a pull request on that GIT ☺️
 
Appreciate the credit there @Revyn112 however there's all sorts of wrong in that FLTSIM section.
I'll create a better template for you later tonight and post here. Actually I'll just make a pull request on that GIT ☺

Would be happy to see your feedback and contribution there, so we could have a reliable source to get the things right :)
 
Top