Menorca (LEMH) - Localizer Offset

[PilotGW]

Hi,

I’ll preface by saying that I don’t think that this is a Navigraph issue, but the issue persists even with the Navigraph in-sim navigation database installed.

When using Simwings Menorca (LEMH) in MSFS 2024, I’ve noticed that the ILS localizer is offset on both runways.

This only seems to happen when using an aircraft that is using the in-sim navigation database. Aircraft I’ve tried so far include the FlightFX Citation X and the A2A Comanche. I’ve tried using both the default MSFS navigation data and, as mentioned, the Navigraph replacement of the in-sim navigation data. The result is the same.

It doesn’t seem to affect most add-on aircraft that have their own navigation data (i.e., Fenix Airbus, PMDG 737 etc.). Weirdly, it does seem to affect the iniBuilds A350 with its Navigraph database installed.

Uninstalling the Simwings Menorca scenery and using the default airport instead, seemingly fixes the issue.

At the moment, I’m guessing the scenery is at fault. I’ve left a post on the Aerosoft forum, but considering Menorca isn’t the most well known destination on Earth, I suspect a response or a fix won’t be forthcoming from their side.

Is there anything that can be done?

[NAVData]

The question for me is:
Have you tried disabling or removing the scenery and using the stock scenery only?

Do you see the offset too? When no, you know it’s a scenery issue.

Cheers
Richard

[PilotGW]

Hi,

Thanks for your reply!

I was heavily leaning towards it being a scenery issue, I just wasn’t 100% sure. As mentioned, the issue isn’t present with the default scenery, so that confirms it.

Aerosoft / Simwings will need to fix it then, but I’m not holding out much hope.

[NAVData]

Ah, right, sorry, I have overread it … Seems to be a scenery issue, yes … Sorry, but in this case you can’t do more than report it to Aerosoft to fix it.

Cheers
Richard

[PilotGW]

That’s no problem!

I did some more testing today and I may have spoken too soon about most addons working fine. In fact, only one aircraft works properly now. The PMDG, which I’m fairly sure worked fine yesterday (unless I’ve gone mad), didn’t today.

I sat on each runway in multiple different aircraft, manually tuned the ILS and observed the localizer deviation:

Fenix Airbus:

PMDG 737:

iniBuilds A350:

Just Flight Avro RJ:

FlightFX Citation X:

The only aircraft where the localizer aligns on both runways, whether using the Simwings scenery or default is the Fenix Airbus.

Every other aircraft I tried, on both runways, had an offset when using the scenery. They were still fine without the scenery.

Why might the Fenix be fine, but nothing else?

[NAVData]

@PilotGW

Why might the Fenix be fine, but nothing else?

Sorry, I can’t answer this. The values in every dataset are the same. Possible that they use another magvar or calculate something on the fly. I didn’t know, sorry.

Cheers
Richard

[jpschuchna]

All beside Fenix use either the bgl based base package ILS signals or bgl based add on scenery ILS signals. For some Airports like EDDH Simwings used to have custom ILS coded, which caused issues with outdated frequencies.

Looks like Simwings is overwriting the Navigraph base package because otherwise Fenix and the others would have same indications.

You can build a patch for yourself and adjust the localizer to the add on scenery according to the simple Navdata tutorial. First check if the Simwings scenery has the following entry in the Manifest.json as order hint and the try again.

CUSTOM_AIRPORT

If it still doesn‘t work try to rebuild the ILS. The first thing would be to try and use the original Ident and frequency. If that still doesn’t work an ILS with a separate Ident and frequency is needed.

SimpleNavData

To get it aligned the following variables are important:

Localizer coordinate must be aligned with extended centerline of the Simwings scenery

The combination of full degree magnetic inbound course and variation must match the Simwings RWY true bearing. Use the developer mode to measure the true bearing with a transparent RWY as overlay.

Here is a template for the Navdata Sample in the SDK, that I did to correct the wrong GS in EDDS for RWY 25:

<?xml version='1.0' encoding='ASCII'?>
<FSData version="9.0">
<Airport lat="48.6898777261376" lon="9.22196388244629" alt="1255F" ident="EDDS" onlyAddIfReplace="TRUE">
<Ils
lat="48.684952304"
lon="9.196054016"
alt="373.075M"
heading="251.0"
frequency="111.100"
range="27.0N"
magvar="-2.987"
ident="IABC"
width="5.19999980926514"
name="ILS/DME 25"
backCourse="FALSE">
<GlideSlope
lat="48.692385287"
lon="9.240224948"
alt="1259F"
pitch="3"
range="27.0N"/>
<Dme
lat="48.692385287"
lon="9.240224948"
alt="1259F"
range="27.0N"/>
</Ils>
</Airport>
</FSData>

After the package is created using the package tool

Package Tool

the manifest.json needs to get following entry for the order hint:

CUSTOM_NAVDATA_PATCH

Regards Jan-Paul

[PilotGW]

Oh, thank you so much for this! Menorca’s one of my favourite destinations so I’d hate for it not to get fixed.

It might be a little bit beyond me, but I’ll definitely give this a read!