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.

F/O screens turn black after shutdown

Featured Replies

Indeed it does Patrick.  Pull up the elec synoptic page once you're on the ground after an autoland and see the elec system reconfigure itself to the correct configuration when you turn off both FD.  Start up the APU and shut down the engines, it will not interrupt power to the FO side of the aircraft.  As I said, you can also perform the same work around by just hitting AP and then AP disconnect.  I'm not sure where the problem is but I think it has something to do with the AP and autoland.

 

Tim

Tim Gyno

  • Replies 37
  • Views 7k
  • Created
  • Last Reply
  • Author

Again thank you Tim!

 

I will add this to my next answer in the support ticket. I'm sure this will help to solve the problem!

 

Patrick

  • Author

Ok, the ticket is closed now. It is a bug and they are working on it to solve it. For now, turning off the F/Ds before you cut off the fuel is the "solution". It seems to be not easy to fix.

Patrick

  • Commercial Member

Ok, the ticket is closed now. It is a bug and they are working on it to solve it. For now, turning off the F/Ds before you cut off the fuel is the "solution". It seems to be not easy to fix.

Patrick

 

Thanks for submitting a ticket, and thanks for reporting back.

Kyle Rodgers

Tim,

 

Thanks for the "solution". I will try it later. FDs off on my shutdown checklist now.

 

Regards,

Heron Domingues, Jr

Intel Core I7 10700KF, 3.80GHz (5.10GHz Turbo), Gigabyte B460, RAM 32GB, Corsair 750W, GPU Palit RTX 3060, Windows 10 Pro 64., P3Dv5.4.

Boeing777_Banner_Pilot.jpg

  • 1 year later...

I am wondering if there is any update on this. I have been experiencing the same issue, two years later. Should I open a ticket as well?

Cheers,

Zsolt Monostori

1hxz6d.png
kityatyi

I7 6700K 4.6 GHz, MSI Geforce GTX 1070 8GB GDDR5

16GB DDR4 Corsair Vengeance 2666 MHz RAM, 750GB SSD, 1TB HDD

I am wondering if there is any update on this. I have been experiencing the same issue, two years later. Should I open a ticket as well?

 

Cheers,

 

Zsolt Monostori

It wouldn't achieve anything. Two years later there has not been an update to the product other than what was required to implement FSXSE compatibility.  The to do list is still there waiting for PMDG to commit resources to a product update.

Dan Downs KCRP

  • Commercial Member

Patrick,

 

Yes,  turning off both Flight Directors after landing will clear the current fault.  The issue has been confirmed and occurs only after an Autoland.   It has been passed along to the development team to look into for the next update to the 777.

Paul Gollnick

Manager Customer/Technical Support

Precision Manuals Development Group

www.precisionmanuals.com

PMDG_NGX_Dev_Team.jpg

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.