Dave-Pilot2ATC

If you don't see the microphone, then you need to press the Options button. A window will open and there should be a "Speech" option. Press that button and it should install the Speech Recognition engine and display the microphone icon after the Options window closes. Dave

The snippet from the log file indicates the Speech Recognition engine is not loading. This would not be affected by what region you are in. Regions drive what Chatter files play when you are using the ATC Chatter feature. If it works sometimes and not other times, that would indicate a problem during connection. Disconnecting and reconnecting to the SIM might fix it when it fails the first time. A good test would be to try using the Speech Training utility which works without connecting to the SIM. If that works, you know the speech engine is installed correctly in Windows. You would have to use your voice and say something simple like "Say Altimeter" to see if you are recognized in the Trainer. Dave

Try downloading and installing the latest P2A update. This should replace any corrupt files, etc. IF that doesn't work, check your installation of the English-US language and speech engine in Windows. See the User's Manual for details on how to do that. Dave

If you mean you are not hearing a response from Clearance, except you did get one at KMSP, then most likely it's a problem with voices. Microsoft disabled the free use of their Online voices in desktop applications other than their own. ATIS is working because you selected a non-online voice for it. So, you will need to uninstall all the online voices. See the V3 Downloads page of the website for instructions on how to do this. Dave

There is an issue with the interpretation of "X ray" that will be fixed in the next update. Dave

Some specific aircraft may not allow P2A to swap frequencies, so you have to do that in the cockpit. You may even have to set the standby frequency in the cockpit. Try using one of the stock GA aircraft in your SIM to rule this cause out. Also, the SIMs have settings that allow them to control the frequencies. These are in the ATC settings and should be turned off, along with any other ATC settings. Sometimes, just swapping the frequencies a second time, or Disconnecting and Reconnecting will fix this sort of issue. Dave

P2ATCv3 Update_3.0.0.0_RC3 Fixes Arrival and Approach start issues. Fixes descent start and vectoring issues. Fixes Copilot control of Coms issues that were mostly found in X-Plane. Fix Activate Approach view of intended vector/approach track. More fixes to taxi request/responses for specific gates or FBOs, etc. Fixes many other bugs.

P2ATCv3 Update_3.0.0.0_RC2 Fixes Waypoint tracking. Fixes arrival and approach scenarios with and without vectoring. Fixes missed descent instructions on certain approach scenarios. Improves handling of approaches when Departure and Destination are close to each other. Fixes missing Copilot Speech options in certain scenarios. Fix ATC Controller handoffs in certain scenarios. Fixes handling of taxi requests to named parking locations. Fixes many other bugs.

You can set the aircraft type and color in the Aircraft Profile Acft Info tab. To open the Profile, Click on the Profile button to the left of the AutoPilot button in the same area as the Connect button. Dave

That specific error message is normal and does not affect the operation of P2A. Strangely, nothing has changed regarding the connection to a remote X-Plane installation. You mentioned in the original post that unchecking the setting "Run on X-Plane Remote Computer" allowed P2A to connect to X-Plane but just the traffic didn't display. Is that still the case? Dave

P2A V2 has an alternate "Slow" version of the P2ALink that can be installed. It runs less frequently and therefore has less of an impact on XP. You can check that option in Settings and then reinstall the XPLink plugin and it should load the "Slow" version. V3 doesn't use any plugins and therefore has very little, if any, performance impact on XP. Dave

Thanks Bob. TOD does get recalculated during the flight, which might explain the large change. I believe the problem with the early descent is a bug in the waypoint tracking that makes ATC think the aircraft is further along than it actually is, but it could be the TOD calculation being off also. I'll look into both. Recent AIRAC updates have changed some Center controllers to Radar Control controllers which is what causes Washington Control instead of Center. That's on the list to fix also. And you're right about the "radar contact" only being done once. You should be getting only a greeting like "Good afternoon" for subsequent controller handoffs in most cases. If somehow the controller loses contact or can't find you on his busy screen, he might ask you to Squawk Ident and then you would get another "radar contact" call. So there must be something wrong in that area as well....possibly not enough randomness in that possibility. Thanks for the detailed reports! Dave

Thanks Bob. I'll try flying the flight and get it fixed. There have been issues with the waypoint tracking where it jumps ahead and triggers these early events. Dave

Thanks Bob. Strange bug. I'll check it out. Dave

Thanks for the report. I'll look into it. Dave