@Adrian.S I moved from the Vertical 1 to the 2. I was really unsure about AMOLED, but now, for me, MIP is history – I’d never go back. The only thing I miss is a slightly dimmer mode. ‘Low’ is still a bit too bright, but it’s a small thing they could tweak later.

@Joaquin this is excellent news. Thank you so much!! Fix is expected for Q2, right? I bought the Race 2 and I skipped it because of this issue, but the thing is I’m very thin with small wrists and after several runs, I think the Race 2 is very likely the more convenient for me than the Vertical 2. Please, remember the Spark needs also some important work because at this moment we even have overlapped audios and the experience it’s somehow disgusting considering the price. There’s a feedback thread here, of course. I hope you can evolve the software with fixes and something like an integration into a Suunto ecosystem, because the hardware is really worth. They are incredible well built and sound quality is really good. I know this is not the thread, but I wanted to tell you not to forget about that product. I really think Suunto has a very big opportunity here. And you rock guys, really. This is the way.

@Tieutieu said in New on Dev-side..... Race Pacer with planned segments/paces: the only “issue” you could have with your preload plan is that even if you plan your 2,45km @5:19/km segment like in your exemple, on the field there is a lot of chances that your segment will not be 2,45km Yes, as someone who uses navigation routes extensively I can tell that whatever distance was planned, it always end up being inaccurate. In my experience, when running on trails, planned distances can easily be 5% too short. For example, If the on-the-route distance to a waypoint was 20 km, it reality it can end up being 21 km.

@2b2bff well well well … if you tell to someone who is doing a diet that he lost 5000 g and to his wife that she lost 5 kg … you are right … this is not the same … the wife will be super happy but the man wearing a suunto and for who 43 and 43.0 make a difference will start to question himself about the precision of instrument … how it could have been possible that he arrives preciselly to exact 5000 Joking !!!

I mean, with the watch in Spanish (without touching anything in the phone), the issue is there. With the watch in English there’s no issue. I’m not sure about these headshets. I expected better firmware. There’s no integration either and touch is too sensitive. Physical buttons are much better while running in my opinion.

@garyt687 This post honestly deserves way more attention. If Suunto really wants to break properly into the tech diving / enthusiast market, this is exactly the kind of feedback they should listen to. What’s frustrating is that the hardware actually seems really solid. Big screen, long battery, GPS, nice design… it genuinely feels like the foundation for a top dive computer is already there. Most of the problems you mention sound software/firmware related, which means they could realistically be fixed. And the thing is, when people ask for dive computer recommendations on Reddit, Scubaboard, forums etc., it’s usually experienced rec divers and tech divers answering. Those communities massively influence what people buy. If those users don’t trust features like GF99, compass behavior, or GPS tracking, word spreads fast. The app point is also super important. A lot of divers want a proper digital logbook with deco info, profiles, gas switches, equipment tracking, dive numbering, all that stuff. Right now it sounds like the app is way too basic for the audience Suunto is targeting. But honestly, with the hardware they already have, this could become a seriously good platform if they iterate fast and actually listen to users like you. Btw regarding the entry/exit GPS points: why are they so wrong exactly? In theory those should be GPS-corrected at the surface before descent and after ascent no?

@MirageDev Hello , what could be really interresting is at least to have the capacity to develop some widgets that we can suggest to Suunto … up to them to decide if they are valuable or not and get inspired I’m sure we have soem interresting ideas … and at least as not suunto has a “demonstrator” It could be nice that we use it, develop a widget and then “sell the idea” to them Here an example of a widget that I miss in my SUUNTO There watchface are beautiful and the last one of the Vertical 2 … Simple => I do nto want to change it all now … it really great BUT BUT BUT A sport watch is before sport … a watch … And all what concerns time is not so easily to access and will agve deserved to be concentrated in a single For example : I will have been super happy of a new widget where I can go and that concentrate all this below Current Date in big Current Time <-- just in case I choose a watch face with needle instead figure so to offer a digital view percentage of battery <-- it’s also a matter of time : how long my watch can work ? Second time what is the next alarm set and in which amount of time it will ring what are the other future alarm set … and the same when will the sun go down <-- just this so to not replace the sun widget

@enriqueescoms Hello Here a new version I realized while looking to suuntoplus big number that in face I can also use the total full scren iI want, so I decided to let the original white below part because I feel it is nice, but instead to remove the clock on the top so that I can now use better the screen which allow me to show both the thousand informations as well as the unit information in a better manner here some screen shots : for the distance and compared to the sport screen with 3 fields when the swimmer swim already 450 m [image: 1779232089752-c8704d52-5b10-43f7-8d9d-e9c155ca2259-image.png] the same but now compared to the graphic and when a swimmer already swim 1 kilometer and 25 meter [image: 1779232170551-1354e6a9-4868-4165-b95c-ed8b3993d247-image.png] for the time compared to the sport screen with 4 fields when it is 1 h and 10 minutes in the morning … yes yes there are crasy swimmers … or me !!! [image: 1779232316977-7df9c74f-0222-4f82-adc4-1092920f36b1-image.png] and for the duration compared to suunto plus big number after 14 minutes and 5 seconds [image: 1779232240218-527a5090-35b3-4168-88c0-3696027d3a12-image.png] the beauty is that now if I want I can also put some unit information like km. and m. in very small font for the distance… eventually I could also complexify even more the app byt puttin around it the famouse blue, green, yellow, read circles that show in which heart area I’m currently located … I cannot put here some ZIP files so I cannot give you my proof of concept but if someone wants it I can give it for free … if this allow some more people to raise that having a bigger number app which has really giant font to SUUNTO … then I give it without any royalties

I’m having trouble connecting my Suunto heart rate belt to my Suunto Nautic. My software version is 2.49.32. My smartphone is connected to the Suunto Nautic. I open the Suunto MobileApp, go to Settings, and select “Heart Rate Monitor Pairing.” I can see my current BPM changing in the app, so I know the belt is working and transmitting data. Then I go to the Control Panel on the Suunto Nautic and navigate to Device Settings. However, I only find “Paired Devices” and there is no “Pair New Device” option. I would really like to get this connected. Has anyone managed to get this working?

@Egika said in swimrun mode: @microniko Yes, the S+ app does (or should) detect the transitions and create laps. Just this happens all within the single sport mode (running). So you end up with a running activity that has laps for when you change in and out of swimming. It is a bit strange that you can’t use it in multisport modes… Anyway, I’ll just have to live with it. Repeat option: […] OK. I understand. Thanks!

Hi @isazi, this is indeed using the OHR. In the meantime, I’ve purchased a heart rate belt which I sometimes use during peak & valley power walks. The described behavior cannot be reproduced when using the belt, which operates accurately. So, it seems to be rather a problem of the OHR

@JSampson wished you had the thread properly. As Runalyze can get the data it seems like an incomplete implementation of the Suunto API at TrainingPeaks… So, Suunto isn’t to be blamed - in this case…

@sky-runner it does actually. It always starts to connect to the last used, but advances to others it finds. But you can disable each sensor per activity and it will remember this…