@Charlie-Needham known issue and Suunto is aware, no idea if it’ll get addressed in a future update.

@soisan Perhaps I should change the title of my post. As I observed, perhaps the problem is not with the algorithm itself but with the fact that FusedAlti makes very rapid altitude changes that are not based on reality and that these altitude changes feed into ascent and descent calculation. Would you agree that if someone stands still, the altitude should not start suddenly and rapidly change and that these changes in altitude should not impact ascent and descent? If I am standing still, I shouldn’t be getting extra ascent or descent at a rate reaching 12 meters per minute. That’s what I’ve observed. If you haven’t observed any of that, it doesn’t mean that the algorithm is correct. I’ve done a few dozen runs with with the new software. On most of them ascent and descent were fine. But there have been at least 3 runs already where the ascent was significantly exaggerated by as much as 20-30%. Also, there is another thread that discusses a similar perhaps related issue: https://forum.suunto.com/topic/14423/getting-too-much-ascent-descent-on-flat-routes

@GiPFELKiND Potentially related thread: https://forum.suunto.com/topic/14594/new-ascent-calculation-algorithm-is-less-accurate-than-before

@duffman19 as a single data point, I have compared my multiple (two different Garmins, three different Coros, and three different Suuntos, one of them the Race 2) to my measuring wheel. All of them compare favourably except the Race 2, which measures short every time, in the error range we’ve talked about in this thread (usually closer to 0.5% and not as often up to 1.5%). My wheel is accurate (and technique with it is good), so from my perspective it is indeed that the Race 2 measures short, even with straight and flat lines. A great watch in many ways, one that seems to be a bit off where (imho) it matters most.

@GiPFELKiND You know I am a field tester…When I get home I’ll send a photo on V1, I think it is on there.

@Mattg576 Hi, I was able to do the test this afternoon and the measured value is 2k ohms. The YouTuber seems to be saying that it needs to have a value lower than 10k ohms, so I can consider the belt okay in that respect?

@Egika said in Each Suunto Vertical 2 Limited Edition: @tikgnd If you buy the limited edition, you will receive a code you enter into SA to then enable the watch face for your other watches Hmm, I would buy the watch just for that code. Would sell good here

@el.Fakir So you would probably get sorting with votes also for good jokes, or whatever is voted in the full mess of answers (me included )

Search the forum, it was written recently that Ocean is not dead. But saying when something will be out, the answer is the usual one…

« Zero data as bad sleep »

What I’m asking for is not lower accuracy during activities, but a different operating logic between activity mode and 24/7 tracking. During activities: Keep the current strict SNR threshold. Prioritize signal quality and accuracy. If conditions are sub-optimal, the user can rely on a chest strap anyway. During 24/7 and night tracking: Use a more conservative and tolerant algorithm. Accept a slightly noisier signal instead of shutting the sensor down. Apply stronger temporal smoothing and trend-based validation rather than instant SNR rejection. Never fully disable the sensor unless there is a true hardware failure. From a user perspective, this would solve the real problem: In daily life the watch inevitably moves, rotates, and loosens. Micro-motion, skin compression, sweat, temperature changes and external contacts are normal. A minimal tattoo, as shown in the photo, is irrelevant from a physiological point of view and should not trigger a sensor shutdown. Right now the behavior is binary: Good conditions → excellent HR detection. Slightly imperfect conditions → sensor off, sometimes for hours. This is not acceptable for a device that is marketed with: 24/7 HR Sleep tracking Recovery metrics Stress and resources monitoring A more fault-tolerant logic would: Preserve all activity tracking features. Restore reliability of h24 metrics. Reduce user frustration and false “no data” periods. Align the device behavior with real-world usage. From a technical standpoint, this looks like a software policy choice, not a hardware limitation. Other manufacturers already differentiate thresholds and filters between: Workout HR Background HR Sleep HR I’m confident Suunto can do the same. I’m not asking for perfection. I’m asking for continuity instead of shutdown. Best regards.

@Sportsfreund try this https://testflight.apple.com/join/DJyDC5SU?fbclid=IwAR3jTWlAkPOE4uL_3ehgsHHRV4SGRXAM9NCWEFH34_aMtwfu_Ac6WYzQOJ0

@Squirrel It says 3.1.9

@giuliosq Wrist heart rate is highly individual. What works for you does not work for others and vice versa in all conditions. A car is designed to drive around a corner. Yet it does not what it is designed for if you try it on an icy surface.

# Suunto Request: It would be great if can you make a Switch Window “Compass View” double field. In this case we can assign it to the main screen and have the pressure + compass in a single view. The view would be perfect to hold position and check regurarly during the dive. The limited view should hold the position N/S/W/E markers and bearing indication as in the picture below. [image: 1770198867673-suunto.png] [image: 1770200200608-suunto2.png]