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.

SKeller

Members
  • Joined

  • Last visited

Everything posted by SKeller

  1. But then you would need to release the Pause button in order to press your PTT button for your readback, so the FO would continue his speech while you're talking to ATC.
  2. No frequency dialing necessary. You only need to enable the correct button in the NGX's audio panel. See the Main Ops manual, page 38: Note: To communicate with the Ground Crew, press the FLT button on the Captain’s audio panel [...] The screenshot on page 39 shows the button(s) to press. Hope this helps, Stefan
  3. It will work, don't worry. The installer simply does not recognize SP1D and throws this message, but if your WX Radar is working, you have the latest build, and FS2Crew will run fine.
  4. Simply ignore the error message. FS2Crew will work fine.
  5. Ah, NOW I'm with you I've been flying the NGX since it's release, and I never observed this problem. Could this be a problem specific to FSX Steam? I'm on FSX Boxed. Maybe the Steam pilots have an idea. But what you're saying is that pressing B will return different results depending on whether you're in the PMDGs or a default aircraft? This is very strange indeed... Last try: Do you happen to have two weather engines active and running at the same time? E.g., you use ASN and forgot to uncheck the IVAO weather in IvAp Configurator?
  6. Maybe I have completely misunderstood your problem? Are you saying that the altimeter reading at the bottom right corner of the PFD does not match the reported QNH, but you think it should always match without any input by you? Is this what you're asking for? If so: It doesn't. And by the way, since you played the experience card: I've been an IVAO member for 14.5 years now.
  7. Please trust me: There is no difference whatsoever between online and offline in this respect. And YES, you need to calibrate your altimeter manually. Always. That's also true for real life by the way. Your wheather in FSX will change automatically, yes. But your altimeter setting will NOT. And as said above, it's normally only three times you need to calibrate your altimeter during each flight: 1. On ground at your Departure airport prior to takeoff 2. When passing TA in climb 3. When passing TL in descent And each time, you need to do so manually.
  8. It seems there's some kind of misunderstanding how altimeter calibration works ;-) Pressing B will set the altimeter to the local QNH at your current position. It will not re-calibrate automatically when the QNH changes later. Remember that you probably pass through different weather conditions with different pressure in cruise. Basically what you do is the following: 1. Set local QNH at your Departure Airport. 2. After takeoff, when passing Transition Altitude, set standard pressure (1013/29.92) and leave it there during climb, cruise and most of your descent, regardless of what the actual ambient pressure is. The idea is that all aircraft above TA use the same reference point for their altimeters. 3. When passing Transition Level during approach, set local QNH again (hit 'B'). That's it
  9. I can help only with 1): The altimeter will *NOT* automatically calibrate! The barometric pressure is not read by the aircraft at startup. The altimeter setting of the NGX/777 will always be the value that was saved with the panel state you use as your startup state. So, once the aircraft and live weather has finished loading, you need to manually calibrate the altimeter to local QNH (simply pressing B on the keyboard will be the quickest way).
  10. If you have the boxed version of the NGX, then the key on the DVD sticker is the one you need to enter at the Aerosoft site. If this does not work, you should contact Aerosoft rather than PMDG. Good luck!
  11. Because when flying online on IVAO, you are normally assigned an individual squawk code. This makes sure that your callsign is displayed in the aircraft label on the radar screens (even when the transponder is in Standby), which is really handy (from the ATC point of view, that is). Setting transponder codes of 1200, 2000 and 7000, however, will make your callsign disappear from the label. Instead, the transponder code will be displayed. I know that by the time FS2Crew sets the transponder, you are parked at the gate. But being a TWR/GND controller on IVAO myself, I can really say that it would help a lot on busy aprons, if arriving aircraft kept their callsign in the label until they disconnect from IVAO. Not a big deal, of course. I was just thinking you might consider it now that you're recoding tons of stuff anyway... :Big Grin: Oh, and thanks for the news on ground crew handling. Sounds excellent. Best regards, Stefan
  12. Hi Bryan, While you're being at it ... Would it be possible to prevent FS2Crew Reboot from resetting both the transponder code and the CFG settings for PWR/AIR SRC once you arrive at the gate? In the current version, as soon as you shut down both engines and answer the call by the ground crew, the transponder resets to 2000 and the PWR/AIR SRC resets to APU, regardless what was selected before. So, in order to have the ground crew connect the GPU, you need to open the CFG panel and select EXT/AC first, before you can issue the "Please connect the GPU now" command. It would be really great if these two settings were kept as they are during the entire "stay on board" I'm looking forward to Reboot!!! Thanks and best regards, Stefan
  13. Will the panel states we created with the previous SP1d work in the latest version or do we have to re create them? Thanks
  14. see here: http://forum.avsim.net/topic/464558-13mar15-aerosoft-dvd-and-download-customers-and-fsx-se-compatibility/#entry3199102
  15. Hi Richard, Yes, it is. Edit: Plus, I *think* that "Aircraft casts shadow on itself" (or whatever the option is called in English - I have a German version of FSX) must be enabled in the FSX settings as well.
  16. Did you delete the entire [sIM]\PMDG folder after uninstalling? Because I removed only the PMDG 737 NGX subfolder and left my NAVDATA folder untouched. After installing SP1d, my current AIRAC was still there.
  17. It does not expedite the release, that's for sure :-) It refreshes your browser.
  18. Hi Bryan, I am wondering if the current version of FS2Crew for the NGX will work with PMDG's SP1d which is due to be released very "soon". I'm not talking about Steam, just the regular FSX version. Thanks and best regards, Stefan
  19. I have a (maybe dumb) question: Will SP1d be available for both the 800/900 and the 600/700 at the same time?
  20. My thoughts as well... Let's hope that Bryan from FS2Crew will do his magic on this to provide us with an F/O.
  21. Better be easy on your F5 key. I'm not an English native speaker, so I might be wrong, but I don't think that Robert meant to say the SP will be released 6-18h *from now*, but that he will give us notice 6-18h prior to release.
  22. This, however, would mean an epic fail
  23. I wonder if people who report performance increases in FSX:SE might not take into consideration that they are (most likely) comparing a vanilla SE install with a several years old and tweaked to death FSX Boxed configuration? Somehow I'm not convinced ^_^

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.