My Vertical 2 Wishlist for Next Update in 2026
-
- Improve navigation and Climb Guidance:
https://forum.suunto.com/topic/15071/several-navigation-issues-feedback/
-
Better integration with Spark:
https://forum.suunto.com/topic/15018/suunto-spark/ -
Bluetooth FTMS:
https://forum.suunto.com/topic/15154/bluetooth-ftms-support/
- One minimalistic watchface.
The rest is almost perfect for me, just those things.
-
On device music for me like the Run… I would have thought it would be easy to copy over? V2 would be almost perfect then… apart from payments but I can go without.
-
@James-Alexander think that the music can be accomplished very easily with the headsets (that in any case you already need).
-
@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.
-
I forgot, espresso maker. Please. For the summit.
EDIT: altimeter calibration using the elevation data now present on the map!
-
@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”?
-
@Ze-Stuart could you elaborate ?
-
@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…?
-
@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!
-
@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 »