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.

Stasiek

Members
  • Joined

  • Last visited

  1. Hi there. My Fenix A320 in half way of circling procedure freezing cocpit buttons and uncontrolled dive to the ground. After FS2020 SDK latest update it worked well for one flight. Next flight to another airport the problem was back. Any idea why it happens, please?
  2. I have no clue who supply A320neo V2 Navdata. I'm done with that issue and do not care anymore. Still appreciate FBW freeware. Their developers do fantastic job. You have a good day!
  3. Bingo! My apology, vonmar. MSFS shows EDDK 32/14. This is MSFS scenery issue. I think, Navigraph new AIRACs will never coordinate with that right. Thanks for good explanation. Meybe new FS2024 will deal better with that. I'm waiting for. Thanks for your help. You have a good one, vonmar.
  4. MSFS Airbuses have got the right AIRAC. EDDK runway 31/13. The ONLY wrong EDDK runway 32/14(old) is in FBW 32NX navdata. That's the one on your scrrenshot: Active nav data base: 05SEP-030OCT MS24090001(in green). Have you checked it out in there ? Why it doesn't show it as AIRAC instead of mysterious MS24090001 ? Why another FBW plane Boeing 747 Salty has the right navdata(EDDK runway 31/13) and FBW 32NX has not ? Both planes are FBW projects. That's all about that from my side. Hopefully next, coming soon AIRAC will update NX32 navdata correct. I don't really want to create big problem from a little thing we can deal with easy. 32/14 or 31/13 who care. We can sill enjoy our sim. You have a wonderfull time, vonmar.
  5. Sorry, I've never posted screenshots. Managed picture into my windows pictures folder and no clue how to make it with URL address. Will try to learn. Anyway, your screenshot shows FBW 32NX navdata base marked in green as: MS24090001. Jump on MSFS default Airbus A320neo get on the same MCDU page and you should see navdata base marked in white as: AIRAC. Then INIT page, enter flight to EDDK and open Arrivals. There is another FBW aircraft available in FBW Installer: Boeing 747-8 Salty. I think this one has the same navdata base as MSFS default Airbus A320neo. Just compare all of them. Good luck.
  6. Thanks vonmar. I see exactly the same. Just check the EDDK airport data in there, then fire up MSFS A320neo(not Version 2, there is a mess), check up the same airport in its MCDU and you will see the different data. I think, EDDK runway numbers was changed in April this year. Have a nice day.
  7. That's right, gdjak. MSFS A320neo and FBW 32NX nav database should be the same, but is not. Check one airport in Germany: EDDK. 32NX still using old runway numbers(32/14) and not RNAV appr. for that runway. A320neo is using right numbers(31/13) and more RNAV appr. as well.
  8. Hi there. On my FS 2020 I fly A320neo and FBW 32NX as well. I'm Navigraph subscriber with unlimited support. A320neo Navdata looks better, but FBW 32NX FMGC still operate pretty old data. Its EFB is hooked up with my Navigraph account. I think, it should be updated with Navigraph current AIRAC, but in fact it's not. Some airports got runway numbers changed months ago and 32NX sill has the old runway numbers in FMGC Navdata. Needs extra set up ? Anyone knows how to fix it, please.

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.