Navigraph NavData Overriding Custom ILS

Apologies in advance as I know that there have been several topics about this, but I am at my wit’s end and wanted to try my hand at seeing if there is any more information that could be gleaned from the community.

I will start by saying that I am using an old AIRAC from the last time I had a subscription (2204), but I don’t believe that has anything to do with my issue.

I was experimenting with airport design using ScruffyDuck’s ADE20 and picked a random airport to experiment with. In this case it is LOWI. My experiment was adding ILS to this airport, not that I’d likely fly into it but it was an airport that I knew didn’t have what I wanted to experiment with.

I was able to get a properly built package and installed it into my Community folder. When I reloaded my scenery library without AIRAC 2204 enabled, I got this (please ignore the mess, but you should be able to see that 18 and 26 both have properly aligned ILS cones):

Then I enabled AIRAC 2204 and reloaded again, and I got this:

You can see that my custom ILS cones have disappeared. I had read a fair bit about content.xml, package ordering, etc. My content.xml looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Priorities>
    <Package name="navigraph-navdata-base" priority="1"/>
    <Package name="navigraph-navdata" priority="1"/>
	<Package name="zz-redbeard-lowi-innsbruck" priority="100"/>
</Priorities>

Am I missing something or should this work? Can and will clarify if none of the above was succinct enough. Thanks in advance!

Hi,
This is not so easy to answer. In theory, it should work - the content file is correct (excluding the priority of our packages). It should be:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Priorities>
    <Package name="navigraph-navdata-base" priority="1"/>
    <Package name="navigraph-navdata" priority="2"/>
	<Package name="zz-redbeard-lowi-innsbruck" priority="100"/>
</Priorities>

But it also depends on the zz-redbeard-lowi-innsbruck package because you must set a few parameters for which our package will be overwritten. It´s not as simple as it looks, but at least from the content file, it should work when you don´t use a 3rd party scenery for this airport tool.

I don´t see any real issue. I´m sorry. Is it possible that this package will not be compiled by LNM? Have you tried entering the frequency directly in the sim to verify if you receive an ILS signal or not?

Cheers
Richard

Richard, thanks for your reply. I’m currently experimenting and will report back once I have something to report on. I appreciate you very much. Would it potentially help if I provided the scenery file in question?

1 Like

Of course, yes but not here in a public forum - I will write you a PM :wink:

Cheers,
Richard

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.