February 19, 20224 yr Is anyone else getting garbled communications from ATC with the latest Public Beta2m? For example, in Eastern Europe on a flight from LHBP > LROP Contact BUDAPE SAINTERNATIONALCOUNTYNTROL Center on Contact BELGRADECOUNTYCONTROL Center on ... QNH is One Zero One Six at HENRICOUNTYANDA
February 19, 20224 yr Commercial Member That's an issue with the names of controllers and airports in the AIRAC data. There is logic to try and fix most names, but garbage names like the examples don't lend themselves to fixing. Dave
February 20, 20224 yr Author Interesting. For what it's worth, I've experimented a bit with this and discovered the following. Updating the AIRAC cycle from 2113 to 2201 and running the same Public Beta2m, gave the same results as reported above in the earlier post with mispronounced/garbled names on the same route. So I've since rolled back to Public Beta2g2, which was my last version before Public Beta2m, and found that the issue has disappeared and the names are pronounced and displayed correctly. So there's maybe a little more to this than has been suggested. I think I will stick with Public Beta2g2 for the time being.
February 20, 20224 yr Commercial Member It's possible that the logic to "fix" the names is acting up. I'll have a look and see if I can find a problem. Dave EDIT: There was a problem and it should be fixed in Public Beta 2n. Edited February 20, 20224 yr by Dave-Pilot2ATC
February 20, 20224 yr Author Thanks very much. It never ceases to amaze me how quick Dave is to respond to queries and to fix issues. As has been said before, probably the best customer service in the business.
Archived
This topic is now archived and is closed to further replies.