I found the calibration factor on the Stryd wind was substantially (~3%) short on distance originally. It changed significantly with the latest firmware update to be exactly the same as my old Stryd — which is ~1% short. 

Stryd should be stable within…

+1 for this. Live in Denver, and took me a bit to figure out why everything was reporting so short based upon range finder distances. Without altitude adjustments, it provides me little to no good to know how far I got the ball on the launch monitor. 

Generally I compare to Strava. Sometimes I also use all trails and Fitbit. Those three matchup in distance however Garmin is consistently showing less distance. I have tried Galileo and Glonass and also just GPS alone. The results seem pretty consistent…

As I mentioned before - I am okay with the watch not getting 100% accurate results due to rain/sweat/wind (+/- 20m on short distance, even 100m on long distance would be okay) but what I am saying is that the accuracy has dropped recently making it virtually…

When running in a park with longer straight distances, the watch algorithm uses the adjacent data points to "clean up" your heading and distance. While individual datapoints may be out, when you put a number of them together, the trend line becomes pretty…

I had to try out ultratrac on my Fenix 5, well aware of the fact that it may have a different algorithm, as well as has a different GPS-chip and antenna construction compared to the 945.

I used smart recording, and logged my short daily commute on bike…

Update: did another test: no autostart. I'll report this.

----------------

Thanks beta team, as always I'm happy with the ongoing development. However, I did a quick test and LT 'auto start' did not work. Perhaps the test was too short of duration…