I know this has been mentioned before but this bug is the one thing that is stopping me from investing in this otherwise excellent program. I am on the trial version and am hesitating to buy because almost every time that I reach a hold point  before take-off (I fly mainly from EGLL with the ZIBO 737-800), the program DOES NOT transfer over to Tower. My MIC is fine, everything has been OK up until then, I have made input requests etc when I need to and I have received the required responses ( which my co-pilot has handled efficiently...). But  then as I follow the correct taxi path and reach the runway, absolute silence. The radio has transferred to the right TWR frequency but then nix, nada, zilch. After waiting (and waiting...) I try various requests myself (Call sign Holding xxx, Ready for departure etc etc) but nothing happens. The only time it worked was when I pressed one of the other TWR frequencies and I heard  a bong type sound and only then did TWR contact me. The other time it worked was when I rebooted the program while at the holding point. Most of the time it has not worked. It's really irritating because once I do get responses and am up and away it is very satisfying. But this bug.... ugh

More frustration. I tried a different airport (EHAM) and the program gave me a COMPLETELY wrong taxi direction. I wanted (and was approved by ATC) 18L and it directed me to 36L! On the other side of the airport... AND when I tried to contact TWR again, nothing happened, no response and I tried all the different speech combinations.

This program is just too buggy for me to buy it. If I am going to pay a - not insubstantial - amount of money for a product, I expect it to work 99% if not 100% of the time. I don't want to have to reboot it every time it fails ( and it still doesn't work) or to waste my time scouring these forums to try and find a fix to a problem which should not be happening in the first place.

It's a shame because when it DOES work the couple of times I have succeeded, it does what it says on the tin. But there are just too many times when I have ended up frustrated and irritated and left standing (literally) not knowing what has gone wrong when I know I have carried out all the procedures correctly. 😞

I'll keep an eye out for an updated version in the future to test, hoping it will behave better then...

 

 

The trouble you're describing may be a problem with the taxiway definitions not matching the scenery definitions in whatever SIM you are using.  Have you updated these airports using TaxiMnt in P2A?  Instructions for this are in the P2A Operations manual in the Documents folder of the installation.

If you email your latest P2A log file where you had this problem to [email protected], I'll have a look and see if there is a bug, but most likely, it is a problem with the data.

P2A Log files are located in: 
C:\Users\<UserName>\AppData\Roaming\P2A_200\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.  

Dave