Race 2 accuracy

[shamilt1]

I was thinking about returning my Race 2 for the Vertical 2 because of this issue, but in the end I decided to stick with the Race 2.
I’m really glad to hear this issue will be addressed!

[dreamer_]

@shamilt1 said:

I was thinking about returning my Race 2 for the Vertical 2 because of this issue, but in the end I decided to stick with the Race 2.
I’m really glad to hear this issue will be addressed!

I did that because of this and while the V2 is a fantastic device, I’m personally finding the Race 2 was better in my wrist (I’m thin with thin wrists). Buttons are also higher profile and I wish they were lower, like the buttons of the Race 2. But that’s my experience, of course.

[shamilt1]

@dreamer_ I’m built similarly to you so glad I stuck with the Race 2. Maybe you’ll change back after the update!

I didn’t want to pay an additional £100 for a torch and bigger battery, neither of which I need. This would also come with more bulk and omission of the scroll wheel which I like for zooming the maps.

I wonder whether this update will be included in the next quarterly one or a separate earlier fix…

[YoeChr]

Any updates on improved accuracy atm?

[YoeChr]

Maybe nice to share this video by The Quantified Scientist. He compares the gps accuracy of Suunto watches (R2 and V2) with Garmin, Polar and Coros.

https://www.youtube.com/watch?v=TuxK1XP1blw

[EzioAuditore]

@YoeChr saw it and imho it’s the biggest b…it coming from him. Having the watches on a flexible strap where some are facing the ground and others (pretty sure it’s the forerunner) facing sky. If not the gps it will throw off every algorithm based on the steps/gps calculation. That being said I confirm that the R2 is shortening all my runs compared to the V2 and others. In some cases as much as 250m on a 20km

[isaac.net]

@EzioAuditore and once again it must be remembered that the GPS data collection of the Race 2 is very good, the problem comes later with the software processing of the information to calculate the distance to be displayed.

[YoeChr]

@isaac.net Is the postprocessing problem only visible in Suunto App, or also on outlets like Strava and TrainingPeaks?

[isaac.net]

@YoeChr the post-processing issue is visible on all platforms that import activity data from Suunto, as this is the total distance data that is sent. In Strava, this can be corrected using the “Correct distance” option for the activity, but this is a web-only option and requires manual execution.

[Egika]

The new update of today introduces a different distance calculation for Race 2.
It should solve the under-reporting of distance.

[Svenning]

Thanks @Egika! Great! I’ll test the GPS tonight right away.

[GiPFELKiND]

@Egika now we run a half Marathon and the Race 2 calculates a Marathon? I never saw a distance Problem at the Vertical 2

[Egika]

@GiPFELKiND said:

@Egika now we run a half Marathon and the Race 2 calculates a Marathon? I never saw a distance Problem at the Vertical 2

this thread is about Race 2.

[jjorgemoura]

@Egika As a Race 2 user, these are good news.
As a Software Engineer, I’m wondering and curious why Race 2 and Vertical 2 have different methods of calculate and/or report distance. Unless is an Hardware related issue.

[isazi]

@jjorgemoura different antenna design.

[isaac.net]

I did a test today: a 9.50km walk (final distance on the Race 2). Strava, after applying the distance correction, showed 9.51km, the same on the Sportstracker map. So, this first test seems promising for resolving the issue

P.S.: If the watch had a live tracking system integrated with the Suunto app itself, it would be perfect for me.