Did anyone find a solution for this? Even the current user manual for the Race S says that it should be possible to change the view: Altitude navigation: bottom: remaining ascent or descent (tap screen to change views)

Second crash today in about 1 year with the Race S. Crashes in the last 20 years with Garmin FR201, FR910xt, Huawei watch, Ambit3, Suunto5 and Suunto9P: Zero! I don’t get that we are discussing about how many crashes per year are normal given this relation.

@Dimitrios-Kanellopoulos This could be something useful.

@sky-runner sorry I’ve missed that thread. I’ve read it now and I can confirm many of the issue you have described! Thanks also for the magnetic declination tip

@Mff73 said in And it crashes mid run: @Kenneth-De-Cocker Besides software problems, you might have an hardware one which is happening in rare situations and causing the crash (es). You should maybe contact support while your watch is still under warranty. I contacted support they also said to return it, just a small problem I have a big trainings weekend coming up and also I participating in a race half September. They said if I send the watch it could take up to 14 business days … so yeah not ideal for the moment so perhaps I’ll send it off after that race. Also gonna take zero risk on race day and use a second watch an old polar but it has no gpx function which is mandatory for the race so yeah better hope is stays alive during that 100km.

You can manually edit TSS in the App. Just open the activity and choose “edit”.

@James-Bellin Yes, I sent it to the SAT and they changed it for a new one.

@zadow Unfortunately I had to return the Race. NATO strap did not helped. I am waiting to Race 2. It seems a bit better design. Till then I will use Garmin Epix Pro that I got as a replacement of Epix (non pro).

@Tami999 well it stops charging if you put phone next to it on the desk as it’s so sensitive

@BastMaSVSRS9PP Suunto does only use movement data for sleep tracking. But so does the Apple as well. With a much greater success. But Apple has a lot of money and time invested in those health related things. He mentioned as well that it is impossible to get the sleep stages data for analysis. And looking at the praised Suunto API you can see that they are not included…

Hello everybody Same trouble to me: 120 meters of ascending instead of 2 meters. I’m totally disappointing. I don’t have warranty because I purchased used watches. But still believe that it is a software trouble. Does anybody resolve the issue successfully? And what would you say about software downgrade, maybe it helped somebody?

I’ve returned the Race… I would like to have an AMOLED but I follow a lot of routes and I do not want to suffer this abnormal behaviour. I will continue enjoying my Vertical.

@dommywalsh mine is two weeks old and I have just had this happen at one hour and 55 minutes. After it reset itself I began the activity again but when downloaded, the app picked up the activity first but didn’t analyse it so the metrics of the activity don’t appear.

@borgelkranz thank you these look great

@Miroslava said in Vo2 max: It’s frustrating when I can actually see that I’ve improved and it doesn’t change at all. VO2Max changes very little once you’ve passed the large gains going from an inactive person to a regularly training person, so my advice would be to forget that specific data point - which anyway can only be roughly estimated by our watches. Instead focus on the real data, i.e. your perceived effort plus actual Heart Rate at different paces over distance and time. As for Company estimates… Garmin have always grossly overestimated my VO2Max. Since I began running at the age of 53 until today at 65 they regularly put it at 49, 50, 51 ml/kg/min which gives pure fantasy running times over all distances (meaning much, much too fast). Suunto also overestimates it as being around 44 to 45 which, again, predicts racing times I never will reach. Coros however came closer with their 39, 40 to 41 estimates which tallies better with a Cooper Test I did (run 12 minutes at controlled max pace) which gave 42. Still, those figures are all estimates, and with little real world application. If you would like a better insight as how to train (paces for different goals) use a lookup table. Plug in your best effort for a known distance and adopt however you feel. Example: https://www.finalsurge.com/tinman-calculator Taking myself as an example: A couple of years ago I did 4:11 as a personal best for 1 kilometres. Putting that in at the calculator they say run at 6:30-6:57/Km for an Easy pace on flat ground. Jupp, that is what I normally do for the long aerobic sessions. They say do 4:29-4:34 for VO2Max pace. That aligns with the vVO2Max (Velocity at VO2Max) of ca 4:30 I found some years ago [Run at a controlled max pace for 6 minutes - the last 2 will feel like you are dying; the average pace over the 6 minutes is your vVO2Max]. The “Equivalent Race Times” of the table gets progressively less accurate with such a short distance entry as 1 km - they predict 01:49:47 for a Half Marathon while I did ca 02:00:00 a few years ago. But that is the nature of generalisations and different distances. If I plug in that real world race time the Easy pace is stated as 07:04-07:33! Very, slow for a flat ground run. I would hardly reach 70% of my Max HR there…

Can you share the altitude profile as shown in the app of this activity?

@dr_free yes

@peegee I use walking without GPS