FS 2020.  Windows 10.  Alienware Arora R12.  FSUIPC7 installed.  Made a flight from KMEZ to KLIT, with STAR, CoPilot handling all radio comms, with PERFECT flight, including a go-around (plane on runway), with ATC vectors to another ILS approach.  The PTT buton is Honeycomb Alpha, left "trigger" (button 0), and the PTT button window shows green, but I never get an answer from ATC.  Sometimes, I get a reply something like "Aircraft calling Center say again with your call sign.", but usually just never hear anything.  Any help would be GREATLY appreciated.

Hi Tom

 

just make sure after clicking the validate and then click FILE button othewise you will never get any answer  then you can press PTT button, let me know if it works. and also make sure the Microphone is on in your aircraft(Important) 

Validate and File confirmed.  Blackshark Headphone/Mic tested and working.  I have a feeling that it may be a setting in FSUIPC7, having to do with how the Honeycomb "trigger" button is "sending" to P2A.  Watched Clumsy Geek video again, and got a hint of a setting that I will probably try later this evening.  Thanks.

1 hour ago, Tom V said:

Validate and File confirmed.  Blackshark Headphone/Mic tested and working.  I have a feeling that it may be a setting in FSUIPC7, having to do with how the Honeycomb "trigger" button is "sending" to P2A.

If you assigned that button to PTT within P2A then FSUIPC has nothing to do with it.  It is P2A which is reading your button presses. You wouldn't even assign anything to that button in FSUIPC.  And in any case, you did say:

15 hours ago, Tom V said:

The PTT buton is Honeycomb Alpha, left "trigger" (button 0), and the PTT button window shows green,

If the PTT is showing green in P2A then of course it IS being detected!  You can prove to yourself that it must be your microphone sound input which is wrong by pressing the PTT button on the P2A window directly, and holding it, using the mouse instead of the button.

I sometimes find that the Windows sound input has disabled itself in the Windows sound settings and have to specifically re-enable it. 

If it is really just that P2A is not recognising your requests, try using the facility to test this in P2A. I find I have to do this occasionally in any case.

One last thing to bear in mind it that the PTT needs pressing and holding for almost a second before you start speaking.

Pete

 

 

Pete is correct.  If your PTT button on screen is turning green, then your button is working.  And, pressing the button and waiting a half-second or so before speaking may fix the problem.

Using Grammar Help in P2A you can see if your microphone is working correctly.

⦁    Press the Grmr Help button to the right of the Flight Plan
⦁    Press the Practice button 
⦁    Check the Message box with the connection information to see if US English is set as the Speech Recognition language
⦁    Try saying "Say Altimeter" with no other words.  It should be recognized.  
⦁    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 and you have a mic problem, a mic settings problem or a problem with how the mic is positioned relative to your mouth.

Dave
 

Thanks for all the great suggestions.  I will try Everything this evening, and will try to share what I find (assuming I can get it working).  Tom

Dave, practicing seems to indicate that my Blackshark mic is cutting off first and last part of what I am saying.  Wonder if there is a setting for Blackshark that is "clipping" my speech?  I can hear the Replay, but usually clipped on each end.

Tom

Ok.  Shut off "voice activation" in windows.  Trained voice.  Set mic volume to high.  Turned on Practice and it seemed to work.  Then, started talking with atc for an IFR flight, and everything seemed to work!  Fingers crossed!  Anxious to try again later!  Thanks for all your help!

 

Tom