October 12, 20205 yr Hey Peeps, I just posted this over in the FS2020 forum, but I'll spare ya the extra click. The “Daher” call sign for the TBM has annoyed me from Day 1.. like for realsies, but after digging around I finally found a way to fix it - thanks to Asobo’s use of text-to-speech. This btw works with anything... you type it, the SIM will say it. Don't go too crazy though! 🙂 Go to … \Microsoft Flight Simulator\Packages\Official[Steam or MS Store string]\fs-base Open the .locPak of your language (in the US, it would be en-US.locPak) Search for or scroll down to “ATCCOM.ATC_NAME TAYLORCRAFT.0.tts”: “Taylorcraft”, Right below the Taylorcraft entry, insert the following 2 lines. "ATCCOM.ATC_NAME TBM.0.text": "TBM", "ATCCOM.ATC_NAME TBM.0.tts": "TBM", Save and exit the file. Go to the TBM aircraft.cfg (default location …Microsoft Flight Simulator\Packages\Official…\asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930. If you have a TBM mod installed, check its folder to see if the aircraft.cfg is included there.) Open the aircraft.cfg. Right at the top is the [GENERAL] section. Replace the two “atc type” and “atc model” lines with: atc_type = “TT:ATCCOM.ATC_NAME TBM.0.text” atc_model = “TT:ATCCOM.AC_MODEL TBM.0.text” Save and exit the file. Start the SIM, pick the TBM, select FLY and forever be known as TBM! (ok, not forever, the next patch will overwrite the default .locpak files, but you can do it again. I’m not creating a community package for it, because there are lots of TBM mods out there, most of which already modify the aircraft.cfg and this would just create another conflict.) Edited October 12, 20205 yr by Uwajimaya
October 12, 20205 yr Is it possible to do this for the Carenado Mooney? For this aircraft, I hear only the N #. It's so sad that Carenado doesn't pay close attention to the details. MSFS
October 12, 20205 yr Anyone figure out a way to get ATC to stop spelling the number 1 instead of saying it? "climb to o-n-e tree thousand" sounds kinda silly. Ryzen 7 7800X3D/B650 X AX | 5090 | 32gig | Win10 | Pimax Crystal Light
October 16, 20205 yr Author I found a few more super easy call sign edits. You only need to edit the respective aircraft.cfg, nothing else. Works for the default planes, or mods (if you have a mod that contains an updated aircraft.cfg, edit that one) King Air: To change call sign from "Cessna" to "King Air": replace atc_type = "TT:ATCCOM.ATC_NAME_BEECHCRAFT.0.text" with atc_type = "TT:ATCCOM.ATC_NAME KINGAIR.0.text" Bonanza G36: To change call sign from "Beechcraft" to "Bonanza": replace atc_type = "TT:ATCCOM.ATC_NAME_BEECHCRAFT.0.text" with atc_type = "TT:ATCCOM.ATC_NAME BONANZA.0.text" C208 Grand Caravan To change call sign from "Cessna" to "Caravan" replace atc_type = "TT:ATCCOM.ATC_NAME CESSNA.0.text" with atc_type = "TT:ATCCOM.ATC_NAME CARAVAN.0.text" C172: To change call sign from "Cessna" to "Skyhawk": replace atc_type = "TT:ATCCOM.ATC_NAME CESSNA.0.text" with atc_type = "TT:ATCCOM.ATC_NAME SKYHAWK.0.text"
October 16, 20205 yr Author HEADS UP! @heavyapproach just helped me identify an issue with Step #8 in my TBM post at the top. It's displaying incorrect quotation marks which won't be recognized when you paste the section into your aircraft.cfg. The section should be: atc_type = "TT:ATCCOM.ATC_NAME TBM.0.text" atc_model = "TT:ATCCOM.AC_MODEL TBM.0.text" This issue does not exists in the Beechcraft and Cessna callsign instructions. Apologies for any issues you may have encountered! Edited October 16, 20205 yr by Uwajimaya
October 16, 20205 yr this is excellent, thank you so much for discovering and sharing this! ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
October 16, 20205 yr Awesome, thank you for sharing. Can’t wait to try this Richard i7-12700K | Noctua NH-D15S Black Version | MSI Pro Z690 - A | 32 GB DDR4 3600 | Gigabyte Gaming OC 4090 | 1TB WD Blue NMVe (MSFS 2020) | 500 GB WD Black Gen 4 NVMe | 4TB WD Black Conventional | Fractal Design Torrent Case | Seasonic 1000W Gold Plus PSU | Thrustmaster Boeing Yoke | Honeycomb Throttle | Airbus Side Stick | Virpil Rudder Pedals | Sony X90K 55 Inch TV |
October 17, 20205 yr 18 hours ago, Uwajimaya said: Bonanza G36: To change call sign from "Beechcraft" to "Bonanza": replace atc_type = "TT:ATCCOM.ATC_NAME_BEECHCRAFT.0.text" with atc_type = "TT:ATCCOM.ATC_NAME BONANZA.0.text" Great job with this thread. I have to ask...half seriously...if you typed in "BANANA" instead of "BONANZA", would it say banana? I should try it and find out. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
October 17, 20205 yr 42 minutes ago, Mace said: Great job with this thread. I have to ask...half seriously...if you typed in "BANANA" instead of "BONANZA", would it say banana? I should try it and find out. If you do that, it exposes a hidden Easter Egg and the ATC will say: Quote Beech 157 Oscar Tango, stop monkeying around!
October 17, 20205 yr On 10/12/2020 at 12:44 PM, eslader said: Anyone figure out a way to get ATC to stop spelling the number 1 instead of saying it? "climb to o-n-e tree thousand" sounds kinda silly. Change the following lines in the en-US.locPak (for U.S. ATC) FROM "ATCCOM.LITERAL_1_INITIAL.0.tts": " ONE ", "ATCCOM.LITERAL_1_MIDDLE.0.tts": " ONE ", "ATCCOM.LITERAL_1_TRAILING.0.tts": " ONE ", TO "ATCCOM.LITERAL_1_INITIAL.0.tts": " one ", "ATCCOM.LITERAL_1_MIDDLE.0.tts": " one ", "ATCCOM.LITERAL_1_TRAILING.0.tts": " one ", I'm not sure why the upper case version is pronounced differently from the lower case version but this worked for me. Hope it works for you too. Happy flying!
October 17, 20205 yr 4 minutes ago, Phantoms said: Anyone notice that "3" is "TREE"? There's been a thread on this before. That is the proper ICAO pronunciation of "3". https://www.skybrary.aero/index.php/ICAO_Phonetic_Alphabet
October 17, 20205 yr Author 2 hours ago, Mace said: Great job with this thread. I have to ask...half seriously...if you typed in "BANANA" instead of "BONANZA", would it say banana? I should try it and find out. The beauty of text-to-speech is you can create your own call sign, it'll say ANYTHING. Works great for military callsigns, or if you're 12.. *snicker* - but you have to follow the TBM steps and add the word to the locpack files first. Step 1, 2 as above, then find the alphabetical spot of your new word (dunno if it matters, but I'm following the existing layout) and insert: "ATCCOM.ATC_NAME [your callsign].0.text": "[your callsign]", "ATCCOM.ATC_NAME [your callsign].0.tts": "[your callsign]" And then use that in aircraft.cfg: atc_type = "TT:ATCCOM.ATC_NAME [your callsign].0.text" atc_model = "TT:ATCCOM.AC_MODEL [your callsign].0.text" The model can be a number by the way, but I got mixed results with the TBM, so I use it for both name and model. Try it out and let us know what happens! Edited October 17, 20205 yr by Uwajimaya
October 17, 20205 yr Has anybody tried to alter pronunciations by creating a new version of en-US.locPak in the Community folder? It seems stupid to make these changes over and over again just to have the file overwritten with each MSFS update?
October 17, 20205 yr 4 hours ago, jabloomf1230 said: It seems stupid to make these changes over and over again just to have the file overwritten with each MSFS update? I modified the file and then saved a copy on my desktop. After next update, I’ll just drag and drop. But yes, not having to do that would be better.
Archived
This topic is now archived and is closed to further replies.