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.
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!
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:
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.
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.
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.
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!
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!
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.
