The aircraft.cfg is a standard format so you can create a livery package and create an appropriate aircraft.cfg for the plane for the livery.
As noted in @ENON2058 post, Liveries are ordered alphabetically, so just name the plane folder containing the aircraft.cfg file and texture files 00_carenado_PC12_whatever so it’s first, and then the call sign from the livery will be used. Obviously, you can change the manufacturer to Pilatus as well instead of Carenado (if that’s how it’s labeled) so it shows up in your hangar in the right slot, too. Etc. etc.
Don’t forget the
[VARIATION]
base_container = “…<Aircraft_Package_Name>”
section so it knows what plane to connect to… (if the livery already works, it should already have this section).
The call sign is controlled by the
atc_type =
atc_model =
sections. See the default aircraft for examples. If you use the TT_ etc. etc. stuff, the manufacturer and model must be in the “I forget” base file definitions in the One Source\fs-base directory. You can edit that file to add new definitions, but it gets overwritten with every update.
I’ll fix the post when I get home to my MSFS computer.