Hi guys,

 

I have quite a few paints in MSFS 2020 that I am never going to fly, both Microsoft official and 3rd party aircraft.

 

 

Sometimes one model will give you 15 different paints, all with just different registrations...I don't want that.

 

Is there a way to disable them so they are not loaded into the sim each and every time...this is a bit of housekeeping on my part.

 

I have aircraft manager but cannot see a way of disabling paints you will not fly.

 

Thank you..

In content manager you can just delete all the liveries you don't want. You can't preview them but from the titles it's fairly obvious what they are. 

For the third party aircraft bought outside of the Marketplace, just go in the the folder for that aircraft, find the texture you want to keep, make sure the texture.cfg doesn't refer to other folders (if it does, remember not to delete them) and remove the texture folders you don't want. You'll also have to edit the aircraft.cfg and renumber the entries so the first one starts with '[FLTSIM.0]'.  You usually have to keep the main texture folder as other texture folders need to refer to it but sometimes that one folder has everything you need for the one livery you want to keep. 

It's time consuming but worth it in my opinion. For every aircraft I have there is only one livery, just as there would be if it was a real hanger. I wouldn't have the same aircraft in seven different liveries! 

Just keep a backup until you have tested it in MSFS first. 

 

If it's just eliminating the host of paints in the selection section, here's what I have done:

Find your way to the Aircraft.cfg and change this:

[FLTSIM.0]
Blah

blah

blah
isisUserSelectable=1   to   UserSelectable=0

Good for one of those 'What shall I do now?' days.

 

EDIT: Oh bugger! St Mawgan already did it. Wake up Attwood! 🙄 

Although you can do this for Asobo ones as well. Not just add-ons

Edited July 19, 20241 yr by Ron Attwood

Thanks guys, I moved all the paints I did not want into a unused paint folder BUT did not alter the aircraft .cfg numerical order , for the simple reason I can't find it subsequently the sim loaded and those entries in the selection were just blank. I did this before raising my question.

 

So, my million dollar question, where on earth are the aircraft.cfg files for a given plane...

 

Update, I can find the aircraft.cfg file for a 3rd party add on but not via marketplace...EG the Cessna 337 from Carenado has waaaay  to many variations I will use so want to do as St.Mawston suggested, backed up by Ron. This I used to do in Prepar3d...where are their aircraft.cfg?

Edited July 19, 20241 yr by davenicoll
Addition

2 hours ago, Ron Attwood said:

isisUserSelectable=1   to   UserSelectable=0

Actually for addon aircraft models purchased at sites other than the MSFS Marketplace, and more recently for Asobo default models, Mr Attwood nailed it.  After planning out what you want the process only takes a couple of minutes.  First, find the aircraft for which you wish to limit the number of liveries.  Determine the standard (developer supplied) liveries you wish to see. 

Navigate in to find that addon model's Airplanes folder.  Will look something like this:

D:\MSFS Addons\Aircraft Mods\Cessna 414-AW 4_1 (flysimware)\flysimware-cessna-414aw\SimObjects\Airplanes

Find and make a copy of the "aircraft.cfg" file.  Also, make a backup copy elsewhere on your system.

Open the aircraft.cfg file with a text editor like notepad.  Perform a Replace/Replace All and change "isUserSelectable=1"  to  "isUserSelectable=0".  That will eliminate ALL of that model's liveries from showing in MSFS.  Next, find the sections for just those liveries you do wish to show.  Manually in those sections change isUserSelectable= from 0 back to 1.  Save the file.  Done!

Here is an example.  My Flysimware Cessna 414-AW comes with I believe sixteen (16) liveries.  But there are only four (4) different color schemes.  For each of those schemes there is a livery version with a WT enhanced Garmin GNS530.  There is a version of each scheme with a TDS Garmin GTN 750 and weather scope.  There are then two liveries of each scheme with PMS GTN 750s. Those two of each have different autopilot avionics.

I have the TDS GTN 750 and do not have the PMS version.  So I can quickly identify eight (8) of the liveries I could care less about.  Of the other eight (8) remaining liveries, I myself only prefer the N427RC color scheme. 

I will time myself here with a stopwatch. 

I will first make a backup copy of aircraft.cfg.  I will then use Replace/Replace All with Notepad to change all of the the isUserSelectable=1 lines to isUserSelectable=0.  Next I will locate the two (2) livery sections for N427RC that I wish to see and manually change each back to isUserSelectable=1.  Last I will save the file.

It took me 1:35 (minutes:seconds)

This issue is expressly why I now purchase addon aircraft models at 3rd party sites. 

If you wish to limit the number of addon liveries you have downloaded from sites like TO. simply do not select them with AddonsLinker, or if not using that invaluable tool then just remove those liveries from your Community folder.

Hey those that own the Simworks Studio Kodiak 100's.  This method is right  up your alley.....

Edited July 19, 20241 yr by fppilot

17 minutes ago, davenicoll said:

So, my million dollar question, where on earth are the aircraft.cfg files for a given plane...

They are not accessible foraddon models purchased in the MSFS Marketplace.  Again, that's why I purchase elsewhere.  I thought Asobo was going to remove that restraint for purchased 3rd party addon models but have not seen that done yet.

Edited July 19, 20241 yr by fppilot

Thank you fppilot...what about those from the marketplace?

2 hours ago, Ron Attwood said:

Although you can do this for Asobo ones as well. Not just add-ons

Can you enlighten me Ron?

9 minutes ago, davenicoll said:

Thank you fppilot...what about those from the marketplace?

I meant Marketplace.  I have edited my earlier message to correct it.  Thanks for pointing that out.  I also corrected what I originally wrote about Asobo default models.  Asobo did open up access those aircraft.cfg files.  So the issue persists for 3rd party aircraft models purchased from the marketplace.

Edited July 19, 20241 yr by fppilot

You must be one of the new guys. I use the old 'Hammer and chisel' method 😉

Asobo B58

[FLTSIM.0]
title = "Asobo Baron G58" ; Variation name
model = "" ; model folder
panel = "" ; panel folder
sound = "" ; sound folder
texture = "" ; texture folder
kb_checklists = "" ; Procedures/Checklist sibling file name
kb_reference = "" ; 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 = "TT:AIRCRAFT.UI_MODEL" ; e.g. 747-400, 172
ui_variation = "TT:AIRCRAFT.LIVERY.DEFAULT" ; e.g. World Air, IFR Panel
ui_typerole = "Twin Engine Prop" ; 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 = 20688 ; service ceiling / max certified operating altitude (ft)
ui_max_range = 1480 ; max distance the aircraft can fly between take-off and landing in (NM)
ui_autonomy = 7 ; max duration the aircraft can fly between take-off and landing in (Hrs)
ui_fuel_burn_rate = 200 ; average fuel consumption per hour (lbs/hr) - reminder: fuel density is ~6.7lbs per US gallon
atc_id = "ASXGS" ; 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 = "" ; 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

 

4 minutes ago, davenicoll said:

Can you enlighten me Ron?

C:\Users\Ron\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore

Select your victim.

It's true there are one or two aircraft left without .cfg and some without the 'IsUserSelectable = 1 ; Is the plane selectable by the user' line

But you can insert the line yourself

Thanks guys - So all those purchased via the marketplace are the only ones we can't have an aircraft.cfg for....Grrrr...there the ones that clutter us up with far to many paints..

2 minutes ago, Ron Attwood said:

C:\Users\Ron\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore

Thanks Ron....I went to that location and found tumbleweed blowing through it...it's empty..

Just to add Doing it this way means that you can still see the correct livery in multiplayer (Stifles laughter) if that concerns you.