In MSFS2020

ATC or copilot voice cuts out when right mouse button is pressed in simulator windows. Full sentence is heard when holding down right mouse button or when not pressing it. When pressed mid sentence, the rest is lost and not heard. Same happens if right mouse button is released. I had this problem before and cannot recall how I fixed it, and not it is back in the PMDG 73-series. I've tried clearing out all the key mappings without success. Also checked for any right mouse button mappings and cannot find any that could interrupt. This problem also seems to correspond to P2A not detecting when battery is turned on. Interestingly, it will detect the battery on when the right mouse button is pressed in the simulator.

 

EDIT: Also noticed, this does not happen in the external view

Edited February 17, 20233 yr by myrmicat

You can be absolutely sure that all P2A key and button mappings are cleared by rename or deleting the AppConfig.xml file located at:

c:\users\<UserName>\AppData\Roaming\P2A_200\Settings\AppConfig.xml
where <UserName> is your PC user name.
 

If that doesn't fix it, then the Mouse button may be doing something in a different program that is muting the sound.

I have this exact same problem exactly the same way as described.

I am using the Fenix A320.

I have tried deleting the `AppConfig.xml` and starting over.

I have also removed all bindings in MSFS for the right-click button to see if it made a difference. If I remove all the bindings it does not work at all actually, I need to hold the right-click button for Pilot2ATC to work.

I am not sure what the problem is. I feel like I have exhausted all the possible options to make this work 😞

OK , on this topic I seem to have found a fix , at least for me anyway, I set all the controller profiles in MSFS2020 to default , once they were set to default ,Then, I started Pilot2ATC and it worked , then I proceeded to find which profile the error was on by process of elimination , by changing each one , one at a time BACK to the profile I had created for it , when I got    to ( In my case ) is the Honeycomb Alpha profile I had created , and noticed it wasn't working and determined , that this profile was this issue.