I spawn in with the N427RC registration Cessna 414, which has the following configuration:
atc_id=“N427RC”
atc_flight_number=“N427RC”
I don’t know why they did this, but anyway.
I then noticed I had put my tail number in the call sign box by accident.
When I contact ATC I see this:
It’s reported my custom tail number, as well as the tail number built into that livery.
Now, if I open the Behaviours window, and do a quick reload, then contact ground again, I now see this, and this is without me changing anything.
So call sign, and flight number will override the config file even if they are present,
It is now no longer reporting my custom tail number, but the manufacturer as defined here:
atc_type =“$$:CESSNA”
If I remember right, the only way to get your custom tail number to show is to blank the “atc_id” field, as it overrides the custom one.
So if I change that to:
atc_id=“”
I now see this:
It looks like the call sign is overriding the manufacturer, but is this intentional?
Blanking both “atc_id”, and “atc_flightnumber” in the config, then shows neither of the two values above:
Unless you go back to the main menu, and it only works that one time. Any reloading, and it breaks again. I think this last is perhaps an old issue I first saw with Carenado planes, as they were one of the first to work out how to get dynamic tail numbers on liveries.
And if I add the flight number as well, it does not show the tail number at all, just call sign, and flight number.
But again, only if you don’t reload:
So the callsign on its only only overrides the manufacturer, not the tail number.
Callsign plus flight number displays only those two values, and overrides both manufacturer, and tail number in the config file.
Tail number on its own displays the manufacturer, and tail number in the config.
Using all three only shows the call sign, and flight number, so if you want the tail number only, never mix the three values.
I’m sure this is old news, but I can’t say I ever noticed this before, and only did because I populated the wrong box in customisation.
The only “bug” here perhaps is that using the SDK to reload the plane then removes the customisations, and either a restart or back to main menu is needed to restore them.