Haha, good catch @el.Fakir ! Maybe the next firmware with provide teleportation feature. Beam me up to the surface!

Teleportation bug: User @el.fakir caught a good bug in the dive plan: Suunto Nautic does not consider ascent rate in its calculations. Following screenshot red highlights that Nautic assumes instant teleport from 36m to 9m. [image: 1769418288877-c7da9e3b-ca88-4c13-b2df-c19ff83d1ebe-image.png] Link to original post: https://forum.suunto.com/post/184204

@Liviu-Nastasa Sorry, you shared your “official” distance and GNSS (RAW data) measured distance: 14,44km vs 14,65km. That’s the exact behaviour I’ve been watching. In previous watches (RaceS, Vertical), the official distance (recorded in the FIT file and showed in watch) is always close to the GNSS distance. In Race is always between 0.5%-2% less distance than its own GNSS distance so it seems a lot more conservative than SV/SRS in terms of distance calculation, filtering/cutting distance from the “viewed” GNSS raw data. If Suunto has been always recognized as top accuracy GNSS reception watches (dual band, very clean tracks, etc), the calculated distance would be closer to the GNSS distance, unless poor recepction or data is received and discarded for whatever reason. Then, why Race 2 is more conservative? It has a problem in its algorithm and understimate distances? Is it more accurate and then SV and SRS were overestimating distances? Who knows, it seems clear that the algorithm (and final distances, paces, etc) are calculated in a different way and are different. To be honest, I think that SV it’s been a bit generous and overestimating distances a bit, while Race 2 is a bit conservative. May be the “real” distance will be in the middle.

@JebClydeNC no idea about the persistence of the storm alarm symbol, but I definitely do have the baro trend in the alti/baro widget: [image: 1769409972852-img_3117.jpeg]

@giuliosq, hi, considering that you wrote: @giuliosq said in Wrong HR during skitouring: the watch was obviously well positioned. I’m assuming that you’re relying on the optical HR measurement. It’s a common issue that with cold weather (less blood flow) and using poles (sort of sensor cadence locking) the OHR measurement fails, even if the watch is well positioned over the wrist. If you care about HR data, go with HR belt.

@Brad_Olwin said in Subject: Feedback on Zone Sense accuracy: Short intervals and Zone 2 threshold shifts: I do not know what HR belt you are using. I use Suunto HR belt, and it is reasonably new, perhaps 4-5 months old, and I don’t use it that often. It was the same with Polar H10 before. If I have a truly easy run. ZS remains green. But usually those are Z1 jogs with my dog where we do a lot of stops. But if I am trail running and putting some effort, my ZS graphs are always messed up like in the example above. I think it confuses the muscular stress with the aerobic stress. Aerobically I am well developed and my HR stays in Z1 and Z2 most of the time with occasional Z3 and Z4 and almost never Z5, but according to ZS it is red a large percentage of the time. I guess I am an outlier and ZS simply doesn’t work for me.

@SergioB are there notifications of Suunto App appearing in the iPhone’s message centre?

@MarkG normally there is no issue with activities that long. Hopefully a one off.

After days of using Race 2 HRV i decided to give a try to Suunto Chest Strap again. Yesterday on shopping i bought new CR2025 batteries different brand (Energizer) I put new battery to strap. Wet electrodes of strap. Connected strap with Race 2 succesfully + get strap on my chest. 100% Chest strap battery. I DIDNT start exercise. I just took off chest strap + I took off sensor from belt, everything was laying separate. Next day I started exercise with strap - it was magically 20% batttery left before I started to run. Lost 80% during 24h without using it and having sensor taken off from belt with dry strap so its impossible it could work anyway + battery should last 500h. Next day I started running exercise with 20% battery in sensor, ended up and magically Race2 shows it got 30% battery left Did 40 minutes gym session - still 30% battery. Now i know its not batteries fault. Its sensor from strap/Race2 software that reads wrong battery status or problems with connecting BT. or watch itself. Its my probably last try and post, just wanted to give a info

@Charlie-Needham Totally agree. The flow with Suunto Race for me is quite better. Already had several issues with different activities finishing them by accident.

@jamesGW I’ll second all of these. The ability to import/export POIs from the app in particular. I would also add, the ability to enter coordinates for a new POI creation directly on watch in the field (ie off of maps, guides, signs, etc) without needing the app would be fantastic. This was a feature on the Suunto Traverse and Traverse Alpha, but has been missing the past few years since the Spartan line. A sorely missed feature!

Just created a Marathon Training Plan in the lazest App version 6.6.6. The Assistant asked me when I would like to have my Long Run. My answer: Sunday. Result: Not even one training on a Sunday in the whole 10 weeks. Completly useless unfortunatly… Also its not possible to enter the Race Date like in Training Peaks

@2b2bff Hi everyone, thanks for your input. I’ll enter my maximum heart rate achieved in both sports, but I’ll configure different ranges for each discipline since certain muscles or physical qualities are more involved. Thanks for your contributions.

Thank you for the feedback Pavel “At first glance it looks like doing something like this for Suunto should be relatively simple” Quite cool! Interesting pointers given by NO-DECO and Nandodiver, thanks, I will give a try to both Subsurface and Divelogs