Navigraph AIRAC Cycle for 2024 Missing Waypoints in the Sim

I generated a Flight Plan for the Vision Jet via SimBrief:

When I import this into the Vision Jet via the integrated SimBrief tool I get:

If I try to manually add the missing waypoints WIGGL, HAGRO, and CASRA within V25, they will not resolve:

This is what I see for the missing waypoints – “Searching…”:

I also tried searching for PRB and PXN, which it also couldn’t find. It was able to find SNS, LIN and TURLO.

I’ve been unable to utilize the Navigraph AIRAC successfully since the beta was released, as I have had issues such as this with every attempt to use its data.

Hello! Welcome back to our forum!

Hmm, this is puzzling. Here is what I get if I follow your steps - with Navigraph AIRAC 2413 rev.1 beta installed:

Everything looks correct here. To me, it sounds like the Navigraph AIRAC was not correctly loaded in your case due to ordering issues. We shall dive deeper into this specifically to determine what has changed in MSFS2024, but this is about as helpful as I can be at the moment!

Kind Regards,
Malte

We actually have a related bug report for the simulator. It looks like the ordering that we set is being ignored, meaning that we are potentially powerless in this situation unfortunately:

Hmm…

I only have the Navigraph 2024 suite of tools installed via the Hub and FSLTL’s models (not FSLTL’s injector) installed in my Community folder.

If I strip everything out of the Community folder except the AIRAC Cycle would that fix this, or is the load order also involving the streamed content of the Base, Deluxe and Premium Deluxe content?

I have no other Marketplace content activated, so other than the aforementioned Community folder items I am running a “vanilla” installation.

Good question - we’d like to know too which is why we have opened the topic in the MSFS forums. You could give it a try! I had it working with only our AIRAC, the G1000 plugin and the SimBrief EFB app installed.

Here’s another thought. Do I use the Package Reorder Tool under General > Advanced Options to change when the Navigraph AIRAC Cycle loads?

Does it need to load first or does it need to load last?

(What is my age-old question, of course, is why this is affecting me and not others… sigh.)

EDIT:

Okay, I used the reorder tool to place Navigraph’s AIRAC cycle to load last and on cursory glance, it looks like it has resolved the issue, for now.

I am happy to hear that it improved the situation! Ideally, we’d handle the ordering for you in the future - once we get a response from Asobo.

You are not alone, that’s for sure. It seems a bit random and the behavior behind it is unknown for us at this moment!

1 Like

It doesn’t seem entirely cured. Even though the changes I made via the Package Reorder Tool stay consistent (meaning every time I open the tool, Navigraph is where I had placed it), upon a quit and launch cycle of the sim it breaks Navigraph’s loading again. I have to open the Package Reorder Tool, move Navigraph one place, move it back, close it, quit the sim and then relaunch the sim to get Navigraph working again.

Sigh.

This isn’t the place, but MSFS 2024… man…

Indeed, this sounds symptomatic with what we have found and reported. The sim is evolving, just… backwards in some cases!

At least there is a workaround for now. I agree that it could have been easier to perform, but hopefully they will see to it from the simulator side! There is nothing else we can do in this case.

Kind Regards,
Malte

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

Hello again!

To whom it may concern: We have now released a revised AIRAC package in the Navigraph Hub that contains a temporary workaround that should fix many navigation data-related issues. Please update and give it a go, then let me know how it worked out!

Kind Regards,
Malte

One thing I noted is the workaround did not delete the normally named navigraph-nav-base & navigraph-nav-jepp folders, so the install ends up with both the originally named ones and the new ones with the !!! & }}} name fixes.

I hand deleted the originally named folders. I didn’t launch the sim with both installed, so I don’t know what the net result would have been if I had.

Yes, this is unfortunately expected! They will disappear the next time that the package is updated. This is due to technical difficulties - we had not anticipated having to rename packages that have already been released!

We did run some local tests with both the old and new folders in the community folder and it worked fine, but to be ”better safe than sorry” it’s probably best to remove the old ones!

Kind Regards,
Malte

1 Like

Unfortunately, the renaming fix still isn’t doing it for me.

I’ve even gone into the Package Reorder Tool and set the two Navigraph navdata add-ons to load at 1099 and 1100 and they are still not loading in an order that successfully gets all the navdata to load.

Here’s a missing waypoint/VOR on a fresh load of the sim. The GNS thinks I’m still referring to PR and the EFB can’t even see PRB:

Every time I launch the sim it’s like I’ve had to roll a 20-sided die for some really small odds of things just going as they “should”. I spend more time screwing around than I do actually flying.

Who knows when Asobo is going to fix this unfortunate mess…

EDIT:

I’m suspecting this mix up with the Navdata loading is possibly due to my enabling an add-on via My library in SU1 Beta. I’m suspecting when we do any enabling/disabling, the entire content list is reloaded and it’s possible when this occurs it mixes up the load order regardless of content.xml indicating custom values for individual items.

Of course, without properly debugging this, I’m just guessing here, but I had no issues whatsoever with Navigraph loading correctly once I’d used the Package Reorder tool to elevate them to 1099 & 1100.

The only variable that I can think of that changed here is the addition of “on-the-fly” enabling and disabling of add-ons with SU1 Beta.

Anyhow, this needs further investigation. Note, I’m just too frustrated by 2024 right now and am focusing on 2020 where I can simply enjoy simming again.

Keep me posted if you delve into this and learn anything.

:slightly_smiling_face:

Hello! Please see this post for an additional workaround that might help:

1 Like

I am still having loading order issues with Navigraph’s navdata.

I have your latest update that adds the “CUSTOM_NAVDATA” tag and I’ve also tried using the package reorder tool to set them to 1099 & 1100, which worked for one quit/relaunch cycle of the sim. Today, on first load I’m back to the missing navdata issues.

I really do not understand what is going on here, and what I need to do to put an end to this once and for all.

I’m using SU1 Beta 1.3.22.0.

(The basic ATC is broken, so I need BeyondATC, which needs SimBrief, which needs current Navigraph data, otherwise I would just run the default navdata for now.)

EDIT:

To reiterate, yesterday, or the day before, I updated Navigraph’s navdata via the hub. I ensured that the previous workaround of extra characters at the beginning of the names versions were deleted.

I loaded the sim and I had navdata.

The next load I did not have navdata. I used the package reorder tool to move the two Navigraph navdata add-ons to 1099 & 1100.

I quit and reloaded the sim and had navdata.

Today. I loaded the sim and had no navdata. I tried moving the two Navigraph navdata add-ons even higher in priority to 1999 & 2000. I quit and relaunched the sim and still had no navdata.

I removed the two priority entries from content.xml for the Navigraph navdata add-ons.

I launched the sim and have navdata.

This inconsistency and confusion over what the fix is, is the concern.

Hi,
We have asked ASOBO/MS in their dev forum, and the answer was to add this additional tag to load the data correctly.

It is possible that this doesn’t work as expected, as there are so many other things in this sim version. In this case, we can’t do anything; we do what ASOBO/MS has recommended.

I’m also not sure if this reorder tool in the sim is really working because, due to their answer to our question in the dev forum and the reference to the SDK, this tool is useless, and you confirm it, too.

Sorry, but we have currently no better answer, nor can we offer any better solution. Again, the package contains all the necessary information to be loaded correctly.

I’m sorry.

Cheers
Richard

1 Like

Thank you. I’m not holding Navigraph responsible here. I just want to keep you informed of what I’ve been trying, so you can report that back to Asobo.

:slight_smile:

1 Like

Here the reference link/answer from the dev forum:

Cheers
Richard

1 Like