ILS approaches for LBSF and other fly2high sceneries in MSFS24

[WernerAir]

Hi there,
I am just flying to the first of my fly2high airport sceneries since moving to MSFS24. In this case it’s LBSF v2. I am using the Inibuilds A321LR, and the odd thing is that the MCDU will not give me any other than visual approaches when configuring my arrival. Somehow the ILS approaches are not in the database, even though Navigraph navdata is correctly installed.

As it seems, the problem seems to have been appearing on other fly2high sceneries as well (even before SU3), as I can gather from a corresponding MSFS forum post: Fly2High Airports - No Approaches in MCDU - Scenery & Airports - Microsoft Flight Simulator Forums

Is there any way to determine where the problem lies? I am pretty sure it is not a Navigraph problem, but I am still wondering why the Navigraph navdata is not accessible here even when the scenery is botched. Or is it possible that this is an aircraft related problem?

Any ideas will be appreciated…

[NAVData]

Hi,
I assume you have a scenery issue or a loading order issue on your system. When you remove the third-party scenery, do you see more approaches?

I don´t have this scenery, therefore I can only use the stock LBSF scenery, and here I have all approaches available:

Here from the WorldMap EFB:
Runway 09:

Runway 27:

… and here directly from the C172 with the G1000:

So it is either a 3rd party scenery issue or an order issue, but it is not a navdata issue as you see.

I would recommend first trying to "reset your content.xml file.

FAQ - MSFS2024 (SU3 and above) - airport, procedure, waypoint, 3rd party & flightplan import issues

There is a new loading order logic since SU3; therefore, it is essential to reset your content.xml file when, for example: You miss airports. You miss procedures. You miss waypoints. Legs are missing from the nav devices. There are third-party scenery issues. There are flight plan import issues. … This file will be automatically recreated at the next simulation start. You will find the content.xml file in the following locations (Note, the location has changed since SU3 - it´s now in a sub-f…

When this doesn´t help, you should report this to fly2high …
Cheers,
Richard

[WernerAir]

Have you by any chance tried with any of the Inibuilds aircraft? Their MCDU is a bit special - and sometimes I don’t know which navdata I am looking at. For example, many ILS course values are off by 1 or 2 degrees.

[NAVData]

Here the approaches from the Inibuild A321LR (MSFS2024 SU3, stock scenery, Inibuilds A321LR and AIRAC 2509 installed):

Cheers,
Richard

[WernerAir]

Thanks Richard. Definitely seems to be a scenery problem then.
I will look into the behaviour of my other fly2high sceneries, and if I can confirm, I will contact them.
Any idea what they can do in a scenery that will prevent Navigraph navdata from being used?

[NAVData]

@WernerAir

Any idea what they can do in a scenery that will prevent Navigraph navdata from being used?

No, I´m not a scenery designer, but with SU3, there were many changes with scenery loading orders.

Have you tried this recommendation too?

FAQ - MSFS2024 (SU3 and above) - airport, procedure, waypoint, 3rd party & flightplan import issues

There is a new loading order logic since SU3; therefore, it is essential to reset your content.xml file when, for example: You miss airports. You miss procedures. You miss waypoints. Legs are missing from the nav devices. There are third-party scenery issues. There are flight plan import issues. … This file will be automatically recreated at the next simulation start. You will find the content.xml file in the following locations (Note, the location has changed since SU3 - it´s now in a sub-f…

Cheers,
Richard

[WernerAir]

I just tried it. Nevertheless, the only thing that changes anything is removing the LBSF scenery. Interestingly, EPWA and EPWR don’t have the same problem, so as far as I am affected it seems to concern only fly2high’s LBSF. I will contact them.

Thanks again for your help!