Quacks63

Hello Dave, thank you for your response.Here are two screenshots: https://www.dropbox.com/s/z7w1dfslaff3dfu/2018-07-16 (5).png?dl=0 https://www.dropbox.com/s/902s4i90cz0h1lc/2018-07-16 (6).png?dl=0 kind regards, Gerd

Hello Dave, thank you for your response and service. It fits this awsome software that I appreciate very much! Lets go on to the issue: 1. SWITCH SETTINGS: Check to be sure the Power indicator in the bottom left of the main P2A screen is green. check! it´s green 2. VALID CALL SIGN: Make sure you are using a valid call sign by changing it to the default check! Callsign is Beech N45XS 3. 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. check! Freq is valid, actice and standby swapped a couple of times. ATIS freq returns ATIS information without any prob. 4. PTT BUTTON: Use the PTT button on the main screen to eliminate the possibility of it being the Joystick button setup as the issue check! PTT button turns to green when pressed either assigned key or P2A screen. No prob. 5. VALID PHRASES: Make sure the phrase you are using is appropriate for the controller. “Say Altimeter” should work with all controllers, so use it. check! Pressing PTT and saying "say altimeter" returns no reaction. If I use the "say it" option, everything works fine, the controller responds as estimated. 6. VOLUME SETTINGS: Check the Windows Volume Mixer and be sure Pilot2ATC volume is turned up. (RIght click on the speaker icon in the task bar and select Volume Mixer). check! all volumes on 100% Also check the volume of the voices in P2A Config. check! all volumes on 75% and I can hear them. On the Communications tab of the Sound dialog, be sure "Do Nothing" is checked for when Windows detects Communications activity. set and checked! 7. 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. Latest drivers are installed, Dave. I have no idea what addons are running. Do you mean Realtek Audio Manager? "Nahimic 2+" was delivered with the Mainboard. I turned it off and on with no difference in result. btw: Windows 10 does not list P2A as an app thats has control over the microphone. Is this essential? If so: how can I add it to that list? 8. GRAMMAR HELP SCREEN AND DIAGNOSTICS: Try using the Grammar Help screen. ⦁ Press the Grmr Help button to the right of the Flight Plan ⦁ Pess 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 I followed all steps. Will send you my screenshots. "Say altimeter" does not trigger anything. Replay returns nothing. It´s just as if my mic is simply cut off...

Unfortunately, same problem here. Microphone works fine with TeamSpeak, Skype, SQUAD and Battlefield (both ingame voice) and others. But does not trigger any reaction of Pilot2atc. Windows 10, MSI Gaming Pro Carbon z470, nVidia Geforce 1080, AMD Ryzen 5 2600x, Realtec Audio drivers, Sennheiser Headset Any suggestions are welcome. Thx in advance.