I've built a data field for fun and personal use to get more data on the screen of my Fenix 5x and I was trying to use the distanceToDestination in Activity->Info. I want to have the same data value as the native distance remaining field while following a course. In the simulator this shows the correct data set under the navigation information. However while testing on the Fenix 5x I've noticed that the data it gives is dependent on the Routing setting for the app. If the Routing setting is 'Use Map' the distanceToDestination is accurate but if the Routing setting is 'Follow Course' then it always shows the same distance as the distanceToNext field. I'm using a course built in Garmin Connect to test that has just a few course points to make sure there's differentiation between distanceToNext versus distanceToDestination. Shouldn't the distanceToDestination behave the same regardless of the App Routing option? Is there another way to get the same value as the native distance remaining while following a course?
I am also running into this issue and wish Garmin would address this bug. I want to create an ETE/ETA field that is based in my average moving speed during activity and distance remaining. With this bug, I only get ETE/ETA to next waypoint along course.
Devices often share the same code. e.g., the fenix6 family is based on the code from the fenix5plus. If a bug is fixed in the device firmware for one device, it will make its way out to similar devices, but that will take time.
Do devices sync in this common base each time they release a new firmware? Or is this more a branch of from the common base when the new device is "created" and then just implementing "new device specific" stuff without resynchronizing ever again (unless there's a manual synchronization action)?
