BartonW

OK, what I did was make a backup and then changed the "SpeechOutputKeyCode" from 90 to zero and "SpeechOutputKeyCodeText" to blank and that seemed to work. Did a test flight and seemed to behave itself. Thanks!

I checked the AppConfig.xml file and found the following. I'm think issue is with "SpeechOutputKeyCode". Note that I did recheck (again) the configuration in P2A and confirmed only Speech Assist is defined.: <AppSetting> <Name>SpeechOutputKeyCodeText</Name> <Value>zZ</Value> <LastChanged>2022-01-07T08:56:55.129151-05:00</LastChanged> </AppSetting> <AppSetting> <Name>SpeechOutputKeyCode</Name> <Value>90</Value> <LastChanged>2022-01-07T08:56:55.1321512-05:00</LastChanged> </AppSetting> <AppSetting> <Name>SpeechOutputKeyMod</Name> <Value>0</Value> <LastChanged>2022-01-07T08:56:55.1331517-05:00</LastChanged> </AppSetting> Knowing that programs don't like end users tampering with app configuration files, is there an issue here and if so, what change should be made? Bart

Dave, I rechecked my P2A configure panel and the only thing that is defined is "W" for Voice Assist. Just to be sure, I also went ahead and clicked on all other options ``Clear" button just to be sure something behind the scene was not there but that didn't make any difference. I also checked and confirmed that the "Require P2A or SIM Focus" is checked. Now as it is, I am able to get around this because the upper case "Z" does work and so far the SIM does not seem to care about the case. Also a side note. The Speak Assist hotkey of "W" works sometimes and others it does not. I am still trying to determine what the pattern to this and thus have not reported it. Don't think that it impacts the other problem but figured I would mention it. Barton

Have a strange issue that appears to be Pilot2ATC related where I lose ability to type "z". Note that upper case "Z" still works. 1. I create and open a simple text file using Windows notepad. 2. I start MSFS2020. As part of that process, it automatically loads PSUIPC 7. 3. Switching to notepad, I can enter "z" fine. 4. The I run Pilot2ATC and while it is still initializing, notepad is fine. 5. Once P2A is functioning, going to notepad, nothing happens when typing the letter "z" . However typing upper case "Z", it works. 6. Close P2A. 7. Notepad now accept "z". NOTE: 1. I am using P2A beta 2q. 2. The lack of ability to enter "z" applies other places as well, not just notepad (for example inside the simulator). 3. My P2A configuration DOES NOT use the "z" key as a hot key. and in fact only hot key is "W".

OK, thanks!

Request for a new option for Pilot2ATC. Can we have an option to disable the use of the voice recognition or at least allow the program to connect to the simulator without a microphone? Currently the program when it tries to connect the simulator, it will show a message if no microphone is detected and then not connect. However if a microphone is detected, then of course it connects but the program can be run fine without actually using it. Instead we can use the "SayIt Speech Assistant" to do the same thing as normally would be done with our voice. And with the "Favorite" feature in the beta version of Speech Assistance, it makes the use of that feature so much better! Now I know the question arises as to why this request, given that one of the big features of the program is the voice recognition. In my case, due to medical issues, my voice is rather raspy and voice recognition software often has trouble fully understanding me. This is not the fault of the program or any other speech recognition but simply that the voice is not clear enough. Pilot2ATC is a great program and I love to use it but it is frustrating that it does not properly understand me because of the above issue. So please, if possible, provide a way to use the program without the voice recognition. Thank You for your consideration.

Make sure that you do not have voices assigned in the specific controller fields but that they are blank. As I understand it, if there is a value there, it will always override the random voices. I assume this is by design so that for example, you could assign a specific voice to copilot and always get the same one. Hope this help

Email has been sent.

Have an ongoing issue (tried a couple of times) with the flight plan shown below using cruise altitude of FL300. Using version 2.16.1.3_x64 on Window 10 and using "Co-Pilot Responds" option enabled. Also using the latest Navigraph data. The initial flight is fine up to the point that ATC should give a decent command with P2A Map shows proper decent point and the plan detail in P2A also showing the decent point. Howver instead of giving the command, nothing happens for a little while past that point and then it gives a "Cleared for ILS runway 28R" while I am still at FL 300! So decided to go ahead and descend on my own and follow the flight route and was not alterted by ATC about altitude or anyting else. After passing over the airport (approach was opposite direction from current flight path), was contacted by ATC to call the tower which Co-Pilot did. It then cleared me for landing runway 10! I went ahead and finished following my flight plane landing on Runway 28R which once done, the normal exit runway when able was given followed later by taxi to parking. Barton Whisler ====================== Flight Plan ================== 1100 version CYCLE 2013 ADEP KPIE DEPRWY RW36 SID PIE9 SIDTRANS PIE ADES KFLL DESRWY RW28R STAR FORTL7 STARTRANS PIE APP I28R NUMENR 2 1 KPIE ADEP 11 27.9087 -82.6865 1 KFLL ADES 65 26.07167 -80.1497

Thanks gordong! Had same issue of gtn 750 not working on the Carendado Citation II however after using your tip about using the plug in drop down and a little bit of playing around, got it working again - GREAT!