No Navigraph navdata in MSFS2024 Longitude?

[Atriuslol]

Not sure if i’m posting in the wrong category; if so, please move it.

It seems that the Longitude in MSFS2024 does not load navdata from Navigraph. Is this a know thing? Searching yields no results neither on these forums or on flightsimulator forums.

Charts are working as expected though.

I have AIRAC 2511 rev.3 and G3000&G6000 v.2.0.7 from Navigraph Hub. Still it loads the default MSFS2024 Navdata from LIDO.

[NAVData]

Hi,

@Atriuslol

Still it loads the default MSFS2024 Navdata from LIDO.

One question: How do you determine that Longitude loads the Lido data instead of our own data? Do you look for a specific waypoint, navaid, or how do you identify that the aircraft uses the stock Lido data?

Cheers,
Richard

[Atriuslol]

Hi Richard,

Many thanks for the swift reply.

I did a flight to ENSB yesterday and got runways 10 and 28 with RNP A and Visual approach as options. These are rather old (09 and 27 current) and there are multiple other approaches available.

Checked the CRJ900 and have the correct navdata:

Edit:

It actually looks like the Longitude loads an old AIRAC as well? MSFS Flightplanner has updated procs atleast.

[NAVData]

Have you installed any 3rd party scenery, especially for ENSB, or do you use the stock scenery?

Cheers,
Richard

[Atriuslol]

No custom scenery installed for ENSB - using default MSFS2024.

[NAVData]

… but other 3rd party sceneries, right?

When yes, please look here and try it:

FAQ - MSFS2024 (SU3 and above) - airport, procedure, waypoint, 3rd party & flightplan import issues

There is a new loading order logic since SU3; therefore, it is essential to reset your content.xml file when, for example: You miss airports. You miss procedures. You miss waypoints. Legs are missing from the nav devices. There are third-party scenery issues. There are flight plan import issues. … This file will be automatically recreated at the next simulation start. You will find the content.xml file in the following locations (Note, the location has changed since SU3 - it´s now in a sub-f…

I´m pretty sure, that this is a 3rd party package issue somewhere on your system.

Cheers,
Richard

[Atriuslol]

Ah yes, sorry. Have 3rd party sceneries installed for other, unrelated airports.

Seems strange that it works properly with the CRJ and other aircraft, but not the Longitude if this was a 3rd party package?

[Atriuslol]

Removed all 3rd party mods and tried again. Same problem with both Longitude and PC-24.
ENSB is the only airport i’ve experienced this with thus far. It seems that the default MSFS data still uses the old runway designators, which might be conflicting with your navdata?

I now assume this is the same problem as Missing procedures at ENSB - #2 by NAVData

I guess it works fine in the CRJ due to the dedicated addon package in Hub?

[NAVData]

Ahhhh sorry, my fault. I have not read your initial posting correctly. Sorry for that …

Yes, when the stock scenery offers outdated runway-idents, you can´t see the approaches which we offered because the sim can´t assign the approaches (with the new idents) to the existing outdated runway idents. That is an MSFS limitation, sorry. We cannot change existing runways, I’m afraid.

However, this is also evident in the Lido data, as shown by the MSFS flight planner, which lists the correct runways. Nevertheless, this discrepancy does not align with the stock scenery in the sim. Similarly, Lido also has this exact issue.

Sorry, you can´t do anything - this is an internal SIM issue. Sorry too for the confusion …

Cheers,
Richard

PS: You can try to find a freeware scenery for ENSB that has the correct runway-idents then you will also see all approaches

[Atriuslol]

No worries at all, Richard. I should have been more specific in my first post.

Thanks for your swift assistance!

[NAVData]

Hi again,
I have tried to find a freeware scenery …

When you use this scenery, you will have

1. the correct runway-idents 09/27
2. and all the approaches which we offered

Runway 09:

Runway 27:

… and here from the Longitude:

I have used this scenery:
https://de.flightsim.to/file/93669/ensb-svalbard-airport-enhancement

But please (if you want to try it) replace this manifest.json file to make this scenery SU3 compatible.
manifest.json (509 Bytes)

Replace the existing file with the file that I have uploaded here. Should also work on your system. This is important because the

"package_order_hint": "CUSTOM_AIRPORT"

is missing in this file, and it is an important tag since SU3; it should be present in any 3rd-party scenery.

Cheers,
Richard

[Atriuslol]

Hi again Richard,

Thank you so much for your eager support. I had decided to purchase the new ENSB scenery from iniBuilds, so i just went with that. Using it, the procedures loads as expected and i got a great scenery at the same time.

Thank you again!

[NAVData]

You are welcome. Thank you for your feedback, positive comments, and kind words. Much appreciated…

Enjoy your new scenery, and let us know if you have any questions.
Richard