@freeheeler nope I mean climb guidance

@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)

@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.

@gkaempfer Same here

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

@Egika Yes, different colours make no difference unfortunately

@Highlands These are great! Thanks

@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.

@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…

@jjpaz I have a large number of trail runs with Race2 and V2 and they are essentially identical. I can share data, several different firmware and from 45 min to 7h trail runs. I am in the US with mostly open skies. Part of the observations may depend on the environment as I believe all of you that see shorter distances with R2. However, maybe not a firmware bug but maybe design differences including antennas. I always see fewer satellites connected to R2 than V1 or V2. Could impact distance when GPS conditions are more challenging.

@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…

@Stoke80 You’re welcome. Tomorrow, I’ll ride to cottage and back. 40+40km without pause. I’ll let you know, if I got same average power. I’m curious about that.

@Brainicus 4th degree not needed…I’m neither moderator or suunto related. Even some users here are close to suunto, it’s still supposed to be a help forum between users, not an official suunto support tool. If I had wanted things to be better I guess I would had created my own brand and done everything well since begining and better than garmin, coros, suunto and all the others, and promise a lifetime update support with clear vision of what tech and developpement will be in the futur… I personnaly use SV1, it’s a 3 years old watch, it has already been improved a lot, and I’m confident we will have updates, but also understand hardware can limit update in the (close?) futur. SV1 works like a charm, can for sure be better but is already a best seller on his kind. For ocean my understanding is that it’s a device that must at first be strong on “diving” features and that it can’t suffer about regression bugs on those features. So I guess improvements and testings can’t be nothing else than 100% sure.

@Gunnar said in Map Design Update 2.53.42: memory is not storage Unfortunately, I can’t find any information anywhere about the difference in RAM between the Race and the Race2.