Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.
No
Brief description of the issue:
As above. ATC is using my callsign on the ground but as soon as Iām airborne it changes to using āAirbusā or āBoeingā. Only started happening in the last couple of days, which has coincided with a number of connection drops and loss of ATC voice
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Fly
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
Latest
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OPās steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if thereās an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
Mods and/or payware arenāt the issue. It started happening a couple of days ago when the connection started dropping and the Azure ATC keeps failing.
Well, it is requested by support to test without any addons, in some cases you think they cannot be related but in fact one of them is the root cause. Anyway are you having that issue with all planes ? or which one are you using to test ?, could you also provide screenshots where you have configured your call sign and the ATC window once in flight ?. Also make sure all your ATC is correctly activated in the general options\sound setup.
I didnāt think much about it at the time, but yes, I too have been hearing ATC calling out aircraft manufacturer names (i.e. Boeing) rather than the usual airline and flight number over the past few days.
Itās not that. It works as it should on the ground then as soon as youāre airborne it changes to the using the manufacturer instead of the airline callsign. It also dumps the alpha-numeric element, so āRYANAIR123ā becomes simply āBoeingā. I went in to the aircraft livery config file and changed the manufacturer to the airline callsign which works as a temporary fix but itās far from ideal.
Something has changed in the last few days and itās almost certainly on the Microsoft side of the game. It started with the Azure voices dropping out, was followed by connection issues then this. @TheSevenflyer This is clearly a new bug, itās not a community support thing.
Just started a quick flight with the stock A320 and ATC was using my call sign, will make some more tests. Can you reproduce that issue with the stock A320 or any base MSFS aircraft ?
I havenāt had chance to try. Out of interest, do you use the rolling cache? This behaviour coincided with me turning it back on and I recall seeing someone else saying that the rolling cache might have caused this behaviour. I canāt imagine how.
I fly at least once a day, most days a couple times.
I just landed at TNCC after an hour and a half flight.
I was not able to reproduce this.
I have heard it occasionally in the past, but that could have been from aircraft that do not have the proper entries in their aircraft cfg file.
These definitely do and weāre working just fine only a few days ago. Itās very odd, but has 100% coincided with these connection drop outs. IIRC itās those that might associated with the rolling cache. I need to try it with the cache off and see what happens.
Very tentatively, I just tried a flight with the rolling cache off. No drop outs and the callsign worked when airborne
I need to try with one of the offending livery / aircraft combos to corroborate it but itās looking like the rolling cache is the problem, as Iād read in another thread.
Right, Iāve now reverted the config file of my PMDG 737-800 Ryanair livery and surprise surprise, with the rolling cache off all is well.
The thread I read suggested that with the ORBX UK Mesh enabling the rolling cache caused problems. Since I disabled the cache I havenāt had a connection drop and the callsign problem has now gone away. I think the connection drops were causing the callsign problem, and the rolling cache was causing the connection drops. An annoying circle of errors!
I guess itās the nature of the beast that this sort of conflict sometimes happens, but turning the cache off seems to be the solution. Hopefully if others are having the same issue this will solve it for them.
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
