My custom ILS for St Athan (EGSY) doesn’t work since the latest AIRAC update (2602). With 2601, it was working just fine. I’ve tried different things with the priority (my nav-folders are named !!!navigraph-nav-base and }}}navigraph-nav-jepp, I also tried giving the nav-folders a priority of -9999 / 9999 in the content.xml and tried the same with my custom scenery) and package order within MSFS2024 - nothing seems to work. I thought that maybe you guys would have any idea what the problem could be? Maybe it’s just a priority thing I don’t see…
I only installed the latest AIRAC cycle — I am not using the SU5 beta or anything else.
The only change I made was renaming the navdata folders with “!!!” and “}}}”. I’ve been doing this since November last year because I was experiencing issues with broken STARs and approaches at certain custom airports, such as iniBuilds EGKK and EGLL. Renaming the folders was the only method that resolved those broken procedures.
I’ve also tried reinstalling the AIRAC multiple times in case something went wrong during installation, but the issue persists.
Just so I can understand this better: Does the Navigraph navdata overwrite the navdata from Asobo and 3rd-party sceneries completely when (if) the loading order works correctly?
Is the ILS compiled within an airport attached to a RWY or as standalone in its own XML?
Compiled as standalone in its own xml it should work with CUSTOM_NAVDATA_PATCH as package order hint in the manifest.json. The workaround with !!! and }}} shouldn`t be necessary anymore if the add on airports have CUSTOM_AIRPORT set as package order hint in the manifest.json
… but according to his previous post, he had not changed anything, and we had not either. But the package renaming does indicate an incompatible package, yes.
@SupersonicDrone56, please check the latest SDK and adapt your scenery. The folder-renaming feature is outdated, and we haven’t recommended it for a long time.