I recently had the chance to fly the TBM for the 1st few times since AAU1. This plane is one of my main rides in FSE, in which I have 145 flights and over 300 hours, the vast bulk with the WT mod that was before AAU1. And things worked great all that time with GPS, ILS, and RNAV (RNP even). But this is no longer the case since AAU1.
I have always before just used the World Map to create a High Alt Airways IFR flightplan with any needed SID or STAR (but mostly I don’t use either, just pick some waypoints to turn to the en route course from runway heading), and have selected an approach to fit the wind (I don’t use live ATC). This always loaded perfectly and I never had any problems with the autopilot. I should note that I have Navigraph.
Since AAU1, however, I have noticed the following problems.
-
Flightplan Discontinuities: There are often gaps in the flightplan somewhere, such as between the 1st waypoint in line with the runway and the 1st en route waypoint. Or between the last en route waypoint and 1st of the approach. I tried using SIDs and STARs but gaps would still appear. Meanwhile, the flightplan sequences to the waypoint on the far side of the gap, but says I’m already there even if the waypoint is 100 miles ahead. And note that this ALSO happens with the PMS50 GNS750, not just the G3000, so seems to be something in AAU1 itself instead of the G3000.
-
Failure to Acquire Glideslope on ILS Approaches. Hitting approach mode arms LOC and GS. LOC eventually becomes active, the needle switches to green, and the plane tracks the localizer. However, GS remains white, never activates, and the plane keeps flying level. This has happened 4 out of 4 attempts so far. This only happens in the TBM with the G3000; the 750 follows the glideslope no problem.
-
Failure to Acquire Glideslope on RNP Approaches. Same as with ILS approaches, the TBM just keeps flying level and GS never activates. This is 2 for 2 so far.