A very minor bug that I've come across twice now, so thought it worthwhile to mention here.

I love this feature: a Pilot2ATC controller decides to provide approach vectors to the runway rather than let me fly the (longer) STAR.

However, the controller mentions a completely different airport name in the communication, as you can see from the screenshot.

See the bottom-right corner: in this case I was flying into Rotterdam The Hague airport, but the controller mentions Muenster Osnabrueck airport. This seems to be at that moment one of the closest airports - maybe that helps in finding and fixing the bug. Otherwise everyone is fine, great even. I just kept flying and landed at Rotterdam, no problems.

https://www.dropbox.com/s/lfdo0acj8iq2ht6/Schermafdruk 2017-10-08 00.50.14.png?dl=0

 

Thanks for the report.  It does sound like a bug.  I'll try and squash it.

Dave

Nothing obvious found.  If you still have the Log file for that flight, it might help narrow down the cause.  Please email it to admin @ pilot2atc.com so I can manipulate it.

Log files are located in:

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

where <UserName> is your PC user name

A new one is created each time you start Pilot2ATC, so if you take the most recent one when you have the error, you should have the correct one.

Thanks,

Dave