@Dimitrios-Kanellopoulos yeah, @sky-runner always provides valuable input. The problem is no time to read all feedback

@Egika those running metrics are far superior in something like the head than in very moving one arm. It is explained in that video. That is also a reason with PODs exist in other brands or chest straps with POD features. And pod features could also be improved in a future firmware update. An analogy is running with an HR chest strap. It’s better than the wrist sensor and if you are running with the strap, is because you do want the metrics of the strap. It has no sense to have 2 activities in that scenario. Watch’s metrics should be avoided when running with the Spark paired (in my opinion the contrary is clearly a bug once you have both products in the same workout)

@freeheeler nope I mean climb guidance

@suzzlo said in Downloading map takes a very long time: @muurain said in Downloading map takes a very long time: Suunto’s cloud service that throttles the downloads but… you can download maps for the mobile phone that are much faster… so… if we think, same server is delivering them… this should not be the problem… Anyway, I can live with it You’re right! I didn’t even realize that, even though I did download mobile maps too And yeah this does seem like an understandable constraint of small smart devices. I too am happy to have the convenience of WiFi downloads, even if they are pretty slow compared to bigger devices. My old Garmin Fenix maps downloaded way faster, but it was via USB cable and a PC. But given the analysis here, the original post does now sound like a WiFi issue or a bug. Maybe try downloading maps on some other place or WiFi…? If the download speed is considerably less than 1GB / hour (or ~2Mbps), it should work faster and there are not many broadbands this slow.

@Highlands These are great! Thanks

@Egika Yes, different colours make no difference unfortunately

@Nikolai-Simonov I have intense jungle training this weekend; I’ll be testing both Vertical 2 and the update.

@gkaempfer Same here

@shamilt1 said in Race 2 accuracy: Suunto either know that it measures distance a little short It measures shorter than the other models. The question is is it more accurate, though?

@Egika this was exactly the bug I referred to in my post. Anyway my point is that there is a difference between fixing watch breaking busy and niggles, so it would be good to know what to expect…

@maszop it’s still there in the last public version (6.8.13). Do you have another one?

@Egika Thank you.

@Wojciech-Kubica I’m very satisfied with my V1, 976 activities 1752 h duration, 32.8k km, no issues. Great sport watch from my opinion… Can it be better? Sure… everything can be better, nothing is perfect…

@herlas Yes, Suunto shows both average powers, with and without zeros and in Wahoo settings, you can set if you want average power with zeros or without. I have set this to without zeros and I got SMALLER average power without zeros from Suunto than on Wahoo. Never got higher values from Suunto. On last ride, the difference was 3,6%. It’s clear, that algorithm will differ Suunto vs. Wahoo, but I think, this difference is high and this is the reason, that I’m not sure, if Suunto really doesn’t count auto pauses to the average power… With connecting to device which doesn’t support dual sided wattmeter, Assiomas should send the instantaneous power at a given time and it should be the sum of both pedals. EDIT: On ride with “longer” snack pause, the difference was 5,1%. EDIT2: So no, the difference is not because of auto pause🫤. [image: 1776505793278-screenshot_20260418-114309.png] [image: 1776505803202-screenshot_20260418-114248.png]

@aiv4r no worries. I think the current way is not bad at all. It just need to be consistent. Having a 5km run as PB for 5k - great, Having a 10.xkm run as PB for 10k instead of the 9.95km race I did last time - accepted Having a 20.4km run as PB for the half marathon - what? And nothing I can do to decline that half marathon PB and go back to the one before… support hasn’t been that helpful with that, yet…

@sky-runner said in Race S: Extremely high battery use rate: I suspect this is a software issue so it is likely the same across all models. Indeed as software issue, but maybe connected with the changed HR sensor algorithm? In that case it is a solution solely for the Race S. But who knows… Interested about your results…

@Mitch9 Just to clarify, in both INT‑INT and INT‑REST modes, the main pace shown is already the mean (average) pace of the current interval, and the Previous Interval panel also shows the average pace of the last lap. If you were referring to something different, feel free to explain. Note that INT-REST mode also displays the current pace in INT panel.

@Olaf-Gottschalk I think you are forgeting that it is community forum and not a Suunto support channel. I get it is frustrating, but make a support ticket, report a bug in a proper way, writing it on this forum does not make it official. And since it is forum for a community, you will get some useful answers and you will get some random text, that is usually how communities work. Anyway, I really hope your problem will get fixed.