@Bjuanito nothing changed in that respect, unfortunately. I do not know the BLE standard for speed/cadence so I do not know if there is a way to determine if a sensor is speed or cadence (or both) and act accordingly

@Josaiplu RPE is a very good metric, but feeling is not exactly that and there was a thread where one could see that people understand that quite differently, therefor any addition to algorithm does not make sense also in my opinion. (But Recovery is also kind of made up metric that has not much science behind it, so maybe it fits, idk)

What do you mean with “never worked”? They aren’t there at all? They are not what you expect?

@LGoSo nice, then I got you now! Yeah, you are absolutely right and good observation! Yes, if they would correct for that systemic error, they would get less average absolute deviation while also having more consistency. Therefore, they would need to say that measuring the HRmax with their all-out test and then estimating the T2 by x% of measured HRmax, outperforms ZS/DDFA! That’s why they probably did not try to optimize it and just discussed that it is ok to take the 85% of HRmax, as that is what is always used. Maybe with their test somewhere around 88% or 90% would be really accurate. That’s really disappointing…

@owend said in 3.21.14 Rolling out: I still need to use it in an actual session to see how well it works, but the interval training main screen does look clearer from initial check. Here’s how it looks on previous version on the left vs this new one on the right: [image: 1759146782988-intervals.jpg] I was hoping with this update that we’d also see the ability to customise the other screens though like in regular sports modes Edit: also found an article about this update that indicates there is a 5-sec countdown and out-of-range alerts for intervaals which would be welcome additions. IMHO with this update I receive too much alerts during my run. Is there a way to reduce that?

@sky-runner Ok, I think I see where you mean - that small section between the two dots (waypoints or turns)? So you think it just skipped ahead while you were somewhere on section 6? (Sorry, I’m trying to follow along.) Perhaps in addition to the watch always trying to figure out which direction you’re traveling, it’s also always trying to figure out where you are along the route, rather than just assuming you are strictly moving from one point to the next. So maybe somewhere along section 6, it incorrectly guessed you were farther along in your route (since the paths cross at 6/7) and updated the directional arrow accordingly, but hadn’t yet updated the distance remaining since that lags behind. I’d bet if you had followed the light blue path, away from your car, the remaining distance would have also skipped ahead soon after. But since you followed the route as planned, it didn’t have time to adjust to this mistake. Whatever is going on, you are correct that it’s screwy and inconsistent.

I also play Pickleball and was surprised to find that Suunto didn’t have a Pickleball mode. Wish they would add that.

@duffman19 yup, it’s bugged.

@jakexuan U just can’'t

@cheetah694 thank you for the answer

@sorinus at last a review that shows flashlight use => seems quite powerful !

@Tomi That’s what I thought after the hotfix, but unfortunately it still goes wrong regularly… Zonesense still stops after an hour of training.

@frullewulle same here, no issues since update

When I read the subject of this topic, I thought it would be about the future development of the Suunto Ocean. Unfortunately, that is also true.