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.

dmb_NiL

Members
  • Joined

  • Last visited

  1. Hello, today I had a qute subtile issue with the great PMDG 777. I do not know if it is caused by a faulty operation by myself, a bug by PMDG or if it works as intended. Yesterday I flew from OMDB to EDDF with a 777F. PFPX suggested two step climbs, the FMC as well. I entered the step climbs as planned via /360S and /380S using the right LSKs on the LEGS page eventhough the calculations made by PFPX and by the FMC almost matched perfectly. Finally everything was working well. Today I was flying a much shorter route, namely from EDDP to EGNX. PFPX again calculated a step climb from FL360 to FL380, somewhat 300 miles before T/D, the FMC did not suggest a step climb. Anyway I entered the step climb by the fix PFPX suggested but the PMDG did not accept it. Strangely there was no error. I was able to enter /380S but the FMC still calculated FL360 for the following waypoints so it looked like this: WPT01 .840 / FL360 WPT02 .840 / FL380S WPT03 .840 / FL360 WPT04 .840 / FL360 and so on. The VNAV page still showed S/C at NONE. If I understand the FCOM correctly it should be possible to override the calculations of the FMC. A step climb was actually possible since the MAX FL according to FMC was FL382 from the beginning. What was really strange now that the FMC did not suggest a step climb eventhough the OPT FL on VNAV page was FL371. When I entered FL380 as CRZ FL manually the calculated fuel at the destination was about 0.4 tons higher so the higher FL has actually been more efficient. Furthermore the FMC did not show a recommended FL on the VNAV page besides OPT FL and MAX FL which it did yesterday when everything was working fine. I conjecture that this has something to do with the short length of the flight. But is this working as intended (e. g. no step climbs within 300 miles of T/D; I was not able to find something about that in the FCOM) or is it a bug? Did anyone encounter such a problem before? Regards
  2. Thank you, at the first look it's great! I'm sure it will be at all the looks to follow too as we know it from PMDG .But I am a bit disappointed by the number of liveries. Hoped to see as much as with the 737-800/900 release. (Personally I am missing airberlin, since it is one of the largest 737-700 operators in Europe, since Easyjet is only operating two 737-700.) Are we going to see further liveries by PMDG or do we have to rely on community painters?Anyway, the important things (systems, modelling ...) are just great as I said, thanks for that :).EDIT: Have just seen that. Reading often helps, just ignore my posting :).
  3. They did: Don't think it will be in 2111 . But I don't think that the 600/700-extension will be released today since the liveries have not yet been published, maybe the SP1.
  4. Hello, first of all I want to say thank you to PMDG for this wonderful addon ;). Just a little thing that I've just seen on a flight. The BELOW-operator on the LEGS-page in the FMC doesn't seem to have an effect. The FMC's descent planning ignores the constraint: If I only type 120 instead of 120B it works: It would be nice if you could consider this for the next update. Thanks :).

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.