This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Navigation issue following a planned route

Recently (last two weeks) during navigation with a planned route, I've seen a new behavior of the arrow that indicated my position in respect of the route.

The arrow that indicate the runner position is in some way locked on the route that I've already pass. In the meanwhile the line that indicate my recorded track is ok and indicate my real position.

This behavior continue for some kilometers and after that the position arrow return to the right place at the end of the recorded path. 

For my this is an issue, probably appeared from 18.xx software version.

Have someone noticed this behavior during navigation?

  • I have seen a similar behaviour on a run yesterday on v18.26. This was the first time I noticed it. On a run on v18.24 a navigation was still fine. But probably there are dependencies on other factors.

  • The current official firmware (18.26 and earlier 18.23) have a bug that causes "lock on road" to be always on, regardless of the setting. (This only affects map view, not route recording.) It has already been fixed in the new 19.xx betas.

  • Good news. thanks.

    It seems the problem that i saw durinh navigation. Here the link to the bug report https://forums.garmin.com/beta-program/forerunner-955-series/public-beta-bug-reports/i/public-beta-version-18-xx/hike-trail-run-are-ignoring-lock-on-road---off

    I've checked my setting and my map is in "Lock on road" OFF.

  • The "lock on road" issue seems to also affect trails and is also an issue when simply looking at the map page and not navigating a course. My actual path is the solid red line, but it keeps trying to lock onto the nearest trail (dotted line). The blue triangle for my current position is incorrect and should be where the red dot is at the end of the solid red line. Its been a bit annoying navigating trails since a lot of the trails are not very accurately mapped (like in this example) and I have to remember that the blue triangle is not actually my current position.

    Hopefully they actually fix this in the next update without screwing up something else. At least it doesn't affect the actual gpx track being recorded...

  • Yes, the bug is especially disturbing when on trails. But I've been using the latest betas (19.09 and now 19.12), and this problem has definitely been solved in them (so if this really disturbs you, just join the beta for the duration of this beta cycle). Based on my own use (and the general quietness of the beta forum), I'd say that this time there doesn't seem to be too many new big bugs in the beta.