Future S9 firmware wishlist summary

freeheeler

@cosme-costa
and it would be nice to have the correct number of left ascent. I notice that it’s overshooting most of the time in my case

Chronbu

@regger The best feature that could be implemented in SuuntoPlus is an alternative of ClimbPro from Garmin watches. Hope to see it in the next firmware

isazi

@freeheeler meaning the routes created in SA? That is acknowledged and will be fixed.

MiniForklift

@freeheeler said in Future S9 firmware wishlist summary:

@cosme-costa
and it would be nice to have the correct number of left ascent. I notice that it’s overshooting most of the time in my case

I noticed that on a hill run last week. I planned the route in SA and it calculated just over 800m of elevation; in fact after running the route the total elevation was only a little over 600m. Can’t believe the vert was off by 25%! I remember running down the final decent and it was still showing over a hundred metres of ascent left when there was in fact none. On the plus side it made for a slightly easier run than I was expecting

The hill screen was excellent, great to know exactly where you are on the climbs and what you have left to cover. I definitely think the top number should be the total elevation that you have climbed - that’s a much more meaningful metric to have to hand than your current altitude

freeheeler

@miniforklift said in Future S9 firmware wishlist summary:

I definitely think the top number should be the total elevation that you have climbed - that’s a much more meaningful metric to have to hand than your current altitude

absolutely!
it would be almost like a sandglass but the other way around. while the lower number is getting less, the upper number should gain accordingly

markytarky

@chronbu, well I’d like to argue here. The climb pro is not accurate for long distances like 50k and more. So in case, Suunto will do it, pls do it properly. And btw. the same applies for pace pro for long distances in trail running.

@markytarky I used PacePro and ClimbPro on my F6x for my 80km/4000hm run at Lavaredo Ultra Trail and it worked without any problems.

markytarky

@moe67er well, it works. It’s just super inaccurate, e.g., it said that I was climbing when I was descending, and this happens not just on one route but also many times. The same occurs with pace pro when I split the pace, not per each KM but using elevation. It was out. Maybe I wasn’t lucky.

Bogdan1921

So…When is coming the new firmware?

isazi

@bogdan1921 I think Suunto often releases new firmware on the same weekdays.

Bogdan1921

@isazi

Next Tuesday

cosme.costa

@bogdan1921 Important question, What is new? Will us be surprised @isazi ?

PS: Do not answer if you can’t

isazi

@cosme-costa I think we already anticipated some of the bugs fixed in various forum posts, and for the new features I’ll wait for the announcement.

markytarky

@isazi clever answer

Brad_Olwin

@markytarky said in Future S9 firmware wishlist summary:

@moe67er well, it works. It’s just super inaccurate, e.g., it said that I was climbing when I was descending, and this happens not just on one route but also many times. The same occurs with pace pro when I split the pace, not per each KM but using elevation. It was out. Maybe I wasn’t lucky.

Wow that is bad! Is that your typical experience, I thought ClimbPro worked well?

Egika

@cosme-costa whatever the update will contain: there will always be people complaining about it

markytarky

@brad_olwin yeah, it’s working for short runs, maybe the problem is the environment, I run in terain where the up and downs are pretty short (let’s say from 500m to 2km) and if such route is to long I think the climb pro is not able to calculate it right.

Bulkan

@brad_olwin said in Future S9 firmware wishlist summary:

@markytarky said in Future S9 firmware wishlist summary:

@moe67er well, it works. It’s just super inaccurate, e.g., it said that I was climbing when I was descending, and this happens not just on one route but also many times. The same occurs with pace pro when I split the pace, not per each KM but using elevation. It was out. Maybe I wasn’t lucky.

Wow that is bad! Is that your typical experience, I thought ClimbPro worked well?

ClimbPro works really well. It is one of the best features of Garmin’s.

freeheeler

@egika
typical first world problem… we always find something that’s wrong

aalfaro5

@freeheeler thanks for the answer, I use that but I was saying something that you could add on the face watch with 7 parameters for example so you have speed, time, distance and hill inclination (and other things too)