Good afternoon.
I was happly using MS2024 with navigraph using the following trick in the community folder
I downloaded this morning the new AIRAC but the trick does not work anymore
Waypoint in LIMC are again thousands of miles apart.
Did something changed?
I’ve also tried to leave the folders with the original name but same issue.
Thanks
Matteo
Hi Matteo,
What FMC is it, and from what aircraft? Do you use any 3rd party scenery form LIMC?
Cheers,
Richard
That is from the stock ini A330. Yes I do use a 3rd party LIMC but issues were solved adding exclamations and brackets in front of the folders in the community folder (I believe you or Ian instructed on the forum to do so). This worked perfectly with AIRAC 2501 but it doen’t with 2502.
I deleted 2502 and copied by back up copy of 2501 and all worked fine again
Thanks Matteo, are you able to “remove/disable” the 3rd party scenery for LIMC and install the 2502 again. Re-start the sim and can you try it again please?
We use the official/recommended way what we have offered from ASOBO/MS with 2502, according their instructions and their SDK
Cheers,
Richard
Will try and get back to you
I removed 3rd party LIMC and installed the new 2502 from the HUB (I left the folder name unchanged) and all works fine
If the 3rd party airport is enabled all fixes are messed up showing lat/log 0N/0E.
Changing the folder names starting with !!! and }}} doen not work anymore like it worked with 2501.
Same thing goes for VHHH.
I’m assuming we are stuck either with not using 3rd party airports with 2502 or stayng with 2501 with the folder name “trick”
Matteo
The problem here is that ASOBO/MS has changed its loading priority rules, and it seems that third-party scenery doesn´t follow these new rules now. I assume it´s only a kind of “transition phase” and that all scenery designers are following these rules (link see above in my posting).
In the meantime, we have only two possibilities - to follow the official rules (what we have decided now due to the navdata development) or to rename the packages. Both “solutions” are currently not optimal, but we had to decide on one of them.
Sorry, Matteo, for the additional effort at the moment, but again, it was not our idea to change a working logic 
Cheers,
Richard
Thanks. All clear. Mi only question is:
Why if I rename the 2502 AIRAC folders in the community the issue persists while it was working with 2501
Something changed “within” the folder according to the SDK reccomandations that makes the folders name “trick” not effective anymore?
Very sad to see that the workaround in the previous AIRAC cycle doesn’t work anymore, making airports like VTBS and VHHH unflyable again with the Navigraph Navdata.
In the previous cycle I could do the ‘trick’ (remove Scenery indexes, delete content.xml, reinstall navdata) and happily fly out of and in to ‘problematic’ 3rd party airports and import the route from Simbrief. Unfortunately the new update has put us back to square one (from a user point of view).
Hopefully in the next few weeks the PMDG777 will drop for MS2024 and iniBuilds A350 will be available in a few days. They will both use “custom” database and the issue will be partially solved. I’m sad because I find the stock A330 a pretty good aricraft to fly but this issue is of course a blocker since it is not reccomanded to fly in VATSIM with outdated AIRACS
Matteo
Hi,
As I wrote in my previous posting, this “solution” is the recommended way from ASOBO/MS for ALL 3rd party developers, and it’s the official way according to their SDK (see the link).
Someone must start to follow their new package loading rules for MSFS2024 to avoid future issues, even when this transition phase is a pain for all of us, especially for the user of 3rd party sceneries when these 3rd party sceneries do not follow these new rules in this way.
It was not our idea to change these rules. We were happy with the priority order solution in the content file. ASOBO/MS decided to change it, and it includes a lot of bugs, too.
Cheers
Richard
PS: yes, external databases help a lot because you are independent entirely from any dependency on the development from ASOBO/MS - but as Matteo wrote, we have a few suitable stock aircrafts, too, which use the in-game data, and for these aircraft we need a final solution too
What airports do not work with stock nav data?
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
