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.

My First three flights with the NGXu update did not go well

Featured Replies

After loading the Christmas update, I tried to complete a flight between KLAS and KSFO. Attempt #1 ended with a P3D hang about 25 miles out from KSFO. I tried the same flight again, and got the same hang on short final (rwy 28).

Being the hard head that I am, I made a 3rd attempt. I decided to change to the NGXu Long startup state from the custom one I saved prior to the update, so I started a scenario, changed the startup state and exited P3D. I started my saved flight again and verified that it was using the new startup state, It was. This flight literally went haywire while in cruise on autopilot flying straight and level at FL340. I looked away from the screen for a couple of seconds and when I looked up, I was at FL320 and descending fast in a 10-15 degree left bank. Cmd A was on. LNAV had switched off. I tried turning cmd A off. No go. Stayed on after several clicks. I pulled the AP disco bar. No joy. Cmd A stayed on. Then I noticed the captain and FO NDs were tracking about 30 degrees off from each other. I tried the MCP heading knob. The heading bug would not move. I checked for faults. None listed, I started checking FMC pages and noticed lots of blanks on all pages. I aborted the flight.

I recalled reading a post on the PMDG forum that instructed someone to delete all of their custom saved startup states, so I deleted all of them but the 3 NGXu ones. I reloaded the flight and it started up using the same NGXu long state that it did on the previous flight. This flight went perfectly. The only issue I had was that I could not get Cmd B to engage for the ILS - AIII autoland. It would only do single channel so I went manual at 50' and completed a perfect flight.

So... If you are having hangs or odd behavior after the update, delete or move any custom startup states saved on the previous version. I have no idea which one was causing the problem. 

For the technically curious, the hangs in flights 1 and 2 were showing as cross-thread hangs in Prepar3d.exe. My system logs show that these were the only 2 logged (I cleared the logs about 3 months ago).  

   

i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440 

 

  • Author

Just a little update: Everything is working fine. Performance has been improved. Life is good.

i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440 

 

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.