This is still happening in 1.37.8.0.
Can’t COM3 just be disabled for this aircraft since we have no active COM3 controls?
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:
Are you using DX11 or DX12?
Are you using DLSS?
If relevant, provide additional screenshots/video:
Same problem. Blacksquare Duke - Cannot switch over KSNS ATIS from Com2 even though frequency is switched in Com2 and Com2 STBY. Leaving anywhere in the Bay Area - in my case KRHV. Very persistant SNS ATIS. Even while doing Vatsim.
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes on MSFS24 SU5 with iniBuilds A310-300
Provide extra information to complete the original description of the issue:
- Only workaround is to tune main radio to another freq - either you get both normal ATC and "parasite"ATIS, or you get none of them (please note that this will lead to the ATIS message still being displayed, but at least not heard)
- This prevents from receiving handoff calls (and answering them obviously). Only workaround found is to tune to another freq and come back later to check, this is the only way to get the handoff calls (note: in career, if ATC tries to request a freq change while being tuned to another freq, you will still get the “confirm freq change” mission step)
Are you using DX11 or DX12?
Irrelevant
Are you using DLSS?
Irrelevant
If relevant, provide additional screenshots/video:
