I have zero confidence in Suunto route navigation!
-
@sky-runner It’s been this way for many years, and no one’s doing anything about it.
Where did Suunto developers even get the idea that a watch that can’t handle the alarm for different days or menu loops should handle more complex routes?
It gets even worse when you enable turn-by-turn navigation. You might see things like this:
And what’s worse, the current position displayed on the map in such a case is incorrect.
-
@Mff73 said in I have zero confidence in Suunto route navigation!:
@sky-runner
Would you share this suunto app route gpx file?
Was it created directly on your phone in the Suuntoapp or from an external tool?It was created on Android phone. I don’t see a way to export GPX file from the app. The best I can do is export the app link. I guess opening that link downloads the GPX file.
Also, a small correction: on the second loop it was supposed to go along segment #1, then segment #6, then turn towards the path with the blue arrows. It seems that when I went on that short segment #6 on the first loop, which is shared between the two loops, the navigation got messed up. So there is your repro case!
-
@sky-runner And you’re lucky you weren’t running backwards according to the watch…
Like HERE
These are absolutely unacceptable critical errors. I don’t understand why Suunto can’t fix this. I thought that when switching from Garmin to Suunto, which is used for UTMB races, I’d be getting rid of all the bugs, but it turns out there are just as many, maybe even significantly worse. -
@Jan-Suchánek Suunto is throwing a lot of money on the UTMB races to be overly present there. I guess, it is their niche and true to their claim “Adventure starts here”. But there are a lot of Garmins seen as well.
That said, the Active Ideas YouTuber said that he always relies on the Suunto on longer trail runs and has seen several friends with crashing Garmins on those routes. Long GPX routes, lot of way points…
Myself I used Garmin’s “back to start” feature on my Epix Pro. Where it routes you back to the start point. Somewhere in between, I guess I took enough shortcuts through the woods that Garmin didn’t show me, it simply stopped navigating. I did know where to go from there, luckily, but that was rather strange.
Haven’t had this with my Suunto, yet. TBF, it has not got that specific feature, but the Maps are so fluid and fast, that I just can look on them to decide where to go next to get back. -
@sky-runner
Will try something looking like this. Not sure it will reproduce the exact use case, assuming it is even reproducible on your side.
I must admit I personnaly never navigate such “complex” routes.
What is strange in your case, is that your watch was showing correct remaining distance (8.3mi) but displaying wrong direction. -
You know I navigated from Croatia to Rotterdam last year with my Vertical.
This year a Faro to Alicante coast to coast and around 2500km around Norway then down via Sweden to Copenhagen.
The watch was faultless.
And various other walking and cycling adventures.
Such a dramatic title “I have zero confidence…”
I have total confidence in the Vertical. It is a fantastic bit of kit.
PS I do think the auto reverse is misguided. I’d prefer if it was something you had to implement.
-
@Audaxjoe Yes, when you have a simple point to point navigation there is little that can go wrong! But when using navigation in ultramarathon races or long training runs, I’ve had issues of various degree on many occasions.
Just this year:
- Navigation got confused during Canyons 100k race due to a small last minute detour and was misleading for several hours
- Waypoint for an aid station got moved during a trail marathon to another distance (we went through that point in the beginning and again at the end)
- Multiple instances of incorrect route auto-reversal, including two cases where it directed me away from the car at the end of a run - both cases I caught by chance
- The example above where navigation jumped to another part of the route due to a small overlap between two parts of the route
For example, imagine you have a loop route. If you go off route even for a brief moment, for example because the map was wrong, I guarantee that once you are back on route, the route will reverse and guide you in the opposite direction, even if you are at the end of the loop and close to finishing, even if you didn’t make a single step in the opposite direction. Is that a reasonable behavior?
I said I have zero confidence because I do actually have zero confidence. I now fully expect it to misdirect me because that happened close to a dozen times and I cannot blindly rely on it. If that never happened to you, perhaps you never tried to follow complex routes. But what is the point of having light blue navigation arrows if the navigation doesn’t stick to a planned route and can change direction if there is any opportunity to misinterpret the route?
-
@Mff73 said in I have zero confidence in Suunto route navigation!:
What is strange in your case, is that your watch was showing correct remaining distance (8.3mi) but displaying wrong direction.
I have an intuition of why it behaved that way. I think there are internal “checkpoints” periodically on a route. It would be too expensive to follow every single point in the route GPX file which can be every second if you imported a route, so likely the implementation puts a number of these checkpoints every so often along the route path. Then once you reach each of them it updates the light blue navigation arrow. I have also noticed that these navigation arrows may lag and not be updated often, and sometimes the current position may even be past the navigation arrow.
What I think might have happened is that on that short segment #6 in my above example I passed a “checkpoint” from the second half of the route before passing a checkpoint from the first half, which is quite possible because that segment #6 is shared between two halves of the route. That made the navigation arrow follow the part of the route after that later “checkpoint”. I’ll try to reproduce that with a simpler short route near my home.
-
@sky-runner You don’t have to repeat yourself, the message is clear! YOU have zero confidence in Suunto route navigation. What some of us try to state is that the absence of confidence is just your personal problem and not an objective fact. Since there will never be a perfect navigation tool, maybe the solution to the problems you face is to accept the shortcomings of the one you currently use and try to adapt to it finding a way to overcome them. Or perhaps there is a better navigation tool available for your needs in which case you don’t have to cope anymore with the inadequacies of the Suunto navigation.
-
@GiPFELKiND said in I have zero confidence in Suunto route navigation!:
@sky-runner wow thats incredible inacceptable. But that is no new Problem. In complex routes its necessary to show at the Phone. This didnt work Like exspected. At no time you can navigate a Special route with your Suunto.
I navigate“Special” Routes all the time, most of them off trail. For example, a four day fastpack in the wilderness with nearly 3 days fully off trail and no issues. However, I do admit there are issues. The auto-reverse can cause issues and I have had an issue @sky-runner describes but long ago with the 9baro before maps. I will ask around some and see if other testers have encountered this.
-
@sky-runner
As far as see in the gpx files, there are the track points, the waypoints and the shaping points (points which are/were used to calculate the route itself, and could be reused to recalculate differently in case of changing the navigation mode (paths, roads, etc…)
That said, I tried yesterday a complex route like yours and navigated it with two watches : I obtained multiple resultsnot identical on both watches, but one has followed your issue.
I will try to reproduced it again with more care about the route design itself (mine was too complex).
Like you, if the route reused a same portion twice and turn one side first and the other side after, one of my watch did it OK, but not the other, but they not same watches and not same FWs, though, also difficult to analyze, but it is definitively must not be different).one other thing i tried to reproducted (is it influencing or not) is the fact that you (i think) have specifically selected starting point as a shaping/routing point, don’t you ? thus i did the same.
-
I share that some issues can happen, but I try to deal with them.
Overall it works pretty well. I Rarely have multiple crossing on my route.
Reverse issues are the most annoying (wrong distance to destination, wrong position on altitude profile) ; it used to work better with previous fw.Anyway, for me navigation is a “whole subject” especially when I go in a place I don’t know
- studying my route before starting
- using watch as a tool ; If it fails I must be able to do without it.
- having off line detailled maps (in France, IGN maps)
To me, main complain for now is about last climb update when there are waypoints on route. Not directly part of navigation but closely related.
-
This is 100% caused by the Auto Reverse “feature.” The watch is continuously trying to figure out whether you’re running the route forward or backwards, and guesses wrong about half the time. Suunto just needs to do away with this and give the user the option to follow a route either forward or backward.
@sky-runner I run into this situation all the time as I often use routes while tracing trails to update OpenStreetMap. In doing so, I create routes that always double back on each other to get traces going both forward and backward to help counter any offset that may occur due to direction of travel. This leads to some pretty complicated routing. However, when I’m running to map, I’m also wearing a Garmin (usually a 955) with the same GPX route. The Garmin never screws up navigation since it’s always just following the route in one direction (and the turn notifications are much better).
In this situation where I’m wearing two watches, I end up using the map on the Vertical for zooming in and out of the route as I find this much easier than the 955. And the 955 is used to confirm turns and direction of travel since it’s always correct.