We need a simvar for the name for liveries of the Modular SimObject. It’s currently used to show the livery name on the Aircraft Configuration screen. I propose it to be:
LIVERYNAME | Name from livery.cfg | String (max 128 characters) | Not Settable
The only other one close to this is “Title” and that is pulled from the aircraft.cfg from each variant of the presets folder (so for example, the DA62 there is the Scientific long nose variant and the standard variant). You could override it using a community folder package but it’s not standard procedure and breaks the entire plane on subsequent updates.
FSUIPC, Volanta, SimToolKitPro, and TFDi’s SmartCARS 3 use “TITLE” to pick out what aircraft livery we’re using, and not having a livery name simvar will break functionality for both tracking programs and virtual airlines.
Livery.cfg → Go to [General] → name
TITLE on SimVar page
3 Likes
Id like to show my support to the above request. This is something that just about every virtual airline / other tools have been using for years and specifically with use of MSFS2020, and would like to see something implemented allowing for a unique name to be available as per the above request and would like to ask Asobo / MS to look at this request and offer a workable option.
Thank you
SirValinor
All icao* parameters are not reachable as Simvars:
icao_airline
icao_type_designator
icao_manufacturer
icao_model
icao_engine_type
icao_engine_count
icao_WTC
icao_generic
In general, it should be possible to access programmatically to any variable that might be found in the various .CFG files.
This is even more important now, since the aircraft.cfg file might not even be accessible when streamed.
1 Like
This needs to be upvoted more. The ability to detect liveries are the cornerstone of most VA operations.
Asobo could either do with unencrypting aircraft.cfg for streamed a/c, or providing a simvar. “Title” isn’t sufficient
Bumping this as well - @EPellissier, we have features in some of our MSFS 2020 (blackbird simulations/milviz) products that are dependent on detecting the livery in use.These features are now broken in 2024, with no real method of detecting which livery has been selected.
Having a simvar that can provide a readable reference as to what livery is in use, as suggested in the original post, would be very helpful in resolving this situation.
Hi everyone,
Apologies for the delay in getting back to you on this one - I guess this should be feasible, I’ll check that tomorrow with the team.
Best regards,
Eric / Asobo
I have to disagree with this - for instance you will never have access to data found in protected CFG files. 
Best regards,
Eric / Asobo