August 2, 20187 yr Did a flight from KSLC to KSEA. All went well until I was told to contact Seattle Approach on 133.65. FO responded, radio changed freq. and checked in. SeaAPP responded "Contact Seattle Approach on 133.65". FO responded and the same thing happened over and over until I reached the end of the star and then it started giving vetors to final. Also the nearby freq window was blank. What gives? James
August 2, 20187 yr Commercial Member James, Make sure you have updated to the latest release. 2.5.0.5 R2. This issue should be fixed. If you still get it, please email you P2A Log File for the flight to me at [email protected]. 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, so if you take the most recent one when you have the error, you should have the correct one. Dave
Archived
This topic is now archived and is closed to further replies.