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.

On 9/25/2024 at 9:32 AM, Stasiek said:

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.

My FBW A320 has current Navigraph Navdata.

Why are you posting in the Tips and Tricks forum?

 

24 minutes ago, vonmar said:

Why are you posting in the Tips and Tricks forum?

Moved to the main MSFS forum.

On 9/25/2024 at 3:32 PM, Stasiek said:

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.

The A32nx uses the sim nav database, it doesn't care about the efb settings - that's only for charts.

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.

What Cycle date is shown on your FBW A320 MCDU ?

This is what I see (screenshot):

Edit: When you start MSFS and select EDDK do you see MSFS is using the OLD runways?

 

 

Edited September 29, 20241 yr by vonmar

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.

When you start MSFS and select EDDK do you see MSFS is using the OLD runways?

Edit:

Do a screenshot of the default Neo's (correct runways) MCDU showing the Database and dates.

 

Edited September 29, 20241 yr by vonmar

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.

3rd try:

When you start MSFS and select EDDK do you see MSFS is using the OLD runways?

Also:

Jump on MSFS default Airbus A320neo V2 and see which Navdata it is using?

Edit:

Until you can post screenshots you could you do a short video to document what you see.

 

 

Edited September 30, 20241 yr by vonmar

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.

"FBW 32NX navdata., Active nav data base: 05SEP-030OCT MS24090001"

Right.

Do you know the supplier of that Navdata?

 

"MSFS Airbuses have got the right AIRAC"

Do you know the supplier of that Navdata?

 

Have you checked the Default NEO V2 to see what it says about Active nav data base?

Again:

When you start MSFS and select EDDK do you see MSFS is using the OLD runways?

I do.

That is the first indication of a problem with MSFS.

How are you going to use approach navdata for RWY13 to land on RW14 in MSFS scenery?

 

Just checking:

Are you at your PC to check on these items at this time?

Edited September 30, 20241 yr by vonmar

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.

Navigraph and EDDK Navdata information posted here:

https://forum.navigraph.com/t/msfs2020-latest-airac-cycle-2404-missing-eddk-changed-13l-31r-and-sids/15476/2

**************
MSFS2020 needs to update EDDK and other scenery to use current Navdata.

Or, sometimes Payware (new or recently updated) scenery contains current data.

You can still fly into older scenery.
Just edit your current IFR plates to reflect any old data runway / frequency / CRS etc. that must be used.
Can be a bit of a mess.

A320NEO V2 Navdata image:
Do you know who supplies this Navdata?

 

 

 

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!