G3000 Flight Planning - Adding enroute waypoints replaces destination

Bug Reporting Hub Resolved
, , , ,
1

Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
Have tried with both no add-ons, and a few SimConnect addons (like AFC Bridge) – same thing happens in both situations.

Are you using Developer Mode or made changes in it?
No

Brief description of the issue:
This started happening with Sim Update V. When flight planning in the G3000 / TBM 930, adding an “Enroute Waypoint” puts it as the Destination. Any existing destination gets rotated back as an intermediate waypoint between the origin and destination.

Side Note: This behavior is not found in the Working Title G3000 and it works as expected there. This only happens with the stock G3000.

Provide Screenshot(s)/video(s) of the issue encountered:

Detail steps to reproduce the issue encountered:

  1. Load up the TBM 930 / G3000.
  2. MFD → Flight Plan
  3. Add an origin (eg, 06FA)
  4. Add a destination (eg, KBQK)
  5. Tap “Add Enroute Waypoint” and enter a waypoint (eg, OMN, select the VOR)
  6. Note that the Flight plan is now:
  • 06FA (Origin) > KBQK > OMN (Destination)

PC specs for those who want to assist (if not entered in your profile)
N/A

Build Version # when you first started experiencing this issue:
1.18.13.0

Are you on the Steam or Microsoft Store version?
Steam

Did you submit this to Zendesk? If so, what is your ticket #?
No

2

Given that Working Title was hired by MS-Asobo to revamp and replace (or by virtue of their G1000 NXi - deliver “Official Mods”) the core Garmin units, it may be the best approach to simply stick with WT’s G3000 instead of the stock sim. Eventually, when NXi exits Beta and reaches a production state, WT will turn their development efforts to the G3000 and migrate all the features they pioneered in CJ4 and NXi. In the meantime, QoL and small changes will maintain the WT G3000 lifecycle.

3

That’s the plan, barring no showstoppers in the WT version. Just getting this one in the queue in case I was missing some expected behavior or so that Asobo can be made aware of a regression in Sim Update V.

4

Just saw the notes that this is fixed in today’s hotfix.