My Vertical 2 Wishlist for Next Update in 2026

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.

Mff73

@Fenr1r
I understood, it was indirect answer .
@ze-stuart
https://forum.suunto.com/post/187990

Then you can search in the Web, all vectorized map are having only graphical data, precomputed before map generation by the map builders, based on any external data they want / can access (for free or not).

For elevation usable data, you may also read for example how some people are trying to create them in a reedable format and as much precise as they can.
https://sonny.4lima.de/
It is also a huge work to create them, and then, look at the amount of GB for the whole world.
For my country, I use them with android app, and it is taking 6GB.