August 28, 20223 yr How do I edit the aircraft.cfg in a livery so that ATC does not address me as "decimal"? [FLTSIM.0] Title="Cessna 414A N356II GTN750" Model="\..\..\flysimware_Cessna_414AW\model.GTN750" Panel="\..\..\flysimware_Cessna_414AW\panel.GTN750" Sound="\..\..\flysimware_Cessna_414AW\sound" Texture="N356II" KB_Checklists="" KB_Reference="" description="" wip_indicator=0 ui_manufacturer="Cessna" ui_type="414AW" ui_variation="N356II GTN750" ui_typerole="Twin Engine Prop" ui_createdby="Flysimware" ui_thumbnailfile="" ui_certified_ceiling=14600 ui_max_range=920 ui_autonomy=6 ui_fuel_burn_rate=13.5 atc_id="N356II" icao_airline="" atc_id_enable=1 atc_airline="" atc_flight_number="N356II" atc_heavy=0 atc_id_color="0x00000000" atc_id_font="" isAirTraffic=0 isUserSelectable=1 isFlyable=1 canBeUsedByAITraffic=1 Effects="" atc_parking_types="RAMP" atc_parking_codes="" Edited August 28, 20223 yr by Cpt_Piett 7950X3D | RTX 4090 | 64GB DDR5
August 30, 20223 yr Author Anyone got some advice on this? I entered the callsign in the aircraft.cfg as shown above. They still refer to me as "decimal". Since I have the ICAO EU UK Phraseology Mod installed it leads to some fairly hilarious exchanges. Like: ATC: Decimal contact Anchorage Approach 118 decimal 6. Good day. Me: Contact Anchorage Approach 118 decimal 6, decimal. Fun times, lol. If I enter N356II in MSFS aircraft menu on the flight setup, the callsign is repeated twice, but not pronounced the same way. Like: ATC: N three five six two November three five six India India, Wind 135 degrees, 12 knots, runway 15 cleared for takeoff. Me: Runway 15 cleared for takeoff N three five six two November three five six India India Why is this such a hot mess, what have I done to mess it up, and how can I get some less nonsensical communication? Edited August 30, 20223 yr by Cpt_Piett 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr Author Bumb 😂 Just did a Google search and this thread is on top. Lol! Anyone got any advice? @ryanbatc I’ve got some of your excellent V35 liveries. Do you know how to get ATC to use your aircraft ID properly? (I also know you’re a busy fellow so no pressure to answer). 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr I'm not sure. Everything looks correct. You can try to put just a comma in between the quotes in the ATC airline line. | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
August 31, 20223 yr Author 7 minutes ago, ryanbatc said: I'm not sure. Everything looks correct. You can try to put just a comma in between the quotes in the ATC airline line. Thanks! 🙂 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr Also, the reason it's reading your tail number twice is because you also have it in the flight number spot, you only need 'atc_id="N356II"'
August 31, 20223 yr Did you accidentally enter data on the customization page where you select the aircraft? Type something in and then delete it to make sure it is empty. i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440
August 31, 20223 yr Author 11 minutes ago, Tuskin38 said: Also, the reason it's reading your tail number twice is because you also have it in the flight number spot, you only need 'atc_id="N356II"' Thanks. I put a comma in between the "" for all entries. Still reads my tail number twice. [FLTSIM.0] Title="Cessna 414A N356II GTN750" Model="\..\..\flysimware_Cessna_414AW\model.GTN750" Panel="\..\..\flysimware_Cessna_414AW\panel.GTN750" Sound="\..\..\flysimware_Cessna_414AW\sound" Texture="N356II" KB_Checklists="" KB_Reference="" description="" wip_indicator=0 ui_manufacturer="Cessna" ui_type="414AW" ui_variation="N356II GTN750" ui_typerole="Twin Engine Prop" ui_createdby="Flysimware" ui_thumbnailfile="" ui_certified_ceiling=14600 ui_max_range=920 ui_autonomy=6 ui_fuel_burn_rate=13.5 atc_id="," icao_airline="," atc_id_enable=1 atc_airline="," atc_flight_number="," atc_heavy=0 atc_id_color="0x00000000" atc_id_font="" isAirTraffic=0 isUserSelectable=1 isFlyable=1 canBeUsedByAITraffic=1 Effects="" atc_parking_types="RAMP" atc_parking_codes="" 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr Check that customization window on the flight planner screen, it may still be written in there.
August 31, 20223 yr Author 7 minutes ago, Tuskin38 said: Check that customization window on the flight planner screen, it may still be written in there. It is. Because I entered it there. Thinking that's the correct way. So I've got no entries with the tail number in the aircraft.cfg, but I entered it in the customization window. And the tail number is being read twice. Edited August 31, 20223 yr by Cpt_Piett 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr Author To be honest I've never understood how to do this correctly. Do you set the tail number in the .cfg or in the customization window? Edited August 31, 20223 yr by Cpt_Piett 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr All I know is that if I don't put my flight number in there, ATC just calls me "Airbus" or "Boeing". I think MSFS is using the value in the 'aircraft type' variable instead of what the flight plan or MCDU input says it should be. i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440
August 31, 20223 yr Author Amazing that such a simple thing should be so difficult. Thanks for all the inputs though! I try to avoid having anything in the "tail number" part of the customization menu as it gets written on top of the livery number. It's working on some liveries though. Same aircraft, the 414, and the livery with the tail number "D-ICOM", no issues. I haven't entered anything into the customization menu. [FLTSIM.0] Title="Cessna 414AW D-ICOM GNS530" Model="\..\..\flysimware_Cessna_414AW\model" Panel="\..\..\flysimware_Cessna_414AW\panel" Sound="\..\..\flysimware_Cessna_414AW\sound" Texture="DICOM" KB_Checklists="" KB_Reference="" description="" wip_indicator=0 ui_manufacturer="Cessna" ui_type="414AW" ui_variation="D-ICOM GNS530" ui_typerole="Twin Engine Prop" ui_createdby="Flysimware" ui_thumbnailfile="" ui_certified_ceiling=30000 ui_max_range=1046 ui_autonomy=6 ui_fuel_burn_rate=17 atc_id="D-ICOM" icao_airline="" atc_id_enable=1 atc_airline="" atc_flight_number="COM" atc_heavy=0 atc_id_color="0x00000000" atc_id_font="" isAirTraffic=0 isUserSelectable=1 isFlyable=1 canBeUsedByAITraffic=1 Effects="" atc_parking_types="RAMP" atc_parking_codes="" 7950X3D | RTX 4090 | 64GB DDR5
August 31, 20223 yr Airline and flight number overrule everything else. What I mostly do with GA planes, type eg. "Cessna" as airline and 310 (or short abbr. id) as flight number. Seems odd but always works best. Like this: atc_airline="Cessna" atc_flight_number="310" Edited August 31, 20223 yr by Gerwil
August 31, 20223 yr Author Thanks @Gerwil, I'll give this a try on my next flight 🙂 7950X3D | RTX 4090 | 64GB DDR5
Archived
This topic is now archived and is closed to further replies.