2.14.12 is here

markytarky

@prenj I honestly think there is no change. Seems the only update to the watch FW is the Tour battery mode. The rest seems to be there already. Also, Komoot is not an FW update, but a connected service update or SA update.

Prenj

@markytarky
Strange. Why would they add this under “new features” if it was already there?! I’m confused.

Fenr1r

@prenj No “Define” option in POI creation? Nothing lurking in Bearing Navigation allowing saving (even without coords)?

Fenr1r

@markytarky Did Plotaroute turn instructions reverse when the route was followed B->A? I.e., did a “Next Right” become a “Next Left”?

If they didn’t, and do now, that would probably be a FW thing as WP name-handling appears to be a watch-side thing.

surfboomerang

@fenr1r No new options in Bearing Navigation as far as I can see.

Some videos about komoot integration
https://www.youtube.com/watch?v=6s0uhP61lms

and tour mode
https://www.youtube.com/watch?v=s187MLGFMF0

Prenj

@fenr1r Not that I can see. All the same.

markytarky

@fenr1r just replied to you on the other thread. No, it is not able to react to directions changes, but Komoot is not able to do it as well.

Fenr1r

@surfboomerang @Prenj @markytarky Thanks, all. Could the Release Notes writer(s) have become a little giddy with enthusiasm? Perhaps, in exhaustion and/or triumph, copied over the New Features from the promotional list that differentiates the new S9Ti from the old S9B, throwing in some cumulative App developments along the way?

Bulkan

The new mode of 170 hours doesn’t have the option to “continue later” the activity. I really miss it.

isazi

Anyway the Tour mode is advertised at 170 hours, but it can get more than that (or less if you play with the watch constantly).

Łukasz Szmigiel · S9PP 2.37.48

I’ll hijack this thread a little bit with my thoughts about this update from the S5 user perspective as the versions match and FW was release in the same time:

For S5 it’s basically bug fixes (which ones - we don’t know) and Komoot integration. Which, in the essence, is nothing new to the watch itself but an integration with external service via an API (if you’re stubborn enough, you could do the same thing with SA). Nevertheless, it’s a nice thing to have, and indicates with a little more detail what’s hiding in “digital transformation” slogan. To me, it’s quite obvious: Build amazing hardware and link it with external services and partners via a flexible API. Don’t be the jack of all trades.

So, Komoot:

The good thing

It works as flawlessly as is possible to implement in sane manner. Basically you link the Komoot account with Suunto, create a route and it’s in SA with all turns marked as waypoints. Magically. For all the “I hate creating routes with a mobile app” folks - this is a blessing. Although I’m not sure if it’s possible to create the route without the waypoints (if, for example, you intend to use it without all the disturbances introduced with waypoints or want a truly bi-directional route).

At first I was wondering - why would I ever need that? Especially when the routes with turn-based waypoints aren’t bi-directional. But it occurred to me that you can actually use basic screens and navigate only based on notifications. No need to have breadcrumb trail screen constantly opened. This is indeed a big plus.

The not so good thing

It’s a paid service. So far - not subscription based and rather affordable - but hey, what if it becomes subscription based in a year or two (ie. Endomondo)?

It seems that the waypoints are generated whenever there’s a junction. This is a good thing. However, when there are two junctions one after another not far apart from each other (like, 20 meters), the watch vibrates and shows way too many notifications at once: Upcoming waypoint -> The waypoint -> Next waypoint. In situations where there’s more distance between waypoints - it works brilliantly, but when close - it’s not good. This is a problem when there are two turns one after another - one left and the second one right. You might miss the first notification and focus on the next (upcoming) one. The solution? Some kind of threshold and more waypoint types combining the turns.

ETA to next waypoint has lost its usefulness now as it’ll basically show ETA to next turn. For long routes that have more strategic waypoints the ETA itself has lost its purpose.

Egika

@prenj said in 2.14.12 is here:

Points of interest creation and navigation: Save important locations in Suunto app or on the watch. Navigate towards those locations with your watch.

What exactly does this mean? Can you enter the coordinates of a POI in the watch itself like we used to do with Ambits? I was unable to find any changes with POI-s in the watch.

how about reading the manual?`
https://www.suunto.com/Support/Product-support/suunto_9/suunto_9/features/points-of-interest/

markytarky

@egika ok, but what is new about that? This was there for ages? So what new functionality?

isazi

@markytarky I am assuming that POIs are out of beta in the app, so new users know that they can now create and modify POIs in SA, something that was not there before.

Rob33

@isazi A silly question, what does Komoot bring besides SA? the possibility of creating waypoints more easily?
or an indication of changes of direction even without waypoints based on following the trail of the route and taking into account the map?

isazi

@rob33 in general Komoot gives you the ability to create routes (with automatic routing based on user preferences) on your computer. In particular it transfers automatically routes to Suunto App, and the routes contain automatically generated waypoints for the points where you have to turn, or change direction. The waypoints have descriptive names.

markytarky

@isazi I actually think is also out in the PROD version. I checked the app store and it is there (version 2.1.0.) Since then two other updates went out… So no new non-beta people.

isazi

@markytarky you are forgetting the new users, that are buying the new watches and do not know that POIs are supported by the app

Rob33

@isazi the waypoints generated automatically at each intersection + the waypoints created when recording the route (sometimes different from turns)?