Hi,
Thank you for your posting and for sharing your thoughts.
What you describe is a typical 3rd-party scenery issue and has nothing to do with our data. I will try to explain it without making it too technical.
With MSFS2024 SU3, MS/ASOBO has changed how and in what order 3rd-party packages are loaded. To this end, they have introduced a new setting for 3rd-party developers called “PackageOrderHint”.
Here the original text from the official SDK:
This is used to give the package order hint, which the VFS uses to place the package in the correct place in the load order.
According to the SDK for navdata updates, you should use:
CUSTOM_NAVDATA(These are 3rd party packages that replace all the navigation data for the world)- and/or
CUSTOM_NAVDATA_PATCH(These are 3rd party packages that override navigation data fromCUSTOM_NAVDATApackages)
CUSTOM_POI or CUSTOM_POI_PATCH are for POI elements/objects and not for navdata.
We use the navdata package order hint for our data, as specified by the SDK.
So, what does this mean for 3rd-party scenaries now? That also means 3rd-party scenery needs this package order hint, so the sim knows how to load them in the correct order. When this PackageOrderHint is missing, the sim loads such packages at the end.
You wrote that it is an MSFS2020 scenery. I would expect that this scenery does not have this PackageOrderHint because this information does not exist in MSFS2020, which results in such behavior. The package will be loaded at the end, and therefore, you “overrule” our navdata package.
Since SU3, it is important that this PackageOrderHint is set correctly in all 3rd-party packages, not limited to sceneries.
It is not what we have in our hands. We follow the rules exactly from the MSFS2024 SDK, and we set this flag correctly (therefore, it works without 3rd-party scenery because our package “overrides” the stock scenery navdata information).
In other words, the solution is to go back to Orbx and tell them they must add this PackageOrderHint per the MSFS2024 SDK. We may, and we can´t do this; this is clearly a fully reproducible issue on the 3rd-party scenery. There are tons of such reports here on our forum, and the solution has always been an incompatible 3rd-party package.
This FAQ is from September 2025, where we offer a step-by-step instruction on how you can solve such issues on your own. Again, it is not navdata related - it´s a ddesit’s issue in the 3rd party packages.
Hope that helps,
Richard
PS: as a fast test - let the 3rd party scenery installed - go into the library and turn both our navdata packages on/off - after that, look if the procedures are visible/selectable or not … normally, you should see all procedures as with the stock-scenery because you force the sim to load our packages first.