Hello everyone. 

I'm hoping someone can help me with my problem. I have MSFS 2020 and P2A (updated). I can connect P2A to MSFS. When I do I can work with P2A and change frequencies. I have never used PTT, but want to get on VATSIM, so thought I would use P2A for practice. However, it only seems to work on the initial press of the PTT button. So when I start P2A up, connect to MSFS, then go to use PTT and say "Say Altimeter" it works. When I try it again, nothing. I try using the speech assist, etc. to no avail. I tried to disconnect then reconnect and it still will not function. When I restart P2A it will do the same thing . . . works once, then stops. When I use the Say It function it works fine, it's only when trying to use PTT.

I have to believe I am missing something. I have a VR headset and a regular mic and they both do the same thing. 

Thanks in advance!

Randy

Here are some additional things to  try, with numbers 1 through 6 being most likely issues based on your description:

1.    SWITCH SETTINGS: Check to be sure the Power indicator in the bottom left of the main P2A screen is  green.  If not, then you need to turn on the battery switch and avionics switch in the aircraft, or if that doesn’t turn it green, check the 2 options “Ignore Battery Switch” and “Ignore Avionics Switch” in the Config P2A Setup panel.
2.    MICROPHONE: Be sure the mic volume is turned up and the mic is not muted.  Some mics have physical volume and mute controls and it is easy to forget to set  these.
3.    VALID CALL SIGN: Make sure you are using a valid call sign by changing it to the default Mfg: Beech; Tail Number: N431VB and pressing the Save Button.  You can send me a screenshot of this page and I will let you know if there is a problem with the call sign.
4.    VALID FREQUENCY: Be sure you have a valid frequency showing in the Active frequency display.  Open the Radio Panel and check that the frequency selected has a valid controller assigned.  Try swapping the active and standby frequencies a couple of times.
5.    PTT BUTTON: Use the PTT button on the main screen to eliminate the possibility of it being the Joystick button setup as the issue
6.    VALID PHRASES: Make sure the phrase you are using is appropriate for the controller.  “Say Altimeter” should work with all controllers, so use it.
7.    VOLUME SETTINGS: Check the Windows Volume Mixer and be sure Pilot2ATC volume is turned up. (While P2A is running, rIght click on the speaker icon in the task bar and select Volume Mixer).  Also check the volume of the voices in P2A Config.  On the Communications tab of the Sound dialog, be sure "Do Nothing" is checked for when Windows detects Communications activity.
8.    HEADSET SOUND SETTINGS: If you are using a headset, Windows may recognize that and put a set of "level" settings on the Levels tab of the Headphone Properties.  To set these, select the Headset in the playback devices Windows Settings and press "Properties". Select the Levels tab.  Be sure all levels are turned up as in this screenshot - notice the Microphone setting here on the Playback device:
9.    ADVANCED HEADSET / MIC SETTINGS: Be sure the Advanced tab of the Properties window for your default recording device has the sound format set to 2channel, 16 bit, and either 44,100 Hz or 48000 Hz (CD or DVD Quality).
10.    HEADSET AS DEFAULT PLAYBACK AND RECORDING DEVICE: If you have a headset mic set as the default Recording/Audio Input device, be sure and set the Headset as the Default Playback/Audio Output device.  Some users have had their microphone not working because  they set their Speakers as the Playback device.  
11.    NOISE CANCELLING HEADSET: If you have a noise cancelling headset like used in real aircraft to reduce engine noise, these may not work with the Speech Recognition.  Try using a standard PC headset.
12.    DEFAULT COMMUNICATIONS DEVICE: If using a headset as the default Playback/Recording device, be sure it is not also being used as the Default Communications Device.  This assignment of multiple duties seems to cause a problem.  Likewise, be sure the microphone is not assigned to any other duties besides the default audio input device.
13.    GRAMMAR HELP SCREEN AND DIAGNOSTICS: Try using the Grammar Help screen.  
⦁    Press the Grmr Help button to the right of the Flight Plan
⦁    Press the Practice button 
⦁    Take a screenshot of the resulting Message box with the connection information and email to me 
⦁    Try saying "Say Altimeter" with no other words.  It should be recognized.  Let me know the result.
⦁    If not being recognized, press the "Replay" button and see what your voice sounds like.  If no sound, then your voice is not getting through to Pilot2ATC.
14.    SOUND DRIVERS AND ADD ON PROGRAMS - Many PCs come with Sound Add On programs from the manufacturer that are run at startup.  Some of these programs may "Capture" the microphone and prevent Pilot2ATC from hearing it.  Also, some addons may have such features.  Check to be sure there are not other sound programs running.  Also be sure that you have the latest Audio Drivers for your Microphone installed.
15. Sound Bar or Other Sound Hardware AddOns Some users have reported that disconnecting sound hardware equipment like a Sound Bar or external speakers resolved the problem of a Mic not working.
 

Wow Dave!  Thanks for the detailed steps and quick reply. I will give each of these a try and report back to let everyone know what fixes the problem.

Randy

Looking through each of these, it looks like I tried the majority of them, but I will go back and double check my work. Also, the microphone works the first time I make a call, then nothing afterwards, even on the Grammar Help screen. I speak into the mic using the on-screen PTT and say "say altimeter" and it comes back green. I try it again and nothing happens. On the Grammar screen I press replay when it doesn't pick up my voice and there is nothing, so the mic seems to be disconnecting on my end somewhere.

I'm 99% certain this isn't a P2A issue, but was hoping someone had had this problem before and it would be a quick and easy setting.

There are a couple of steps above that I have not tried. Regardless, I will report back later today. 

Thanks again!

Randy  

I think I have it working now, but trying to bring it into VR to really test it out. Working with Windows Mixed Reality and struggling, but what's new. :-) 

It appears there was some type of conflict with a plug-in mic and the built in mic on the reverb g2 headset.

Thanks for the assist!

Randy