After extensive testing and narrowing down I’ve discovered an issue with Navigraph and PilotPlus EGTK Oxford airport in FS2024. These two products work in perfect harmony in FS2020 and both are marked FS24 compatible
In a nutshell, when Navigraph is installed all runway, apron, and taxiway markings as well as lights and hold short points disappear to be replaced by ugly grey blobs. Once Navigraph is removed all works as designed.
The person on our team that would have the required knowledge in this subject is currently on vacation. We try to get to topics as soon as possible regardless, but sometimes we are limited in resources! Sorry for the delay.
In the meantime: Have you installed this scenery through the marketplace or externally?
If it is installed externally, could you open the folder containing this scenery addon in your Community folder and find the manifest.json, then upload it here? I do not have this scenery and therefore can’t reproduce the issue, but I could at least see if this scenery is really MSFS 2024 compatible based on this file
Hi,
Sorry for the delay of this answer but as Malte wrote, I´m currently on vacation.
I´m pretty sure that this issue is due to the wrong package loading order. You can´t really compare MSFS2020 with MSFS2024 because ASOBO/MS has changed the logic of the loading orders. In the past (MSFS2020), you controlled all over the content.xml file. That’s not the case in MSFS2024. In MSFS2024, a special flag (package_order_hint) must be set in a manifest file (package_order_hint). That’s what we must set, as well as the third-party scenery designer.
When this is not set, the packages will be loaded in the wrong order (or they can), and the result will be missing waypoints, procedures, etc.
You can test it by yourself. When you remove the 3rd party scenery, you can possibly see the EGTK airport without any issue.
I don´t know what FS2024 compatibility means but this flag is new in SU1 an it must be set, that the packages can be loaded correctly. So, the question is, is this flag set or not?
We still have this flag set as navdata; therefore, I´m pretty sure this is not set in the 3rd party scenery.
Hi again,
I have tested the scenery now and this flag is missing
{
"dependencies": [],
"content_type": "SCENERY",
"title": "London Oxford",
"manufacturer": "",
"creator": "Pilot Plus",
"package_version": "1.0.1",
"minimum_game_version": "1.15.8",
"release_notes": {
"neutral": {
"LastUpdate": "VERSION 1.0.1 RELEASED APRIL 23, 2021\\nRemoval of Living World (Due to conflict with other add-ons)",
"OlderHistory": "VERSION 1.0.0 RELEASED MARCH 12, 2021\\nInitial Marketplace Release"
}
}
}
when I set this flag (flag package_order_hint), like:
{
"dependencies": [],
"content_type": "SCENERY",
"title": "London Oxford",
"manufacturer": "",
"creator": "Pilot Plus",
"package_version": "1.0.1",
"minimum_game_version": "1.15.8",
"package_order_hint": "GENERIC_SCENERY_PATCH",
"release_notes": {
"neutral": {
"LastUpdate": "VERSION 1.0.1 RELEASED APRIL 23, 2021\\nRemoval of Living World (Due to conflict with other add-ons)",
"OlderHistory": "VERSION 1.0.0 RELEASED MARCH 12, 2021\\nInitial Marketplace Release"
}
}
}
the scenery looks good and you can also select the approaches:
I’ll digest what you’ve written and feed it back to ORBX where I bought it from. Sadly the developer (PilotPlus) has stopped responding to support requests but has marked this airport as 2024 compatible.
I’ll do exactly that. I figured it was a problem with the scenery but ORBX kept batting it back to me because it works when in the community folder on it’s own.
To be fair they did offer me a refund but I’d rather just have the product working. At least now I have the ammo to prove the scenery isn’t fully compatible with 2024
I’ve fed it back to ORBX and shared this thread with their support. Hopefully they can get in touch with PilotPlus and get them to sort it out officially
Cheers
JW
Just for information making the edit with notepad isn’t enough. You must use Notepad++