Hi again Paul,
Thanks for testing - in 99.9% it´s a scenery issue, rather than a navdata issue.
ASOBO/MS has changed the way to prioritize the loading order of third-party sceneries and third-party navdata. That means, both must be fully SU3 compatible, so that this new (by the way great) logic works correctly on the systems.
I can´t say if the 3rd party scenery is really SU3 compatible.
What does this mean (sorry, when it is a little bit technical):
The scenery must have the new attribute package_order_hint set in the manifest.json file. When you examine our manifest.json file, you will see this new attribute with our specified value.
{
"dependencies": [],
"content_type": "SCENERY",
"title": "AIRAC Cycle Base",
"manufacturer": "Jeppesen",
"creator": "Navigraph",
"package_version": "0.1.0",
"minimum_game_version": "1.5.27",
"minimum_compatibility_version": "5.27.0.112",
"export_type": "Community",
"builder": "Microsoft Flight Simulator 2024",
"package_order_hint": "CUSTOM_NAVDATA",
"release_notes": {
"neutral": {
"LastUpdate": "",
"OlderHistory": ""
}
},
"total_package_size": "10453953"
}
This attribute must be set, because this “tells” the sim what kind of package the sim is currently loaded. Again. I can´t say if this attribute is set, but it is worth checking.
Then, it is essential and HIGHLY recommended to delete your content.xml file once. Because also here, there was a change from SU2 → SU3.
We have written an FAQ for this “reset” of the content file:
Also worth trying…
I´m pretty sure that when both “conditions” are set, the navdata are also working. I would start by resetting the content file and checking if that resolves the issue. After that, I would check the manifest.json file to see if the attribute is set. Depending on that result, inform ORBX.
Hope one of these tricks are helpful for you.
Cheers,
Richard