Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

application freezing in the middle of the flight

Featured Replies

Hi Dave,

I'm using the latest version and I cannot complete a flight because of application freezing. I don't use any other 4th, 5th windows voice refer to 

 

My flight plan is from ZSSS to ZSHC, everytime before arriving the TOC, the P2A application get freezing and shows the blue circle (windows mouse cursor) and stop to output logs.

Then I restart P2A, import the same flight plan and connect again, then I got the following logs:

The following is part of my log (It seems there is an infinite loop before I force closing the P2A application)

 

===================== log ===========================

Filed STAR: SUP11A - RW07 - SUPAR
Filed APPR:
Filed APPR Trans:
Filed Cruise Alt: 18000
File Descent Rate: 1200
End FPLFile 07/03/2018 01:28:33
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:33 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:34 Trigger:ReachedArrivalSetup
RespondToFlightTrigger 01:28:35 Trigger:ReachedArrivalSetup

 

=================end log ======================

Thanks!

 

  • Commercial Member

Can you please email the entire log file to me at [email protected] 

I suspect that with that short flight you may be reaching the point for calculating arrival information before you are done with the SID and climb out, which would cause that event to be fired repeatedly as it is.  You can try flying at a lower altitude or using a slower groundspeed or lower descent rate to be sure the TOD is well beyond the TOC and end of the SID.

Dave

  • Author

Hi Dave,

Thanks for your quick reply.

I just turned down the flight atitude from FL180 to FL80 to make sure I can finishing the SID far before reaching the TOD, and it seems no freezing anymore.
WIll do more test filights to make sure it is the root cause.

Thanks again !

Hmm, i am having the same problem here, flying KLAX to KLAS.  It's a direct SID to STAR route.  Flight level was 290. At some point, the app just freezes, and i have to kill it.  I will redo the flight and try lowering the altitude as well.

Joe

 

  • Commercial Member

Joe,

I don't believe altitude is going to fix the KLAX-KLAS problem.  That route is plenty long enough for a FL290 cruise altitude.

Please email me ([email protected])your P2A Log file for the flight that had a problem and I'll review it.  

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.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.