Mikeingreen

I have a SeriesX but don't see myself using it much for MSFS. For starters I would have to buy the Hub from Honeycomb for my Alpha and Bravo and HOPE that it will convert my Saitek pedals also.My PC and my xBox play through the same 32" monitor so there is no gains either way there. I do have a question though. I see that it says that the console version is available for preload and I have the Digital Ownership, so it should be Play Anywhere. But I cannot find where to click on the Preload.

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.

They are Jeppesen charts, at least they say Jeppesen on them.

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

I just got the same thing with the Release notes got 1.16.2 which I have been running for the last few weeks. Interesting 🧐

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.

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.

It has been an issue all week wherever. I just completed my flight without WT G1000 or Navigraph data and it went off with only one issue. It captured the ILS just fine along with the GS, but I had to let it use the ILS frequency from MSFS (110.9) and not the frequency (109.9) that is posted on the Chart (Jeppsen). That could be because I am not using the Navigraph data but who knows. One thing is certain though, it worked using the MSFS G1000 and did not using the WT G1000. Going to reinstall the Navigraph data and test again. [update] Still had to use the MSFS ILS frequency instead of the one posted on the Chart. Very strange.

Uninstalling Navigraph data didn't cure it. Flight still went to word not allowed at the end. Next I am going to try the flight without WT G1000 and stock nav data. I need to find a shorter flight to test this as the one I am using is around 45 minutes, but I want to keep things the same and not just start over. This all started last week after I started using MSFS AddonsLinker and the updated WT AP's. It isn't an issue with SU4 as I was running that for 2 weeks before the issues started.

I will try that as I still was having issues with Rev.4. Still not following ils.

No link as I use the Navigraph update installer.

AIRAC 2105 Revision 4 (2021-05-28) I hope this is the Rev that fixes things as I have been having issues with ILS approaches since 2105 Rev1.

You are welcome

They did release an updated model for SU4. Here is where to always check on what is the current release: Working Title - Packages

I was having issues with Rev.1 and updated to Rev.3 also. I am 30 minutes into a flight now and seems to be back to following the FP like it should. Using the EMB110 with the GTN750 and all is well now. [update] I am now getting some drift off the magenta line and am having to use HDG mode to continue the flight. I had really hoped that this last update would cure the drift. ☹️

That system would have saved my Wife's cousins life a few years ago. He owned the Boulder Airport services and was selling a Piper Meridian but wanted some pics of it against the Flatrocks before they took delivery. They had a photographer in a chase plain and somebody zigged when they should have zagged and took the tail off of the Meridian. The chase plane landed safely with some wing damage. Sad story.

You can learn something every day.

How can we tell when this is updated? Wile you can see the ver# on the website the download doesn't tell you what version it is.

I just read an article about an in-air collision that happened in Denver this morning. It stated that the CR22 and a Fairchield Metroliner collided on approach. The Metroliner landed safely with major tail damage and the articel says the pilot of the CR22 deployed a parachute that brought the CR22 to the ground with no injuries to the pilot and passenger. I never heard of such a system. Here is the article: 2 small airplanes collide midair above Denver, no one injured, authorities say | Fox News

Thanks Randall, I remember reading that at sometime now.

I hadn't used this before today although I knew about it, and after seeing this thread, and doing some flights in the 172 for NeoFly, I decided to get it set up. While it works and seems better than the G1000 my first complaint is it doesn't seem to remember my Navigraph info. I set it up earlier when I was just checking if it was working. This afternoon when I was in the air to my destination, I clicked on Charts and it said I hadn't logged into Navigraph. I will play with it further as I do like the looks of it. Also, the 2 airports I was going to were both Grass Strips when I got there so I doubt there were any charts anyway.

It does if you use JD's Mod from Flightsim.to. That adds a bunch more aircraft to the GTN750 than the ones that come with it.

I must have got in. When I clicked "Join" it took me to the M$ Store.

This last episode was the first time I have had any issues with AMD and their drivers. I am also not convinced 100% that was the issue to start with. Same flight today is having no issues. Only change is older drivers and newer WTG3000. So far so good. I have had far less issues with AMD than I had with nVidia. A previous hobby had me going through multiple cpu and gpu stuff annually benchmarking it to the edge on a team. Me personally, I will stick with AMD.

I think the root of my problems was the Navigraph data deleting itself, whatever caused that. MSFS was trying to find that data and couldn't but kept looking. After putting that data back in the FP's loaded up instantly and with all the waypoints, ATC was back, and there was no lagging in the menus. I at first thought the AMD driver was causing it but now I am thinking it's not. Going to go back to the newer driver today to test that. So background apps may have been my culprit. Overclocking is not as my system is all running at stock clocks as all settings are on Auto. But it could also be another backgound app contributed as well with the WTG3000 6.1 Mod. It will be interesting to see what happens with their update.