-
@silentvoyager but the elevation profile is tracking correctly. Why on earth would the two be be different??
-
@stromdiddily It wasn’t thinking that you were further along. It knew exactly where you were. But back in April 2019 Suunto introduced this new feature that makes routing dynamic and it uses arrows to point the route the watch “chooses”. I don’t know who’s bright idea that was but that dynamic routing is wrong more often than it right. It doesn’t just stick to the route any longer. It may, for example, decide to reverse the route, which happens on out and back parts of a route. It may also pick a path that it thinks would bring you to the finish point sooner. A person who designed that clearly had no idea how and why trail runners use routes. They probably thought of something like a car navigation.
-
@silentvoyager I finally understand now. I’m not a route/navigation user as I don’t run on trails and therefore I’ve got time to carry an old fashioned map with me and use that for navigation, but I tried to create and use a route few weeks ago for the sake of it, and I could not understand the direction to take (because the route I created had some sections in which I would go both ways), so the arrows were changing. Now I see what was going on.
-
I’m using route navigation relatively often, for example if I’m in new terrain and I never had this issues. I´m happy with dynamic change direction of track, because I sometimes run same route but reversive, and sometimes I change my track in the middle and I decide return back to the start. I don´t remember, that I had anytime some issues.
I will try simulate this issue… -
@Václav-Král Route navigation works fine on simple point-to-point or single loop routes. But as soon as the route is a bit more complex, for example, intersections, multiple loops, or out-and-back sections it does no longer work as expected. Many race courses have multiple loops or out-and-back sections so relying on Suunto navigation would make you lost.
-
@silentvoyager oh gotcha, so the nav portion is saying “hey go this way, it’s faster”.
If that’s truly the case that’s pretty bad.
-
@stromdiddily I had this experience a year ago and reported it as a bug. I think the overall fix is taking time as it is dependent on waypoints, which we know are coming with SA. Having the directional arrows and the fix with waypoints should be ideal. A reason why I think this has not been fixed is that when you do not complete the entire route, the watch will then change the routing to allow one to continue along the return route and does not insist that you finish the unfinished portion. This is good as one could be attempting a summit and either time or weather do not permit a summit. Once started on the return the watch will reroute. I think we should wait until waypoints are enabled and then see if this same issue returns. I can re-report the bug if necessary.
-
@Brad_Olwin, Rerouting is a fine feature. But it should trigger only after a user went in an opposite direction and kept going despite the watch warnings. Currently the watch reroutes proactively before you even know which way was the actual planned route.
-
@silentvoyager , Yes there should be a question to validate or not the change of course direction.
We have already exchange a lot on these improvements with @Dimitrios-Kanellopoulos on FB -
@silentvoyager said in S9 Route Guidance:
@Brad_Olwin, Rerouting is a fine feature. But it should trigger only after a user went in an opposite direction and kept going despite the watch warnings. Currently the watch reroutes proactively before you even know which way was the actual planned route.
That has not occurred to me when turning around but with complicated routes and multiple directions from one intersection the watch can choose the wrong route. Similarly on an out and back the watch has re-routed me in the direction I already came from. However, this has not happened proactively, only when there are multiple choices at an intersection.