• 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.

MSFS20 [GUIDE] Creating Livery Packages for MSFS

Has anybody been able to add multiple liveries in the same package? I assumed it would just be a matter of adding multiple [flightsim.x] entries in the aircraft.cfg along with matching folders and json files, but that does not seem to do it.
 
Hi,

Oke so i'm not the only one running into this problem :-) Seems strange that this not works, for multiple texture we have to use the other method?

Marcel
 
While it looks like you can only put one fltsim entry in an aircraft.cfg file, you can have multiple airplanes in the same package. This will allow you to keep your Community folder clean and make it easier to distribute and manage liveries/packages.
  • <your package>
    • SimObjects
      • Airplanes
        • <aircraft_liveryname_1>
          • <texture.myawesomelivery_1>
        • <aircraft_liveryname_2>
          • <texture.myawesomelivery_2>
        • <aircraft_liveryname_3>
          • <texture.myawesomelivery_3>

EDIT: I made the liveryname and myawesomelivery names unique. They need to be unique in the virtual file system.
 
Last edited:
Hi Clements,

Tried that yesterday also yet did not seems to work. Do you have to do something special with the "layout.json"?

Marcel
 
I ran into that issue as well-- Even if they're in separate packages, they each need to have a unique livery folder name under Airplanes.

I guess it's a bit of a judgment call as to whether they should be in the same package or not. One package is cleaner and easier for installing the whole thing. But separate packages allows people to pick and choose, and many people might only want specific colors, for instance. For now, I'm going with separate packages to allow for easier user choice.
 
Yes, the folder names need to have unique and corrected a typo in my post. The folders directly under Airplanes have to be unique in the virtual file system. For one livery, I had unused Asobo_C172SP_AS1000 thinking it would help me trace the livery back to the original file; however, the plane disappeared from my install - not just the livery but the entire plane (I had 22 airplanes in my hanger before and 21 airplanes after and no C172 with the G1000). When I renamed the directory to clements_Asobo_C172SP_AS1000, everything started working.
 
A good way to name the aircraft folders is
[developer/artist]-livery-[aircraft]-[liveryname]

So if I created a livery for a P40E i would create an aircraft folder like this:
Code: 
ozwookiee-livery-p40e-wookieesworkshop
--texture.wookieesworkshop

This ensures that your aircraft folders are going to be unique in the VFS (it also follows
 
Hi Guys,

Still does not work on my end strangely enough.
mgr_tbm930_2\SimObjects\Airplanes\
contains 2 repaints:
\asobo-tbm930-M-ATTI\Texture.M-ATTI\
\asobo-tbm930-N93ZF\Texture.N93ZF\

If i have a "layout.json" with both folders/repaints, none of the repaints show up.
If i have a "layout.json" with only one folder/repaint the repaint show up.

Do you guys have a working example of more then one repaint?

Marcel
 
mgr said:
Hi Guys,

Still does not work on my end strangely enough.
mgr_tbm930_2\SimObjects\Airplanes\
contains 2 repaints:
\asobo-tbm930-M-ATTI\Texture.M-ATTI\
\asobo-tbm930-N93ZF\Texture.N93ZF\

If i have a "layout.json" with both folders/repaints, none of the repaints show up.
If i have a "layout.json" with only one folder/repaint the repaint show up.

Do you guys have a working example of more then one repaint?

Marcel
Click to expand...
Have you got an aircraft.cfg in each?
 

[VERSION]
major = 1
minor = 0

[VARIATION]
base_container = "..\Asobo_TBM930"

[FLTSIM.0]
title = "TBM 930 Asobo N93ZF" ; Variation name
model = "" ; model folder
panel = "N93ZF" ; panel folder
sound = "" ; sound folder
texture = "N93ZF" ; texture folder
kb_checklists = "Cessna208B_Check" ; Procedures/Checklist sibling file name
kb_reference = "Cessna208B_ref" ; Reference information sibling file name
description = "TT:AIRCRAFT.DESCRIPTION" ; Variation description.
wip_indicator = 0 ; know if the variation is good to go or still WIP : -1=Disabled, 0=Rough, 1=1st Pass, 2=Finished
ui_manufacturer = "TT:AIRCRAFT.UI_MANUFACTURER" ; e.g. Boeing, Cessna
ui_type = "TBM 930 N93ZF" ; e.g. 747-400, 172
ui_variation = "N93ZF" ; e.g. World Air, IFR Panel
ui_typerole = "Single Engine TurboProp" ; e.g. Single Engine Prop, Twin Engine Prop, Rotorcraft, etc
ui_createdby = "Asobo Studio" ; e.g. Asobo Studio, Microsoft, FSAddonCompany, etc
ui_thumbnailfile = "" ; app relative path to ThumbNail image file
ui_certified_ceiling = 31000 ; service ceiling / max certified operating altitude (ft)
ui_max_range = 1730 ; max distance the aircraft can fly between take-off and landing in (NM)
ui_autonomy = 5 ; max duration the aircraft can fly between take-off and landing in (Hrs)
ui_fuel_burn_rate = 248 ; average fuel consumption per hour (lbs/hr) - reminder: fuel density is ~6.7lbs per US gallon
atc_id = "N93ZF" ; tail number
atc_id_enable = 1 ; enable tail number
atc_airline = "" ; airline name
atc_flight_number = "" ; flight number
atc_heavy = 0 ; heavy?
atc_parking_types = "RAMP" ; "ANY" / "RAMP" / "CARGO" / "MIL_CARGO" / "MIL_COMBAT" / "GATE" / "DOCK"
atc_parking_codes = "" ; Comma separated and may be as small as one character each
atc_id_color = "0xff000000" ; color for the tail number : i.e. "#ffff00ff"
atc_id_font = "" ; font for the tail number
isAirTraffic = 0 ; Is the plane usable for air traffic
isUserSelectable = 1 ; Is the plane selectable by the user


[VERSION]
major = 1
minor = 0

[VARIATION]
base_container = "..\Asobo_TBM930"

[FLTSIM.0]
title = "TBM 930 Asobo M-ATTI" ; Variation name
model = "" ; model folder
panel = "M-ATTI" ; panel folder
sound = "" ; sound folder
texture = "M-ATTI" ; texture folder
kb_checklists = "Cessna208B_Check" ; Procedures/Checklist sibling file name
kb_reference = "Cessna208B_ref" ; Reference information sibling file name
description = "TT:AIRCRAFT.DESCRIPTION" ; Variation description.
wip_indicator = 0 ; know if the variation is good to go or still WIP : -1=Disabled, 0=Rough, 1=1st Pass, 2=Finished
ui_manufacturer = "TT:AIRCRAFT.UI_MANUFACTURER" ; e.g. Boeing, Cessna
ui_type = "TBM 930 M-ATTI" ; e.g. 747-400, 172
ui_variation = "M-ATTI" ; e.g. World Air, IFR Panel
ui_typerole = "Single Engine TurboProp" ; e.g. Single Engine Prop, Twin Engine Prop, Rotorcraft, etc
ui_createdby = "Asobo Studio" ; e.g. Asobo Studio, Microsoft, FSAddonCompany, etc
ui_thumbnailfile = "" ; app relative path to ThumbNail image file
ui_certified_ceiling = 31000 ; service ceiling / max certified operating altitude (ft)
ui_max_range = 1730 ; max distance the aircraft can fly between take-off and landing in (NM)
ui_autonomy = 5 ; max duration the aircraft can fly between take-off and landing in (Hrs)
ui_fuel_burn_rate = 248 ; average fuel consumption per hour (lbs/hr) - reminder: fuel density is ~6.7lbs per US gallon
atc_id = "M-ATTI" ; tail number
atc_id_enable = 1 ; enable tail number
atc_airline = "" ; airline name
atc_flight_number = "" ; flight number
atc_heavy = 0 ; heavy?
atc_parking_types = "RAMP" ; "ANY" / "RAMP" / "CARGO" / "MIL_CARGO" / "MIL_COMBAT" / "GATE" / "DOCK"
atc_parking_codes = "" ; Comma separated and may be as small as one character each
atc_id_color = "0xff000000" ; color for the tail number : i.e. "#ffff00ff"
atc_id_font = "" ; font for the tail number
isAirTraffic = 0 ; Is the plane usable for air traffic
isUserSelectable = 1 ; Is the plane selectable by the user
 
Yes, if i modify the "layout.json", so remove one of the two paints reference in the layout.json, it works.
 
mgr said:
Yes, if i modify the "layout.json", so remove one of the two paints reference in the layout.json, it works.
Click to expand...
OK And assuming that it works with either... do this:
Create a model folder in each with a model.cfg that points to the original files
Code: 
; Reference LOD implementation, please keep these comments (for now).

[model.options]
; if true, when showing the exterior, also show the interior model (default false)
withExterior_showInterior=true
; if true, when showing the interior with the exterior, exclude interior.lod.0 (default false); only has an effect when withExterior_showInterior is true
withExterior_showInterior_hideFirstLod=true
; when showing the interior, force showing lod0 (default true)
withInterior_forceFirstLod=true
; when showing the interior, also show the exterior model (default false)
withInterior_showExterior=true

[models]
exterior=../../Asobo_TBM930/model/TBM930.xml
interior=../../Asobo_TBM930/model/TBM930_interior.xml
 
OzWookiee said:
A good way to name the aircraft folders is
[developer/artist]-livery-[aircraft]-[liveryname]

So if I created a livery for a P40E i would create an aircraft folder like this:
Code: 
ozwookiee-livery-p40e-wookieesworkshop
--texture.wookieesworkshop

This ensures that your aircraft folders are going to be unique in the VFS (it also follows
Click to expand...

I have tried to do this but I start to run into problems with the file/pathnames being too long for Windows. Any idea how to get around that?
 
Has anyone been able to use custom panel for 787 or SR22?

When I try to use it I lose functions on the G1000 or things in 787.

I remove custom panel.cfg and all is well.

This is first plane out of 10 others I've done with custom panel.cfg (used to remove registration from exterior.)
 
Just got the Carenado 182T update that includes an iPad with option menu on it. It no longer works with custom panel.cfg -- something is missing. This plane was fine using custom file to remove the exterior registration. It's same behavior with 787 and SR22.

Here's example of panel.cfg before 'tablet' got thrown in.

Code: 
// Panel Configuration file
// MyCompany Gauge Aircraft

[VCockpit01]
size_mm=1024,768
pixel_size=1024,768
texture=$AS1000_PFD_1
background_color=42,42,40

htmlgauge00=NavSystems/AS1000/PFD/AS1000_PFD.html, 0, 0, 1024, 768

[VCockpit02]
size_mm=1024,768
pixel_size=1024,768
texture=$AS1000_PFD_2
background_color=42,42,40

htmlgauge00=NavSystems/AS1000/MFD/AS1000_MFD.html,0,0,1024,768

[VCockpit03]
size_mm=530,120
pixel_size=530,120
texture=$KAP140_1
background_color=42,42,40

htmlgauge00=Generic/Autopilots/KAP140/KAP140.html, 0, 0, 530, 120

[VCockpit04]
size_mm=512,512
pixel_size=512,512
texture=$CAR_UPDATE
background_color=42,42,40

gauge00=GAUGE_UPDATE_C182T!Gauge_Update.xml, 0,0,512,135

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_FS2_5

gauge00=TABLET!WindowsAircrafOptions.xml, 0, 0,  834, 600


// - font_color (either a css predefined value such as black, blue, pink or an hexa value such as 0xFF00FF)
// - font_style (bold, italic, bold-italic)
// - back_color (the color of the background, same syntax as font_color)
// For example, in the panel.cfg, you could write this: painting00=Registration/Registration.html?font_color=black&font_style=bold

[VPainting01]
size_mm                = 2048,512
texture                = $RegistrationNumber
location             = exterior

painting00=Registration/Registration.html?font_style=bold&font_color=0x46402d, 0, 0, 0, 0

[VPainting02]
size_mm    = 2048,512
texture    = $RegistrationNumber
location = interior

painting00=Registration/Registration.html?font_color=0xffffff&font_style=bold, 200, -25, 1500, 500

[VPainting03]
size_mm                = 2048,512
texture                = $RegistrationNumber1
location             = exterior

painting00=Registration/Registration.html?font_style=bold&font_color=black, 100, 0, 0, 0
 
The only reason I'm doing this with custom panel is I cannot get rid of reg on side of plane. atc_id_enable = 0 doesn't do anything.
 
You must log in or register to reply here.
Back
Top