How to have ATC use the correct call signs

Hello There :wink:

I am using the QTR (Qatari) callsign with ATC, but instead of calling something like “Qatari 695” they would say “QTR695”… what do I need to do to make ATC use the correct callsigns?

best
Merlin

Set the flight number to Quatari 695, not QTR

Oh - is there enough character space to do so? I thought I can only enter the 3-letter code haha. Will try to do so - thanks!

No… they need to be set as:

Flight Number: 695
Callsign: Qatari

Then ATC will call you Qatari 695

@MerlinCH65, if you are comfortable with doing some editing. You can also open the aircraft.cfg file for the livery that you want, and you can set the callsign a lot more properly there. Like this Air New Zealand for example.

atc_airline = "New Zealand" ; airline name
atc_flight_number = "4316" ; flight number

Using this, you won’t have character limit, and it allows you to enter Upper/Lower case with spaces as well. If I use the Callsign field in the sim. I would end up with NEWZEALAND as the callsign, as it can’t handle lower case or spaces. And the ATC will read it as “EN-EE-DOUBLEYOU-ZEALAND” due to the uppercases. If I edit the aircraft.cfg file and enter “New Zealand” in there, the ATC will read them properly with “New Zealand”.

3 Likes

Yes, you are right. I was not on the PC when I answered from my memory. :slight_smile:

Anyone having the problem of the sim not remembering your call sign. I have to re-enter it every time i load a plane. I edited all the aircraft.cfg i found but my buds still work as it should. They enter their tail number once and never customize it again. all planes always have their tail numbers like it was during beta.

You need to clear the one on the Flight customisation menu. when you click on the fields, you should see a “Clear” button on the bottom bar, you need to press that. Simply pressing DEL or BACKSPACE on the keyboard doesn’t seem to work. Only pressing the Clear button at the bottom (probably several times) is the confirmed way to really clear the callsign from the UI, so that it can use the one in Aircraft.cfg

Yes that helped, thank you. The planes Im now having the problem with are the ones without the aircraft.cfg file. Like the stock Barren58. Thanks for your thoughts, it really helps.

That’s impossible, Aircraft.cfg are a basic building block of the sim. Without that file, the sim can’t read what the aircraft is, the labels, and whether or not they should be selectable on the menu or if they spawn as part of the ground aircraft.

Even the base stock TBM 930 that’s part of the Core mandatory content of the sim has an aircraft.cfg in the official folder. You just open it, and make the callsign edits to the ATC_Airline fields.

No it isn’t. All the Premium Deluxe aircraft have encrypted config files, in .fsarchive format.

To my defense, I didn’t know Barren58 is part of the premium deluxe, since the poster mentioned it with “stock”, I assumed it’s part of the base sim. Which I also wouldn’t know since I remove all aircrafts except for the A320neo in the sim since I’ll never fly them anyway.

Even so, the aircraft.cfg file is still contained within the encrypted .fsarchive. And same with how we have liveries for the 787 Dreamliner. All you need is another aircraft.cfg with the same kind of structure that points to the Premium Deluxe aircraft and place it on the community folder.

Then when you pick the livery in the menu, it will use whatever registration number, callsign, and flight number that you added in your custom community aircraft.cfg.

Thanks Neo! Just filling out the two fields propperli did the trick! And if you write “Qatari” then it even sounds half decent correct in terms of pronounciation :grin:🙋

sorry bout saying stock… i bought the whole package and refer to Asobo planes as being stock. ino there are a bunch of encrypted aircraft.cfg in the main but still have the open aircraft.cfg for their liveries. I get that. i was just trying to get back to the sim remembering my initial tail# like it use to. I even reformatted and re-installed it all to no avail. thanks for trying guys…

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.