Try following these steps:
- Rename the
navigraph-nav-basefolder to!!!navigraph-nav-base - Rename
navigraph-nav-jeppto}}}navigraph-nav-jepp
We will shortly be attempting to add this to the official version provided in the Hub.
Kind Regards,
Malte
Try following these steps:
navigraph-nav-base folder to !!!navigraph-nav-basenavigraph-nav-jepp to }}}navigraph-nav-jeppWe will shortly be attempting to add this to the official version provided in the Hub.
Kind Regards,
Malte
Canāt find these folders, are they present offline, or only when streamed? Could you please tell me where are they located? Thanks
Thankssssss! It worked. Iām so hapoy now ![]()
Those are the folders created in the community folder after installing the AIRAC via the Navigraph HUB.
Matteo
Thanks for the reply Matteo.
The folders in my Community folder are named differently, ānavigraph-nav-baseā and ānavigraph-nav-jeppā, so some confusion! I assume these are the folders referred to by @skysail?
Those are the ones I am referring to! Sorry, I used the wrong name. I have now updated the post!
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!
You can always perform these changes manually using the method provided above, but you may also install the latest version instead!
Kind Regards,
Malte
Hello! For anyone still having issues, please see this post for an additional workaround that might help:
This is what Asobo is telling us will fix the issue. We will also include this change in our next AIRAC release, but if you want, you can try it out early by doing the change manually!
Kind Regards,
Malte
No luck with this method either
Do we need to delete content.xml after adding package_order_hint so that it gets rebuilt?
Iām not sure; we have not received any such details from Asobo, unfortunately. Give it a go and let us know your findings! It would be much appreciated!
I discovered that the original nav-base and nav-jepp files and also the new !!!nav-base and }}}nav-jepp .dat files were located in the SceneryIndexes folder.
By deleting the original files the navdata seems to now be working correctly.
I am not sure what you mean by this. The packages should be installed in the community folder - was that not the case for you?
Kind Regards,
Malte
I just opened up the Scenery Indexes folder in the main 2024 folder and there were .dat files there using the original naming format of the base and jepp folders. I deleted these and now the data works.
I think this is some sort of cache used by MSFS; it might make sense for NG Hub to programmatically delete those when installing or updating navdata?
Regards,
Tim
Oooh. Now I understand! Thank you, we will definitely investigate this further!
Possibly! We shall investigate!
@N44383 does this work for you too?
Hello again!
The release of SU2 included improvements to how the simulator handles packages that do not follow the specification. In addition, our AIRAC is now considered stable, and we do not expect any issues while using it.
Is anyone here still experiencing any problems?
Kind Regards,
Malte
I am having some issues still, many seemingly random waypoints and VORs are saying they donāt exist. Everything works fine in the aircraft that have custom installs but anything that uses the default navdata does this. It is seemingly resolved after I delete the aforementioned files in the sceneryindexes folder. I have not tried the original renaming workaround yet