@aiv4r is [image: 0UA9ixY] not a sign? Has been there since I dunno when. There are, from my understanding, already SuuntoPlus apps running natively on the Run, don’t ask me which as I’m not sure.

@Steven-Hambleton I would guess that the typical HW development time is 2 years. Then you would have different teams working on different products. I think this is what we see with Garmin and Suunto. If Apple releases new HW every year, they are likely still taking 2+ years for each watch, just running multiple model years in parallel. Suunto seems to follow the normal Agile development approach for software with 2-week sprints and quarterly releases. In my personal view that approach will emphasise regular releases of customer-visible features and give low priority to quality improvements and architectural changes. It does not have to be like that, but it is a common pattern.

@babychai No no, never used screen protector. Suunto saphire glass is very good, no need to protect it with a weaker layer IMO. But I think it’s a hardware issue, watch is not in warranty anymore, but I can live with it, until Suunto Vertical 3 release :). Cheers.

@MikeC30 this is well possible.

A friend diving with the Nautic received a mandatory gas time alarm in the beginning of a dive today 29/07/2026. [image: 1785315395955-screenshot_20260729_115604_suunto.jpg] Suunto please do something about this. This is not an isolated issue or a faulty Nautic that needs to be sent-in for service, it is a issue in the current firmware…!! See below the response from support, this cannot be true. Triggering an alarm is a serious situation and cannot be left up to the divers interpretation to wait for the stabilization of the calculation. Initial SAC Calculation Phase During the first 5–10 minutes of a dive, the algorithm calculates your breathing rate. A higher breathing rate or sudden depth changes during descent may temporarily reduce the estimated gas time, which can trigger an alarm before the calculation stabilizes. Screenshot_20260729_105855_Suunto.jpg [image: 1785313154703-screenshot_20260729_110121_suunto.jpg] [image: 1785313154717-screenshot_20260729_110344_suunto.jpg] [image: 1785313154728-screenshot_20260729_110626_suunto.jpg]

ah here https://www.suunto.com/en-gr/sports/News-Articles-container-page/suunto-core-2-vs-core-1-whats-new-and-why-it-matters/

Tiny fonts again - poor.

@freeheeler I sold my Ambit 3 watch when I bought my Vertical 1. Now I use a Vertical 2, but I haven’t sold my Vertical 1. I wear it occasionally. Legendary watches

@VoiGAS for the EON, thats correct as they hold both tables. You can switch over or set Buhlmann as default where locks do not occur. But this does not downplay the fact that the ceiling was not followed and decompression was not finalized. This will have impact on further calculations as Buhllman uses its nitrogen buildup for further calculations. So better not to have these sitiations and allways follow the indicators on the computer to the letter. Suunto does make the difference between voluntary or mandatory decompression stops. The RGBM lock only applies to the latter. The screen showed in the link indicates a mandatory situation which is explained by Suunto… you get a warning to go to the ceiling of 6,5 meter. You need to do that within 3 minutes and sit out the deco as long as indicated by the EON, in this case 75 minutes which is far from beeing recreational… If you fail - after warnings like the red ceiling indication and audible signal - to comply within 3 minutes, the computer locks for 48 hours. So you might say it indeed locks during the end of the dive.

@VoiGAS said: The Run is the weight king (queen?) It should as it is one of its selling points…

@sartoric No, no protector, suunto has the best saphire glass And always clean. Maybe it’s a hardware fault as @tieutieu and @isazi mentioned. Well, glad to know that it still working as before on some watches because the timing it changes on mine, sure looks like it was being deprecated. Thank you all for the clarification.

@Egika @maszop I can only share my experiences. I sometimes get the notification when my speed is clearly under 5.4km/h and quite often I don’t get a notification when I walk faster than 5.4km/h. I live in the Netherlands, not a really challenging gnss surrounding. Current pase with gps isn’t the most accurate, but I sometimes continue to hike for over 500 meter and then gps should have a fairly accurate pace.

@elbee Thanks for your input but I wasn’t buying it so did some further testing. Fired up my old 9Peak & connected the HR sensor to that, exactly the same outcome with constant connect/disconnect so it’s the sensor that’s faulty rather than my Race. I’ve sent it back to Suunto via online service request & as it’s only 8 months old I’m hoping for a warranty exchange

Test run today with a Garmin. Race2 passed with flying colors. A huge thanks to the developers. Great job, guys. [image: IMG-20260718-123733.jpg]

@bubuche I would use Runalyze or another external platform for that. Now I‘ve been using the latest updates for a bit, I think we‘re there. I thought about using predicted wind from the weather app, but you end up losing accuracy as soon as buildings are involved. I will look at using the accelerometer perhaps, but felt it was overkill when I started with this app. It might solve the grade latency issue though. I‘ll play around with it at some point.

@Squirrel don’t know. This is iOS beta 3.13

@Squirrel I can only tell what I observe. The gnss data is synced right when your watch is connected to the suunto app on the phone. At least, at some point the sync process is saying it is syncing gps data.

I don’t see this too much on trails but 100% on roads. I think they over corrected a bit with this last update. I constantly get “off route” notifications simply being on the other side of the street running in the correct direction.

Just checked the “new” features in the video of the Ocean: They were all present in the latest update. So I guess we cannot expect a new firmware