On Suunto website: Offline maps, improved navigation What is improved in navigation and different than V1?

@Hari-Seldon said in 3.21.14 Rolling out: Added support for the “vertical running” exercise mode. I’m glad to know that the altitude in the profile is purely barometric…

@Brad_Olwin It has a MEAN absolute difference of ±10 BPMs and a 95% confidence interval of around 4 BPMs. Meaning that for most of the 58 tested subjects the estimated value deviates by 10 BPMs and 95% of all tested subjects are in the range of 6-14 BPMs deviation. The data points also seem to be gaussian distributed. So for only less then 5% it has a lower deviation of around 6 BPMs and for some of these 5% it has even a deviation of more then 14 BPMs. Of course, accuracy is highly subjective…but statistically seen, from the available data that I have, I do not use ZS at all. For me personally, when I know that on average, even under perfect conditions, the ZS estimated threshold is off by 8-10 BPMs in either direction, it is not usable for me. 10 BPMs above my threshold is for me all-out running for 1km while 10 BPM below, is the HR that I have on the first kilometers of a Marathon. For me that is just way too much deviation to rely on it for proper training control and also dangerous for people that believe they can trust the value and base their training on. That I am not the only one this applies to, is already reflected by the statistics and the numerous posts from people in this forum that struggle with the value that ZS gives them and are looking for help to understand and interpret it. Communicating the average accuracy under perfect conditions to the average non-expert consumer, would already help them a lot to interpret the value for themselves. For the future, I am looking forward to more data and studies and maybe an improved algorithm, as the concept is really nice! But right now, it’s not there yet, in my eyes.

@GiPFELKiND said in I have zero confidence in Suunto route navigation!: @sky-runner wow thats incredible inacceptable. But that is no new Problem. In complex routes its necessary to show at the Phone. This didnt work Like exspected. At no time you can navigate a Special route with your Suunto. I navigate“Special” Routes all the time, most of them off trail. For example, a four day fastpack in the wilderness with nearly 3 days fully off trail and no issues. However, I do admit there are issues. The auto-reverse can cause issues and I have had an issue @sky-runner describes but long ago with the 9baro before maps. I will ask around some and see if other testers have encountered this.

@Mff73 COOL！tks！

@Desdinova said in So Difference between Race 2 and Vertical 2 = Flashlight and Digital Crown: Just seems a little odd there’s little product differentiation here. Because it is cheapest for the manufacturer.

@Tomas5 with almost every Suunto watch I had bad OHR readings when riding my bike. Usually it would eventually just fall into the lower 80s and stay there. Race 2 was the first watch to ever got OHR in cycling right for me!

@Sandrine Tu écris qu’elle n’existe plus et que tu ne peux pas la désinstaller mais as-tu essayé de l’appairer à nouveau (Paramètres > Connectivité > Appairer un nouvel appareil) ?

French review from Jerôme blog cardio gps

@minimark069 Suunto developers haven’t figured out the loop in the menu yet.

Same problem for me. battery drains à around 1% an hour during daytime, 0.5% per hour during the night. I’m pretty unlucky since I already had a sync problem last year with a new update.

@soisan Look at the graphs - the HR data from the belt is rock solid for the first two examples - that’s downloaded to the app from the watch. Why is the graph stored on the watch completely different from the graph correctly displayed on the phone app? It’s amazing that nobody can see this. The detailed phone app graph shows a completely consistent (and stable) HR recording. Yesterday I went for a walk with just using the optical HR and the two graphs (watch/app) were identical - ZoneSense was activated but there was no data available after syncing. Basically - the software/firmware is a mess. It was the same with the counter being blocked in real time ZoneSense - first admission that there was a problem was the recent firmware update with this error being listed as having been corrected. I’m not going to be using ZoneSense at all now. I’ll see if by getting rid of ZoneSense also removes the problems with the stored graphs being different on watch and app. So far I’ve identified 3 different problems - one has been fixed with the latest firmware update.

@Baarbix First question: I’m not aware of that option, I do not think is possible Second question: yes, that function is implemented

@Florentin 26.0.1 released, so far so good. Sync is continuous and complete.

@Mff73 lets hope for saving Option some day in the App next Post 2038

It is fixed for me

@cheetah694 That doesn’t solve the problem, but it does minimize the inconvenience. Of course, the price can be high: not following the route track and not seeing the profile.