P2A is slowing dying

April 5Apr 5

I'm on 0.2.9
For the last several weeks things have stopped working. First all my maps have disappeared. ALL of them! Now, PTT no longer works. I have tested my mic in Windows, Audacity, etc. and the mic works fine. In P2A, pressing PTT does nothing other than play the "PTT Pressed Tone" sound. If I use the "Speak" button to do a "Radio Check" it works fine, it's only if I use PTT that nothing happens. I don't know what to do now. Since I've never had a problem with my mic before, I never investigated if there was a way to test the mic in P2A. I don't see anything like that. How should I proceed? I've never been big on unstalling a program and re-installing. Would that help? Getting very frustrated here. Please help!

X-Plane 12, Ryzen 7 9800X3D, Nvidia RTX 5090, Asus ROG Strix X870E-E mb, 96GB DDR5 (6800MHz), 4TB SSD, Triple Monitor 1440p, Windows 11, FliteSim CLS-120 Yoke, Honeycomb Bravo, TurtleBeach VelocityOne Pedals, RealSimGear G1000 Suite, PropWash Radio Stack, Tobii Tracker 5, Asus Xonar U5 sound card.

April 6Apr 6

Hopefully the dev can give us a timeline for a working version...

April 6Apr 6

Commercial Member

Hoping for the next update to be out this week. It will fix the map issues and a lot of 0.2.9 bugs.

Dave

1

April 8Apr 8

I just want to say that P2ATC is definitely a Love-Hate relationship. When it works it is fan-fkin-tastic and IMO and for the money is all I could ask for. I fly mostly commercial airliners and rely a lot on the vectoring capabiltiy of ATC. But there are so many broken parts to it that it can, at times, literally make me crazy. Since moving BACK to 0.2.7A things for the most part have gotten a bit better but it amazes me how often it can't recognize what it is clearly showing on the flight plan/waypoints/altitudes/couse correction/............you name it, it can't understand it.

But every now and then it will fly me from portal to portal with excelllent execution..........and that is why I still use it. I don't have any other add-on that I scream at so much, have to restart so often and lose my hair over than P2ATC, but when it all comes together (along with Stick and Rudder Chatter in the background and all the SAPI voices (that I can stand)) it is a beautiful thing.

Thanks Dave, don't abandon us. Not yet.

1

April 8Apr 8

Commercial Member

The new version is out and will hopefully allow you to retain more of your hair.

If you have issues, please email the P2A Log file from the flight and a description of the issue to [email protected].

The log files are located at:

C:\Users\<UserName>\AppData\Roaming\P2A_300\Logs

where <UserName> is your PC user name.

Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.

A new one is created each time you start Pilot2ATC and is closed when you shut it down. So, if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one.

Please don’t send the log files with the word “Utterance” in the name. These are for speech practice and not useful for debugging.

Dave

April 9Apr 9

Hey Dave, looking forward to the new version. Will give it a try soon.

Thanks!

April 10Apr 10

Author

I'm obviously missing something huge here. Just updated to RC1 and don't see anything different. No maps and no PTT. Do I need to uninstall P2A completely? My mic works fine from System and Audacity. Have I just messed this all up trying to make it work?

X-Plane 12, Ryzen 7 9800X3D, Nvidia RTX 5090, Asus ROG Strix X870E-E mb, 96GB DDR5 (6800MHz), 4TB SSD, Triple Monitor 1440p, Windows 11, FliteSim CLS-120 Yoke, Honeycomb Bravo, TurtleBeach VelocityOne Pedals, RealSimGear G1000 Suite, PropWash Radio Stack, Tobii Tracker 5, Asus Xonar U5 sound card.

April 10Apr 10

Commercial Member

For the maps you may need to delete the map's local cache so it is forced to call for new tiles from the server.

The map's local cache folder is located at:

C:\Users\<UserName>\AppData\Local\GMap.NET\TileDBv5\en

Where <UserName> is your PC’s user name.

Delete the entire folder named "en".

When you say "no PTT", if that means you set a PTT button and when you press it the onscreen PTT button doesn't turn green, then that's a settings issue. Deleting the AppSettings.xml file will force all the settings back to default and clear any file corruption issues that may be causing your problem.

The AppSettings.xml file is located at:

c:\users\<UserName>\AppData\Roaming\P2A_300\Settings\AppSettings.xml

where <UserName> is your PC user name.

Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.

Dave

April 11Apr 11

Author

Thanks for all the work you've done on this Dave. Deleting AppSettings.xml got my maps to show up again. So aside from having to restore all my settings, that part of things is fixed. The microphone and PTT however is still very much broken.

I’ve gone through full troubleshooting and wanted to share a more precise symptom.

PTT works (button registers and plays tone), and TTS works (the “Speak” button returns responses correctly), but speech recognition never triggers. Specifically:

The “Speech Recognition Tone” I use (whoosh.wav) never plays
No utterances are logged even with logging enabled
No recognition events occur at all

This behavior is consistent across:

Multiple Windows user accounts
Fresh P2A configuration (AppSettings reset)

Additionally, Windows Speech Recognition (SAPI) does not launch on this system (control /name Microsoft.SpeechRecognition does nothing), although modern Windows dictation works.

This suggests P2A may be failing silently when the SAPI recognizer is unavailable or not initialized.

Is there any logging or diagnostic mode in P2A that confirms whether the recognizer engine successfully initializes at startup?

Also, does P2A require the legacy Windows Speech Recognition (SAPI) subsystem specifically, or can it use the newer Windows speech APIs?

It seems to me that Windows apparently did an update at some point and broke this. I really don't know how to proceed. Not having voice in P2A is very much a show-stopper for me. Without that, I may as well use X-Plane's built-in menu based ATC.

X-Plane 12, Ryzen 7 9800X3D, Nvidia RTX 5090, Asus ROG Strix X870E-E mb, 96GB DDR5 (6800MHz), 4TB SSD, Triple Monitor 1440p, Windows 11, FliteSim CLS-120 Yoke, Honeycomb Bravo, TurtleBeach VelocityOne Pedals, RealSimGear G1000 Suite, PropWash Radio Stack, Tobii Tracker 5, Asus Xonar U5 sound card.

April 11Apr 11

Commercial Member

P2A uses its own instance of the Speech Recognition engine included in the language. After installing the English-US language, you have to go to the options on that language and specifically press the Speech button to install the Speech Recognition engine. Once that is done, P2A can create an instance of it when you connect or try and use the Speech Trainer.

It also makes a night and day difference if you do the somewhat tedious task of going through Training for all 10 of the "controllers" in the speech trainer that comes up when you press the "Train" button on the Language Trainer (accessed from the Utilities tab of Settings). This training must be done anytime you change PCs or reinstall Windows. It is a Windows speech training. After that, you would see at least a 3 or 4 fold improvement. Some have seen even more improvement.

Dave

April 11Apr 11

Author

I went a step further to isolate this.

Clean reinstall of P2A (AppData\Roaming\P2A_300 deleted, no settings restored)
English (US) speech components confirmed installed (Basic + Enhanced)
Mic/PTT/TTS all working

Result is unchanged:

No whoosh tone
No utterances logged
No recognition events

This system was working previously and the only change during the period it stopped working was Windows updates.

Given that a clean P2A install behaves the same way, it seems like P2A is unable to instantiate the recognizer on this system rather than a configuration issue.

Is there any logging or indicator that shows whether recognizer initialization is succeeding or failing?

Edited April 11Apr 11 by snomhf

X-Plane 12, Ryzen 7 9800X3D, Nvidia RTX 5090, Asus ROG Strix X870E-E mb, 96GB DDR5 (6800MHz), 4TB SSD, Triple Monitor 1440p, Windows 11, FliteSim CLS-120 Yoke, Honeycomb Bravo, TurtleBeach VelocityOne Pedals, RealSimGear G1000 Suite, PropWash Radio Stack, Tobii Tracker 5, Asus Xonar U5 sound card.

April 12Apr 12

Commercial Member

Yes, there are log entries when you connect successfully and the Speech Recognizer is installed correctly you should get some entries in the log file like:

Based on what you are saying, it sounds almost more like an issue with P2A thinking the Radio is Inoperative.

Check your Aircraft Profile for the aircraft you are flying. At the bottom of the Acft Performance tab, check the 2 options to "Ignore Battery Switch" and "Ignore Avionics Switch".

Save the profile and then try the radios.

Dave

April 12Apr 12

Author

Progress. After deleting and recreating my aircraft profile (I guess it had gotten corrupted), the log now shows:

User Names Found
LoadGrammar Succeeded
Started Listening
Stopped Listening

So the recognizer is now initializing and entering listen mode on PTT.

However, I still get no recognition result at all:

no speech-recognized tone after PTT release
no utterance logged
no recognized phrase or rejection line in the log

This seems to have moved past recognizer initialization and into a no-recognition/input issue. Is there a specific log entry I should expect for a rejected utterance, or anything else I should check to confirm P2A is actually receiving speech audio during the listen window?

X-Plane 12, Ryzen 7 9800X3D, Nvidia RTX 5090, Asus ROG Strix X870E-E mb, 96GB DDR5 (6800MHz), 4TB SSD, Triple Monitor 1440p, Windows 11, FliteSim CLS-120 Yoke, Honeycomb Bravo, TurtleBeach VelocityOne Pedals, RealSimGear G1000 Suite, PropWash Radio Stack, Tobii Tracker 5, Asus Xonar U5 sound card.

April 13Apr 13

Commercial Member

Using the Speech Trainer utility, you can use the on-screen PTT, say a phrase and if P2A hears you, the Replay button will be available and you can press that to hear what P2A can hear. If it does not hear you, the Replay button will be grayed out.

Did you check to see that the Ignore Battery Switch and Ignore Avionics Switch were checked in the Aircraft Profile for the aircraft you are flying?

Dave

April 13Apr 13

Author

To consolidate where things stand so we don’t keep circling the same items:

Clean reinstall of P2A (AppData cleared, no prior settings restored)
English (US) speech components installed (Basic + Enhanced)
Default aircraft profile configured
“Ignore Battery Switch” and “Ignore Avionics Switch” both enabled
PTT and mic working
Ran Speech Training once

Log now shows:

User Names Found
LoadGrammar Succeeded
Started Listening / Stopped Listening

However:

No recognition result is ever returned
No utterance logged
No recognized phrase or rejection line

So the recognizer is initializing and entering listen mode, but nothing is coming back from it.

What log entry should I expect for a rejected or unrecognized utterance, and is there any condition where the recognizer would listen but never return a result?

X-Plane 12, Ryzen 7 9800X3D, Nvidia RTX 5090, Asus ROG Strix X870E-E mb, 96GB DDR5 (6800MHz), 4TB SSD, Triple Monitor 1440p, Windows 11, FliteSim CLS-120 Yoke, Honeycomb Bravo, TurtleBeach VelocityOne Pedals, RealSimGear G1000 Suite, PropWash Radio Stack, Tobii Tracker 5, Asus Xonar U5 sound card.

P2A is slowing dying

Featured Replies

Create an account or sign in to comment

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)