I've posted an image of the DA62 panel.  The PFD shows a flight plan with TORIE as the next waypoint and the CDI shows a magenta line pointing in the proper direction.   The PFD display advanced from the first enroute waypoint (VPSRT) as the plane approached VPSRT and the autopilot made a nice smooth turn toward the 2nd enroute waypoint (TORIE).  The MFD map display showed the plane making the correct turn and advanced the magenta line to the proper heading from VPSRT to TORIE.

BUT... the MFD flight plan never advanced to the 2nd waypoint (TORIE).

About 90-seconds after settling on a heading to TORIE the autopilot made a 180° turn and flew a course back to VPSRT.

I disabled the autopilot and hand steered the plane back onto a heading toward TORIE.  Thirty seconds after engaging the AP - it again made a left hand 180° turn back to VPSRT while the PFD CDI continued to point at TORIE and the PFD info box and PFD flight plan continued to show TORIE as the next waypoint.  

This also occurs in the C172 Glass aircraft.  

The autopilot is less than useful when this occurs. 

Edited July 31, 20214 yr by TacomaSailor

Upon further research...with NO addons of any kind in Community.

The CDI, Info Box, and Flight Plan displayed on the PFD shows TORIE (the 2nd enroute (waypoint) as the active leg prior to takeoff.  The MFD flight plan shows the correct VSPRT waypoint.  Neither display changes after taking off.  BOTH the PFD and MFD remain static (but distances and bearings update as does the magenta line in the MFD map) until after I am past TORIE heading to the 3rd waypoint (CLSTR).  Once on the TORIE to CLSTR leg - both displays synchronize and work as they should all the way to touch down at KSAN. 

When I select VSPRT in the PFD flight plan (prior to takeoff) and try to do a Direct To - the PFD tells me that is an invalid waypoint. 

When I do the same thing, prior to takeoff, on the MFD - it allows me to set VSPRT as a the Direct To waypoint.

This is very new behavior since SU5 because this flight from KMFY to KSAN has been my standard test for FPS, scenery accuracy, pilotage, and aircraft changes since late 2020.  I have flown it many dozens of time.  

I just made my first flight with the update on the C172 and its new g1000.  Did not have any major issues, though this is only the first flight and one destination.  It followed a proper PT for the first time, so that was neat.

However, when I switched to the localizer on the PFD it did not show the proper course/bearing.  I expect this on a steam gauge system, as you need to set the inbound course manually if you want the indicator to align properly in comparison to your heading.  I've never seen a Garmin system fail to reset the PFD course on its own!

However, when I switched to the localizer on the PFD it did not show the proper course/bearing.

I was going to write about that as a separate problem.  Landing on RWY 27 LOC/ILS at KSAN - the C172 and the DA62 both were on glide path at GATTO.  I switched to LOC (after verifying NAV1 was tuned correctly) by pressing APR and saw the LOC arrow was at 90° to the proper course of 95°.  I used the OBS knob to align the LOC arrow with the proper heading to the runway.  The plane then followed the ILS to the TDZ.

the problem I see here is that I cannot align the LOC arrow with the proper course (it always is set to 0° when I switch the CDI to NAV1) until AFTER I switch the source.  But, it then takes several seconds to use OBS to align the LOC arrow with the runway heading and during that time the AP is steering off course by quite a bit.  If it takes more than 5-seconds to adjust OBS - the plane is outside the ILS capture envelope and the AP will not steer back to the ILS heading.

I thought all this was to be fixed by the G1000 Nxi which I do have installed.

??

33 minutes ago, TacomaSailor said:

the problem I see here is that I cannot align the LOC arrow with the proper course (it always is set to 0° when I switch the CDI to NAV1) until AFTER I switch the source.  But, it then takes several seconds to use OBS to align the LOC arrow

I haven't had quite the same experience but I think we're talking abut the same thing:

• LOC arrow is about 90 deg. off course when I switch over and activate APR
• The AP follows the localizer properly - it's right on the money
• Arrow stays pointed in the wrong direction even though I am properly on the LOC
• I reach over to the Course (not OBS) knob and turn set it to the proper heading

The g1000 NXi should have done this automatically 

1 hour ago, TacomaSailor said:

I thought all this was to be fixed by the G1000 Nxi which I do have installed.

The G1000 NXi is in Early Access, as it says in the Marketplace description. A number of features are not yet implemented, and there will almost certainly be bugs (potentially many). And this is the first release.

As for the CDI, presently, auto-slewing upon tune is not yet implemented, but will be in a future release. However, just like a traditional CDI, the needle does not need to point in the correct direction to properly navigate the ILS. In fact, also just like a traditional CDI, the selected course is completely immaterial to how the autopilot will fly the ILS. You can totally turn it 180 degrees and it will still follow the antenna signal (this is true in the real NXi as well, as it is in all CDIs).

-Matt

This is an nxi bug, IMHO