any comments on accumulated ascent on 11.00?

Thx! For looking. So it looks like the same. Watch measures good, recording is good. But calculations for ascent descent filters out too short hills (1-3 meters) and too fast changes.
think it would be more reliable to just add up all changes which are recorded, than filtering something out.
greatings Mario

Hi Guys,

I'd expect more posts on this ? anyone else? Bandit? Doktorko, Italiano75, GarminNut?
One thing that I've realized is that the problem rises proportionally to the ride's average grade.
I've seen good reports on rides such as 40 miles with 1000 feet (=0.5% avg grade) but when we get to 12.5 miles and 2,120 feet (=3.5% avg grade) like I did last week things get all messed up.
Please, we had it fix on 10.51, 10.52 and 10.53.

Thank you,

PS. I'd hate having to revert.

Hi Guys,

I'd expect more posts on this ? anyone else? Bandit? Doktorko, Italiano75, GarminNut?
One thing that I've realized is that the problem rises proportionally to the ride's average grade.
I've seen good reports on rides such as 40 miles with 1000 feet (=0.5% avg grade) but when we get to 12.5 miles and 2,120 feet (=3.5% avg grade) like I did last week things get all messed up.
Please, we had it fix on 10.51, 10.52 and 10.53.

Thank you,

PS. I'd hate having to revert.

hey Marcosasaad!
which was a good version? was there any version on which you can say, that was accurate in ascent/descent calculations?
thx for the Info!

Mario

i have one extra question:

looking at the changelog firmware for the Fenix F5X:
https://www8.garmin.com/support/download_details.jsp?id=11429
there is not written that something for ascent/descent is correted.

looking at the changelog of the forerunner 935: Version 10.10
https://www8.garmin.com/support/download_details.jsp?id=11495
Fixed an issue that could cause elevation graphs to be smoothed and total ascent and descent values to be inaccurate.

looking at the 5 Plus: Version 4.20
https://www8.garmin.com/support/download_details.jsp?id=14317
Fixed an issue where Total Ascent and Descent could be too low for certain activities.

Maybee the Fenix 5X has only been forgotten to implement the correction.
:-)

marcossaad_ , I would love to test 11.00 on bike, however, had to send my 5x to Southampton due to faulty PC connection :'-(, waiting badly for replacement (hopefully comes soon).

Hi,

Follow elements to demonstrate my point.

8.0.0.0 (total ascent and descent values were ok) https://connect.garmin.com/modern/activity/2658926123
8.0.0.0 (total ascent and descent values were ok) https://connect.garmin.com/modern/activity/2694491563
9.71.0.0 (total ascent and descent values were NOT ok) https://connect.garmin.com/modern/activity/2851728369
9.71.0.0 (total ascent and descent values went NOT ok) https://connect.garmin.com/modern/activity/2869935682
10.51.0.0 (total ascent and descent values were ok) https://connect.garmin.com/modern/activity/2943584288
10.51.0.0 (total ascent and descent values were ok) https://connect.garmin.com/modern/activity/2980631516
10.51.0.0 (total ascent and descent values were ok) https://connect.garmin.com/modern/activity/2998953599
11.0.0.0 (total ascent and descent values went NOT ok) https://connect.garmin.com/modern/activity/3087126113

(*) I have edit the “elevation gain” of this activity on Garmin Express from 516m (bad one) to 714(fair one).

Those are comparable similar rides among each other.

Regards,

Thanks for sharing marcossaad_
that would be great to be fixed again.

ok, for me it's time to give my fenix 5 back to garmin and request another (although i do not thing that this will help). they are just so freakingly unable to fix that damn altimeter. i always got and get over 30% less altitude than with gps altitude in garmin connect online - even more than 40% when comparing to runtastic. that is ridiculous! they seem to have been on a better way with the latest firmwares/betas, but now i am on fw 11 and again over -30%.

i can't believe that the devs are so unable. they fix the one thing and destroy the other. other things are never taken care of. for sure this is my first and last garmin device.

ok, for me it's time to give my fenix 5 back to garmin and request another (although i do not thing that this will help). they are just so freakingly unable to fix that damn altimeter. i always got and get over 30% less altitude than with gps altitude in garmin connect online - even more than 40% when comparing to runtastic. that is ridiculous! they seem to have been on a better way with the latest firmwares/betas, but now i am on fw 11 and again over -30%.

i can't believe that the devs are so unable. they fix the one thing and destroy the other. other things are never taken care of. for sure this is my first and last garmin device.

i would not take connect or runtastic as a reference. if i take runtastic as reference i would be awesome in trail running :-D connect gives you also not a "correct" value. same as stuunto movescount. it gives you an near idea to plan. and i like that.
lately i saw a stuunto 9 ascent count. it was far less then the Fenix 5x on V11.00. i think it is not bad yet. (but i can't tell on mountainbiking.) but if you really move to another brand. my 5 cent's: about elevation accuracy, there is no more accurate watch then the stuunto ambit 3 peak. even the never suunto's doesn't count as accurate then this one. and i have to say that as a Garmin user. we often compared our activities. the peak wins. all in all. it is not way off on my preferred activities. (hiking, mountaineering, climbing and trail running). it would be really nice to have the option to continuous altimeter calibration again. (as there was on the F3, to turn on and off) but all in all, i like this watch.