I have a question about ILS at a custom airfield, it stopped working for me right after the SU3 update, no aircraft can track this ILS now and no info (name, distance) is displayed in Garmin when you set the frequency active, more details below:
Nothing was changed in my exported custom airfield in community folder and I’ve tried to reinstall it also, didn’t help;
My ILS is NOT visible in Little NavMap;
ILS “ident” value was 6 characters and I’ve tried changing it to 3 or 5 characters with no success;
Magvar value was “0”, but changing it to “11.487” did not help;
Deleting the ILS and creating it from scratch did not help;
Tried to add a new ILS for another runway and that one is not working also;
Project rebuild and new export (with no log errors) did not make it working;
Cleaning cache, disabling other addons etc. and even full sim reinstall didn’t help.
At the same time:
My ILS was working all the way since 2024 release;
Airport itself is loaded with all runways, buildings, etc.;
ILS as a system is working fine at default airports (can be tracked by different aircraft),
Glideslope at my airfield is visible in developer mode debug view;
Package_order_hint: “CUSTOM_AIRPORT” is present in manifest.json;
ILS is working at a random fictional airport that I’ve downloaded from the flightsim site and put in the Community folder;
ILS system is working if I create it from scratch in another airport;
My ILS works only if I choose “build and mount” in dev mode.
I have no idea of what is happening or how to fix the issue and will appreciate any help on this question. Right now it looks like it’s not loaded properly from the community folder.
P.S. I don’t have another PC to test so please message me if you’d like to help and check if it works for you and I may share the airfield with you.
I have had to do the following from prior to SU3 (I cannot remember if the issue first appeared when I started SU3 BETA) so I am not certain if this will work for you but it may be worth a try.
I moved my custom airports to the bottom of the Content.xml list, below the navigraph lines. (in …Limitless\8wekyb3…\LocalCache)
In Little NavMap (“LNM”), under the Scenery Library tab; Navigraph - AIRAC Cycle xxxx, select “Do not use Navigraph database”.
I do the latter every time after loading the scenery library (which I do after editing whatever needs to be displayed in LNM, i.e. ILS, VORs, NDBs, WAYPTs, SIDs, STARS, and Approaches.) All the custom data disappear after I “Load” the scenery library but will reappear when I select “Do not use Navigraph…” I assume you can revert to using Navigraph in LNM by unselecting it.
Hi,
I am not sure to totally understand the bug, but I think you should add an approach procedure to the airport that references that ILS.
And also, I have been told that 109MHz is not technically a valid ILS frequency. ILS frequencies always use odd digits in the tenths (109.1, 109.3, 109.5, etc). So the avionics might be confused.
The bug itself is rather simple: you activate ILS frequency in airplane and nothing happens, you cannot track glideslope anymore after SU3.
Steps to reproduce:
place the aircraft in the air on glideslope runway 06R,
dial in 110.1 frequency for ILS tracking in your aircraft (I’ve used C152, PC-6 etc.).
Expected: ILS is tracked.
Actual: ILS is not tracked.
Custom ILS works on other addon airfields with no approach procedures and on the airfield with issue it has frequency of 110.1, so this looks like not the case we’re discussing.
It appeared that somehow Navigraph data has influence on that: if I remove Navigraph, my ILS starts working so the issue may be in addon loading priority mechanics.
As I said, I may provide you with this addon airport so you may reproduce the issue, but in general the steps are very strict as described above.
EDIT: I’ve sent you the link to the addon in private message.
This is probably the main issue. You can check in the package order tool in dev mode to see where your package sits relative to navigraph-nav-base. That package deletes any navdata in layers below it, as that is necessary for them to disable the default navdata.You probably should still choose a valid localiser frequency: Instrument Landing System (ILS) Frequencies - The RadioReference Wiki
The package order tool shows my custom airport below the navigraph data.
Not sure how should I make the order correct not having to edit it manually in the tool, is there any solution for that? I don’t think it’s a good practice to have addon users to manage order manually.
110.1 is a valid ILS LOC frequency, isn’t it? A lot of charts provide frequencies like 110.5, 111.9, 108.9 etc.
from correctly named (by SDK convention) “airport-icao-name”
to “z-airport-icao-name“
immediately restores correct ILS behavior without disabling Navigraph data.
This proves the issue is directly related to addon load order and package priority. It deserves a fix and not a workaround.
This breaks SDK conventions and damages trust in the SDK and in the platform. Developers should not be forced to rely on undocumented naming hacks and addon users should not be forced to manually reorder packages to get core navigation systems working.
I’m still ready to provide the addon itself and/or any information needed as well as spend my time and demonstrate the issue to reproduce it and resolve.
The “package order hint” is here to avoid that kinf of hack. Can you tell me the order hint of the “navigraph-nav-base” ?
Maybe try CUSTOM_AIRPORT_PATH for your airport, just to see if it fix it
for “navigraph-nav-base” “package_order_hint” is “CUSTOM_NAVDATA” (“Custom navigation data“ in package reorder tool).
Setting “package_order_hint” for the airfield to “CUSTOM_AIRPORT_PATH“ results in “INVALID“ string in package reorder tool and did not help to solve the issue with ILS, unfortunately.
Checked it, “package_order_hint” was set to “CUSTOM_AIRPORT_PATCH“ and is seen in reorder tool as “Custom airport patch” now, though ILS is not working still.
Can you take a screenshoot showing your package and the navigraph one in the package reorder tool ? It’s just be sure of the package hint of both packages.
Also, do you have the Delete All ILS option checked in your airport properties ?
Checked deleteAllILSs option, saved the project, rebuilt it and exported to community folder: ILS is not working (tested with 2 planes with different avionics).
What I’ve noticed after enabling the option: now the scenery source xml file contains the string that is missing when NO delete commands are used (all delete options = false) in airfield properties:
You can send us your project (see 3) Provide Private Content) and I will try to check whether anything is misconfigured.
However, I’m afraid we can’t do much more than that, since we don’t have access to Navigraph and therefore can’t reproduce the issue on our side. (The issue I was reproducing in my initial post was a different one.)
@NAVData By any chance, do you have any reports that match the issue described in this topic?
