I have a problem talking to the default ATC which has happened over the last 3 flights on the last 3 days.

It does not appear to be aircraft specific has it has happened with both the Fenix A320 and the PMDG 737-800.
When I start my flight at the gate I have 2 way communications with the ATC as normal and can hear both Pilot and ATC commands.
However at sometime during the flight I loose the sound from the pilot to the ATC although my response to ATC instructions are visible in the ATC text window and are acknowledge by ATC. Communications with AI traffic and ATC are not affected as I hear 2 way communications with the AI traffic. I have not made any changes to my Flight Sim settings or hardware changes.
Any help would be appreciated.

Thanks. 

Edited May 9, 20233 yr by wardp
Formatting

I think this is a bug introduced in the last sim update.  A few have mentioned it and it has sometimes happened to me (I noticed it ocurred after speeding up the sim rate for a while).

It's been happening for me for several SUs.  That's why I gave up on default ATC and use Pilot2ATC now (with Sky4Sim in VR).

Yes, this is a regular bug and the FS team have closed the bug saying they can’t reproduce it. There’s a large thread over at https://forums.flightsimulator.com/t/cannot-hear-atc-instructions-and-other-aircraft-suddenly-while-ai-copilot-still-responds/418969/930 which would be worth posting in.

At this point, it’s the most annoying thing.

Oh wait.... Asobo not being able to reproduce something that thousands of pilots have experienced. THAT’s the most annoying thing.

 

Actually, I've gotten this bug regardless of which ATC I'm using (I've had it with default ATC and Pilot2ATC).  And it's not just the latest SU, it's been going on many SU's back in time.   It doesn't happen all that often for me.

I think it has something to do with Windows, for example how many sound devices do you have defined in Windows Control Panel | Devices?  My old FS computer had a couple defined for some reason.  I just built a new FS rig so I'm hopeful to never see that bug again.

I think one time I got in the device settings when it was bugging, and managed to get the sound kicked on again.  It's almost as if Windows or MSFS becomes confused as to which device it should be outputting to.   It could be a bug in the way MSFS handles sound though, and not a general Windows bug, but I'm not sure.