I saw the same thing after the Navigraph update. I went to the FMS Data manager and updated everything to the current version. All is well now with Navigraph data live in the sim.

55 minutes ago, Bert Pieke said:

I have come to the same conclusion... but if you are a "glass half full" person, WT have said that they are working on fixing this... so SU5/6 should show us where we are headed.. 🙂

I am keeping the faith Bert. I have confidence that WT team will deliver the goods and of course VNAV ..😆 for both Garmins 🤞

4 hours ago, JRBarrett said:

Which specific ILS approach was it? I can check MSFS default vs. Navigraph for the ILS frequency. Are you sure the Jeppesen chart you are using is current? 

KLNK was where I was doing my testing with the DA62/G1000. The chart was from from Navigraph, latest update, so Rev.4. Chart says posted ILS frequency was 109.9. What I found in numerous tests was  DA62 with stock G1000 flew the ILS on 110.9 just fine with Navigraph data installed or uninstalled. Using the DA62X Mod didn't make any difference either, still flew the ILS on 110.9 just fine. Only if I tried using the WTG1000 v.3.7 did I have any issues. The Com freq came up different than the stock and even if I manually entered 110.9 it still wouldn't capture the ILS at all. I have almost always used the WT stuff since the beginning without issues so this kind of surprised me. I had done the SU Beta an did it with no AP Mods but when they released the updates I immediately installed them. But, that was also the same time the Navigraph updated so that is why I thought that had to be the issue, but in my case, it doesn't seem to be the case. I have since mad a few flights with the stock G1000 and the stock G3000 in the Longitude without any ILS issues. I have been keeping whatever ILS freq that MSFS wants to use, which hasn't matched a chart yet. YMMV.

Edited May 30, 20215 yr by Mikeingreen
another thought

3 hours ago, Mikeingreen said:

KLNK was where I was doing my testing with the DA62/G1000. The chart was from from Navigraph, latest update, so Rev.4. Chart says posted ILS frequency was 109.9. What I found in numerous tests was  DA62 with stock G1000 flew the ILS on 110.9 just fine with Navigraph data installed or uninstalled. Using the DA62X Mod didn't make any difference either, still flew the ILS on 110.9 just fine. Only if I tried using the WTG1000 v.3.7 did I have any issues. The Com freq came up different than the stock and even if I manually entered 110.9 it still wouldn't capture the ILS at all. I have almost always used the WT stuff since the beginning without issues so this kind of surprised me. I had done the SU Beta an did it with no AP Mods but when they released the updates I immediately installed them. But, that was also the same time the Navigraph updated so that is why I thought that had to be the issue, but in my case, it doesn't seem to be the case. I have since mad a few flights with the stock G1000 and the stock G3000 in the Longitude without any ILS issues. I have been keeping whatever ILS freq that MSFS wants to use, which hasn't matched a chart yet. YMMV.

109.9 is correct for the KLNK ILS 36 per the current NOS and Jepp charts. I looked at KLNK in LNM, using only the default NavBlue sim database, and then with the Navigraph beta MSFS nav data active, and they both show the ILS on 109.9 as well. I positioned the G1000 C172 on the runway 36 threshold, and it is tuning the ILS fine on 109.9, showing ILNK with a centered needle. Tuning 110.9 shows no signal at all.

8 hours ago, SAPilot said:

.. think I must from now on only do ILS approaches into airports, if available of course. At least for me it so far worked better.

PS : Using Navigraph nav data - 2105 - rev 4

 

I find most RNAV approaches to be great and certainly a decent way to get into a lot of airports that did not have an instrument approach in the past for IFR  conditions (VOR or NDB, etc.).  They are non-precision approaches, so the last thing I expect, in most cases, is to have any type of AP-coupled GS system to bring me down.  I follow the chart and step down accordingly.

Now, I can do this artificially in some cases (setting a descent rate at 3 degrees to DH) or if the threshold is visible, setting a descent to field elevation.  On some GPS approaches I've had a GS intercept, but that's a rarity.

13 hours ago, JRBarrett said:

109.9 is correct for the KLNK ILS 36 per the current NOS and Jepp charts. I looked at KLNK in LNM, using only the default NavBlue sim database, and then with the Navigraph beta MSFS nav data active, and they both show the ILS on 109.9 as well. I positioned the G1000 C172 on the runway 36 threshold, and it is tuning the ILS fine on 109.9, showing ILNK with a centered needle. Tuning 110.9 shows no signal at all.

I agree with you that 109.9 is showing LINK, BUT, if you try the approach using 109.9 you do not get the GS Ribbon and no Verticle guidance. You do get it using 110.9 which MSFS wants you to use, even though 109.9 is labelled ILNK while in STBY. Very strange.

3 hours ago, Mikeingreen said:

I agree with you that 109.9 is showing LINK, BUT, if you try the approach using 109.9 you do not get the GS Ribbon and no Verticle guidance. You do get it using 110.9 which MSFS wants you to use, even though 109.9 is labelled ILNK while in STBY. Very strange.

Do you also get a localizer with 110.9? I didn’t notice if 109.9 had a glideslope, but 110.9 had absolutely nothing.

1 hour ago, JRBarrett said:

Do you also get a localizer with 110.9? I didn’t notice if 109.9 had a glideslope, but 110.9 had absolutely nothing.

Yes, both freq connect when inbound from BIE where you turn on final and center on same direction.

I am somewhat ashamed to come here and admit this, but I feel I have to. I had not really paid much attention to the Comms on the G1000 until this problem cropped up. While I don't know if it will still be an issue with the WTG1000, I had been reading what is the active freq. wrong. I "Assumed" it was the freq that was highlighted that was active. After watching a G1000 tutorial video posted here today I now know that the highlight is just showing which radio is active and that 109.9 was the active freq and it was the one showing the ILS just fine. You learn something in the hobby every day it would seem.

On 5/30/2021 at 6:08 PM, jarmstro said:

Not sure whether it's Navigraph but all my ILS approaches are well off after this update. Nothing is lining up properly. I'm deleting it and going back to default.

I've been having exactly the same problem this week flying in the WT CJ4, I've tried everything I can think of but can't seem to fix it.   I'm running the latest Navigraph navdata.

Interesting - I've only done 3 ILS approaches since the update and they've been spot-on.  In fact, I had been complaining that a number of the approaches gave improper glideslope coupling (about a dot low on average).

Now, since the last updates (sim and Navigraph) coupled approaches are on-the-money and alignment is perfect.