Hi there,

some might have seen my other post over at the MSFS2020 section, so sorry if you have to read that again. It´s also not really a complaint that LNM is doing something wrong. I suppose the problem is within the Sims Navdata, but who knows better than the person who coded the Navdata Import into LNM 😉

So what´s it about?

I realized that for some Airports (let´s use EDNY, EDJA and LSZR for this example) LNM in the Information/Procedures Tab shows "ILS data not found", despite showing the ILS Data on the map.

For other Airports like EDDS and EDDH, it shows the ILS Data on the map and in the Information tab.

It is not a huge issue in LNM, since I have the data accessible in one way or another. I just wonder how this can happen.

 

Why do I think it is not really a LNM problem?

I used the GNS530 a lot recently in the Sim and realized that for some Airports the GNS did not show the ILS frequencies in the NAV/FREQ screen. But if I dialed in the Frequency into the COM Radio, ILS approaches worked without an issue. So I asked over in the MSFS2020 section here and someone asked if I am using the GNS Mod. Indeed I did! So I turned off the GNS mod and the standard Asobo GNS530 does show the ILS Frequencies no problem. So I thought that this is just a problem with the GNS Mod. But looking at LNM I see it has the same problem.

I suppose that there is a difference in the NAV Data that is in the Airport Files and what is in the NAV Data (if there is really a difference) and LNM and the GNS mod are only reading one of them and the Asobo GNS is reading both and shows the Frequencies. This is just a guess. It would be nice to have the whole information that seems to be within the Sim also in LNM, but it is no real issue for me. I just wanted to let @albar965 know 🙂

 

I forgot to add: There is no additional Navdata like Navigraph involved.

Edited March 25, 20224 yr by buedi
Additional Information provided

1 hour ago, buedi said:

Hi there,

some might have seen my other post over at the MSFS2020 section, so sorry if you have to read that again. It´s also not really a complaint that LNM is doing something wrong. I suppose the problem is within the Sims Navdata, but who knows better than the person who coded the Navdata Import into LNM 😉

So what´s it about?

I realized that for some Airports (let´s use EDNY, EDJA and LSZR for this example) LNM in the Information/Procedures Tab shows "ILS data not found", despite showing the ILS Data on the map.

For other Airports like EDDS and EDDH, it shows the ILS Data on the map and in the Information tab.

It is not a huge issue in LNM, since I have the data accessible in one way or another. I just wonder how this can happen.

 

Why do I think it is not really a LNM problem?

I used the GNS530 a lot recently in the Sim and realized that for some Airports the GNS did not show the ILS frequencies in the NAV/FREQ screen. But if I dialed in the Frequency into the COM Radio, ILS approaches worked without an issue. So I asked over in the MSFS2020 section here and someone asked if I am using the GNS Mod. Indeed I did! So I turned off the GNS mod and the standard Asobo GNS530 does show the ILS Frequencies no problem. So I thought that this is just a problem with the GNS Mod. But looking at LNM I see it has the same problem.

I suppose that there is a difference in the NAV Data that is in the Airport Files and what is in the NAV Data (if there is really a difference) and LNM and the GNS mod are only reading one of them and the Asobo GNS is reading both and shows the Frequencies. This is just a guess. It would be nice to have the whole information that seems to be within the Sim also in LNM, but it is no real issue for me. I just wanted to let @albar965 know 🙂

 

I forgot to add: There is no additional Navdata like Navigraph involved.

I'm having the same exact issue. It's already known, but expected to be solved with the next LNM release (next version), hopefully. Let's wait for the confirmation from the people behind the excellent LNM.

Oh, sweet! Thank you very much for letting me know 🙂

LNM 2.6.X takes the ILS information from the simulator and then had to cross-reference it from the Navigraph procedure data. This did not always work due to name changes and whatever. I did this to avoid course mismatches between aircraft and LNM.

LNM 2.7.X now takes ILS from Navigraph (also to simplify things internally). I think I fixed some other issues around this (had to dig into the changelog now to confirm).

You can try the alpha here:

A few post later in this thread is a description how to run the alpha in parallel with the stable.

Alex

Thank you Albar. It´s not a huge deal for me now and I´ll gladly wait for the next stable release 🙂