My Vertical 2 Wishlist for Next Update in 2026

dreamer_

@James-Alexander think that the music can be accomplished very easily with the headsets (that in any case you already need).

Ze Stuart

@dreamer_ said in My Vertical 2 Wishlist for Next Update in 2026:

Better integration with Spark:
https://forum.suunto.com/topic/15018/suunto-spark/

And Aqua. Basically treat them as the chest strap is treated: sync and merge after, the code already exists afterall. Stops it being a marketing exercise of a feature and transforms it into something useful for us.

Ze Stuart

I forgot, espresso maker. Please. For the summit.

EDIT: altimeter calibration using the elevation data now present on the map!

zhangschmidt

@Ze-Stuart said in My Vertical 2 Wishlist for Next Update in 2026:

I forgot, espresso maker. Please. For the summit.

Hahahaha. Poll idea: Who’s old enough to remember that “feature suggestion”?

Tieutieu

@Ze-Stuart could you elaborate ?

Ze Stuart

@Tieutieu yep.

Present: altimeter is calibrated either by GNSS signal, or manual user calibration.
Suggestion: the maps have topo lines, which suggests the maps have elevation data. Let’s assume they do, and it’s queryable, and not just in the GUI. A 3D GNSS fix takes a lot more time than a 2D GNSS fix. With a map and elevation data, and a 2D fix, you can infer altitude with a reverse lookup: what is the altitude on the map for this lat/long?

Not only does this give us known-accurate elevation data, but the benefit that our barometer is more likely to be accurate, too, as currently the data from the manometer has to be parsed to determine if the change is elevation or barometric pressure. FusedAlti is great, but, why infer when you can calculate?

Unless you meant the espresso maker…?

Brad_Olwin

@zhangschmidt said in My Vertical 2 Wishlist for Next Update in 2026:

@Ze-Stuart said in My Vertical 2 Wishlist for Next Update in 2026:

I forgot, espresso maker. Please. For the summit.

Hahahaha. Poll idea: Who’s old enough to remember that “feature suggestion”?

I am!

Tieutieu

@Ze-Stuart ok sorry I thought you were saying it’s was already available.
It’s been discussed a lot ; for now I have never been disappointed by fusedalti, and I use sometimes altitude calibration already available (out of exercice), mostly after long car travels that lead to « altitude errors »

koivikko

@Ecki-D.
I really hope the developers are reading the suggestions. I am new to Suunto and am struggling with all the limitations in comparison with Garmin. Double taps on buttons would be great and of course the possibility to map more useful things to the buttons.

I would vote for your post, but cannot for now, as I need to gain some reputation, first.

maszop

@Ze-Stuart Currently, the altimeter (together with FusedAlti) works great, and I can’t remember the last time I had to manually calibrate it before an activity. The readings are very accurate.

The last problem is with strong winds, although less often than before.

Ze Stuart

@maszop it can be very accurate, but again: why infer when you can extract? I see FusedAlti as excellent, when you don’t have a topo map with a pin on it to look at. When you know where you are on a topo map, you don’t need the overhead as primary.

Put another way, in my scenario above: you have a recent barometric pressure reading for somewhere near you - let’s say an airport - do you claibrate to that, or do you calibrate to the sign that you’re standing next to that states the altitude, as measured by RADAR?

I think there’s a bug in the most recent firmware; two times since updating, I’ve come back from an activity and my altimeter has been way off. Really odd: perfect the whole time, then I stop, save, and I think it was 60m off or something.

dreamer_

I have noticed another bug. When I wake up to the bathroom, let’s say, after 4am and I use a shortcut for the flashlight, the watch triggers the morning report instead of the flashlight.

Can someone report this internally?

Tieutieu

@dreamer_ is it specifically the shortcut that triggers the report, or pressing any button does it also ? On my race s sometimes pressing a button triggers it, sometimes not

dreamer_

@Tieutieu I have the flashlight shortcut in the top button. If I long-press that button it triggers the morning report instead the flashlight but it depends on the hour is pressed.

It can happen at 5.00AM but not at 1.30AM. But I have seen this issue at 4.00AM.
I usually wake up at 6.10AM. The very first thing I do is press the shortcut for the flashligh and the watch triggers (every day) the morning report instead the flashlight.

maszop

@Ze-Stuart “If it ain’t broke, don’t fix it.”

Are you sure contour lines are more accurate? There are plenty of areas where they are completely wrong (e.g., the Dolomites). And even their theoretical accuracy often comes with a much larger error than barometric altimeter readings. It’s no coincidence that barometric altimeters are the most popular and the most accurate.

Ze Stuart

@maszop ha. Well…

Is broke (at the moment), do fix it.
That’s a valid reason to have all three. The way I’d put it, as an algo…

if (FusedAlti confidence is < x) 
use contour datum
else
use FusedAlti
fi

Or just expose it to the end-user in the alti calibration options. I’d really appreciate that functionality. FusedAlti confidence can be determined in the same way other Fused* is: improbable data change, eg altitiude change greater than a rate of x, with x having multiple vars depending on activity.

Fenr1r

@Ze-Stuart Is there any evidence that the contour lines represent embedded elevation data (rather than being simply image elements)?

Mff73

@Fenr1r
There are more evidences that contour lines are precomputed data from various sources and converted into graphical elements when maps are generated.
No elevation data in map themselves.

Ze Stuart

@Mff73 @fenr1r who wants to download a map file and grep it for strings?

Joking aside, it’s just an idea. We don’t need to solve the problem; if Suunto like it they have, somewhere, the elevation data. They can figure it out. Mebbe there’s a way to write a S+ extension, but I’d rather not.

Fenr1r

@Mff73 That’s my understanding but @ze-stuart seems to be assuming otherwise, hence my question.