Software version 10, I am confused

10.0 for me fixed elevation. Better than 9.73 imo.

I have been running 10.0 for a few days and with a few MTB activities and the elevation issues I was previously experiencing seem to be resolved. Ironically, now when I visit Garmin Connect with a browser, I no longer see the device (5S) listed under the activity and therefore don't see the elevation correction option listed. I probably don't need to correct the elevation moving forward but is this normal behavior?

The whole point of beta software is to test it in a wider range of use cases, with different sensors, etc before it is released as production software.

Sometimes that testing uncovers some problems with a new feature. Sometimes it is a simple fix to address the problem, sometimes the fix will take longer, more thorough testing, etc. At which point the developers have a choice of delaying the entire release of the production software, or release the production software on schedule but postpone the new feature until a later release.

As the FW included a new connect IQ platform for 3rd party developers that had been pre-announced, I am assuming they chose to release on schedule without the elevation correction feature, rather than delaying.

There's a saying amongst experienced endurance athletes "Never try anything new on race day", whether that is a new pair of shoes, a brand of energy gel you haven't used before, etc. And personally, I include updated watch software in "anything new", so I turn off the firmware autoupdate a few days before a major ride/run.

The whole point of beta software is to test it in a wider range of use cases, with different sensors, etc before it is released as production software.

Sometimes that testing uncovers some problems with a new feature. Sometimes it is a simple fix to address the problem, sometimes the fix will take longer, more thorough testing, etc. At which point the developers have a choice of delaying the entire release of the production software, or release the production software on schedule but postpone the new feature until a later release.

As the FW included a new connect IQ platform for 3rd party developers that had been pre-announced, I am assuming they chose to release on schedule without the elevation correction feature, rather than delaying.

There's a saying amongst experienced endurance athletes "Never try anything new on race day", whether that is a new pair of shoes, a brand of energy gel you haven't used before, etc. And personally, I include updated watch software in "anything new", so I turn off the firmware autoupdate a few days before a major ride/run.

All excellent points, but what is strange in this case is that while the release notes do not include the elevation fix, my issue (and Lewis_C as reported here) is completely resolved with the 10.0 release. Maybe it was accidentally or intentionally omitted from the notes...

I'm on 10.52 beta and the elevation problems are still the same than on my last Firmware 9.2
Always about 50m behind the real value (like from gps height or readings on cable car stations, maps, etc.).

Recently I tried to go with the "tracker" activity mode on my F5 because I read a tip on a review website.
It was the first time since a long period that my F5 was "just" 6m behind the reading on a cable car station.
I will test this again on my next ride or hike to confirm.

I'm on 10.52 beta and the elevation problems are still the same than on my last Firmware 9.2
Always about 50m behind the real value (like from gps height or readings on cable car stations, maps, etc.).

Recently I tried to go with the "tracker" activity mode on my F5 because I read a tip on a review website.
It was the first time since a long period that my F5 was "just" 6m behind the reading on a cable car station.
I will test this again on my next ride or hike to confirm.

My issue was much worse that that. Attached are two images showing essentially the same MTB ride done months apart. The one with 587 elevation gain was with the firmware just before 10.0 so it was 9.2 (edit: updated with exact firmware). The other is an old MTB ride following essentially the exact same route with the same 5S watch with firmware 8.0, before the elevation issues started and it recorded 1,014 ft elevation gain. As it can be seen, the elevation plot in the bad firmware was showing 57% of the actual elevation gain and the plot is very smooth and missing the correct terrain variation. Using elevation correction does fix the issue but it is a hassle. I was getting consistent wrong elevation gain on the firmware just before 10.0. Now with 10.0 I get very accurate results similar to the older firmware. I hope it lasts!ciq.forums.garmin.com/.../1395912.jpg

For me the issue is also solved with 10.0
This is exactly the same 40 km mtb route performed on different times
Fenix 3 V 8.30 301 m
Fenix 5 V 6.00 305 m
Fenix 5 V 9.20 209 m
Fenix 5 V 9.20 215 m
Fenix 5 V 10.0 295 m

After the 10.0 update the fénix returns at the correct elevation gain.

Arturo J. from Alicante