turn by turn ... A Major Letdown in Navigation

Shrek3k

@thanasis fully agree, turn-by-turn-navigation has been and is nearly useless for me due to the more or less constant ‘spamming’. I love the maps, I love and use navigation a lot … but currently never ever with turn-by-turn-navigation, but by quite often checking the map and changing it’s size … rather effectively preventing the use of other screens during runs in unknown territory.
Nevertheless: I really like my Vertical (although still suffering from massive battery drain (yes, restarted the watch, drained the battery etc) … hoping that it will disappear and go back to normal sooner than later )

thanasis

@Mff73 said in turn by turn ... A Major Letdown in Navigation:

@thanasis
Despite you are very right, it is well known .
I personally don’t use it, but I would like.
Thanks .
Still I felt I had to share my view .

seanvk

@thanasis Agree with you. It is a mess and why I still prefer my Epix Pro (gen 2) for anything using route guidance (i.e., hiking or trail runs)

Dimitrios Kanellopoulos

Have you ever used turn by turn in the past?

Since this was introduced and because it’s abusing the waypoints notifications to provide the feature I always hated it.

On the other hand the same kinda happens with me and google maps.

peegee

@thanasis
i can’t agree with you more!
i was so excited with the turn indication arrows at the bottom of the map which you can choose to notice or ignore… but screens that appear constantly with turning info is most confusing and irritating.
subsiquently i choose to navigate without the turn by turn option until it might (hopefully) be improved…

after saying this…
i definitely enjoy the remaing distance at the bottom of the map but would be overly happy if it would be possible to choose the data i want or even more so, to rotate between data fields.

thanasis

@Dimitrios-Kanellopoulos said in turn by turn ... A Major Letdown in Navigation:

Have you ever used turn by turn in the past?

Since this was introduced and because it’s abusing the waypoints notifications to provide the feature I always hated it.

On the other hand the same kinda happens with me and google maps.

I have used it in the past … yes and it was also awful, but this time I got very frustrated and I felt I should be writing about it.

duffman19

100% agree. I’ve been commenting on the poor implementation since I got my Vertical. It’s hard to imagine that there are people who tested this feature and decided, “Yes, this works well.” There are some glaringly obvious solutions that just never seem to get implemented.

I’ve given up on it for now.

slurpnik

I agree with your points @thanasis - I have also given up on using this feature completely.

The biggest annoyance is when I forget to turn it OFF for a new route I create, only to find out when I start the activity…

Audaxjoe

@slurpnik you can turn off turn by turn during the activity. As I found out the other day when I forgot to turn them off

thanasis

@Audaxjoe do you mind sharing the guide here so that people refer to it when needed ?
Thanks

duffman19

@thanasis I believe you have to pull up the route on the Suunto App, uncheck “Turn-by-turn guidance,” and the route will re-sync without the turn notifications, even in the middle of an activity. One of the great features of the navigation implementation is that routes can be updated on the fly.

far-blue

100% agree. It’s even more confusing on the older watches that don’t have a map to refer to. It’s been raised many times in the forum and no-one can understand why you get the notification for the next turn just when you are supposed to be taking the previous turn. While less of an issue with breadcrumb nav I can certainly see why covering the map with a turn notification would be frustrating. It would certainly be useful to have both the current and next turn available to show as a ‘tooth’ or even as their own screen to view any time rather than having to remember the notification.

isazi

@far-blue totally agree, except the “no-one can understand why you get notifications for the next turn”. That is just the default waypoint behavior of the watch, that shows the next waypoint when you get to the current one. Unfortunately the TbT navigation is just based on waypoints, so the behavior is that one. To have something that really works waypoints and TbT should be separated, the same way climb guidance is separated from the waypoints (at least from the UX point of view).

Audaxjoe

@thanasis as above. Just open the route, turn off guidance and it will resync.

sky-runner

@thanasis The right solution would be to continuously show the next turn at the bottom of the map the way Garmin does it. The distance remaining to the turn must continuously update. Then there may be an optional notification right at the turn, but it should be possible to turn the notification off.

In general notifications are hugely distracting when running on a technical terrain. I prefer to just keep the map open and glance on it from time to time, at least that is how I use navigation on Fenix. Navigation should be usable without notifications.

I still remember how angry I was at my Suunto 9 Baro which kept popping notifications about weak GPS signal during a race when I was super focused on running fast in the dark to the finish and not catching a root with my foot. I couldn’t spare even a second to slow down and discard the notification so it just kept obstructing the view of the data.

Dimitrios Kanellopoulos

There are improvements coming asap

thanasis

@Dimitrios-Kanellopoulos
great to hear (read) that!

Dimitrios Kanellopoulos

@thanasis at least it should be better imo, but still far from perfection

gerstlauer

Just wanted to add my disappointment with this as well, though it’s good to see there may be changes imminent.

I bought my Race S mainly for navigation and turn by turn, but it’s implementation is really poor, as you’ve all shared here. Hopefully this will be fixed soon.

Mister PYC

@Audaxjoe Hello How did you do to turn it off ?
and still see the nevigation ? did you used SNAP to ROUTE instead of ROUTE ?