any comments on accumulated ascent on 11.00?

I was going to wait until I had a few more rides with 11.00 to report but since you asked...

I have only had 1 ride since upgrading but it looked really good. I have been riding with BOTH my 5X and my 910XT for a while because I had questions about the elevation gain with the 5X. In the past the 5X usually showed about 40% less elevation gain during my mountain bike rides. This time the 5X was ONLY 6% less than the 910XT!!! I can live with 6% and that is the closest it has been since version 9.xx. This is the result after only 1 ride so I am not convinced yet, but I am optimistic. See the attached photo for the elevation comparison (ignore the difference in starting elevation). :)

AgentDBCooper Are you expecting a correctly working altimeter to give the same results as the "elevation correction"? If you are you will will never be satisfied and why not just always use the "elevation correction"? The correction is just a crude estimate based on topography held online - it will almost always understate elevation on undulating trails.

Your quoted activities involve so little elevation gain that it wouldn't take much to account for differences - gusting wind, rapidly moving air from high speed for example.

I am a runner and not a biker - so move a lot slower of trails - but on a run of 150m elevation I often see a variation of < 3m (1 hr activity) and for 10000m elevation a variation of 300m (40 hr activity). This has been consistent across many versions of the firmware.

Hello, this is my first mountain biking with 11.00. (gps 2.30)
The height at the beginning and the end is correct ...
https://connect.garmin.com/modern/activity/3086487740

Hello, this is my first mountain biking with 11.00. (gps 2.30)
The height at the beginning and the end is correct ...
https://connect.garmin.com/modern/activity/3086487740

Looks good, the altitudes seem to match up on you outgoing and incoming parts of the session.

bad accumulated ascent on 11:00 compared with 10.51 or 10.52.

Despite the fact I was (and still am) with AUTOUPDATE OFF, 11.00 has forced its installation on my watch against my previous 10.51 ...and guess what? Garmin has once again messed up with accumulated ascent. Unbelievable.
What exactly do I miss by downgrading? I've heard user settings. Does anyone knows exactly which ones?

Thank you

i am happy with the V11.00 ascent calculation too. did a hike an trail run. both results where fine.

Any one with Mountain Biking?

Here I am!
MTB round track done yesterday with v11.00. Result? IMHO...embarassing....
Here attached the stats with Elev. Corrections Disabled and Enabled.
I know very well that the Elev. Corrections is not the good reference to choose, but the difference is too big and a friend of mine recorded the track with SportTracker (smartphone) and got elevation gains very similar with Elev. Corrections Enabled stats.

So, analysis of the original record (Elev. Corrections Disabled):

• GPS configuration used: GPS+Galileo
  
• Starting point elevation 200m more than reality: I used altimeter autocalibration with GPS, making the GPS fix at a big parking in the town with a clear sky view.
  
• Max elevation point 200m more than reality. But this is alligned with the bad calibration.
  
• Elevation profile of the track seems a little bit smoothed but not so much like it was with the v9.x.
  
• Elevation gain: if I calculate the value from the map taking the min and max elevation of only the two biggest uphills I obtain 1495m. The record says 1420m, that could be acceptable except for the fact that obviously this raw calculation using the map does not take care of the profress of the track that include a lot of other short uphill...On the other side I think that the value of more than 1800m calculated with Elev. Corrections Enabled could be really a too much, I do not estimate 400m of gain more due to short downhill/uphill. Here is difficult
  
• Elevation loss: that is the worst result! On a round track it must be comparable with gain! A difference of 300m on a 1400m total is not possbile! As another member said, the issue I think is with fast moving, with trail running activities I never see that difference (OK...I never done trail running with v11.00 til now) but trail running and MTB could be comparable for climbing speed but sure not for downhill speed. But I must say that the previuos MTB round track record done with v8.0 presents the same issue (1418m gain, 1095m loss), but older (always v8.0) not. So I have one dubt about the settings: for MTB profile I use the autopause when speed is < 1,6Km/h, but I do not remember since when, for sure for the last two activities. I have the suspect that when I stop during downhill (on the last track a lot of times due to not cycle sections) the time the 5X needs to restart the recording causes the lost of some meter of donwhill every time. But I see that the 5X reacts very fast when i restart after a stop...I'm not sure if this coudl really be te problem.
  

Unluckily I do not MTBiking so often, so I would like to ask to other more active MTBikers to reset the 5X with v11.00 and made another recording with a reasonable downhill part.
For my experience a clean installation is the right choice to start testing.
To do the backup and restore od the data before and after the reset: https://support.garmin.com/en-GB/?fa...PZ6PboXu5Nf7d6
To hard reset the device:

• Hard reset / factory reset:
  
• Turn OFF the Fenix
  
• Press and HOLD LAP button
  
• Power on (still holding the LAP button)
  
• You will get the menu “Clean user data: Yes/No?” release LAP button
  
• Choose yes
  

(I think this does the same: https://www8.garmin.com/manuals/webhelp/fenix5x/EN-GB/GUID-46551446-AAE7-451C-B857-7D86AD7747EE.html)ciq.forums.garmin.com/.../1414013.png

Hi ziki77! That sound's not good! just for interest, have you tryed to export the original fit file and open it in an fit file viewer (i use GPXsee, to see what is actually recorded? so if the recording is smoothed or only the calculation.

i did a short flat run (as flat as it is possible here in the alps :-) ) with a view up's and down's. the small foto is garmin connect. the big one is the fit file. on the calculation, i think only the 1-2 meter hills are smoothed out. so i'd say it's ok. if i run straight uphill and then downhill. or hike uphill. the ascent gain looks really good. (for note, the 7m more in descent are correct.)
I had the problem before, that is was not as much as the difference of elevation. (for example start at 500m, peak at 100m. elevation gain around 480m).

is the recording in mountainbiking also smoothed? or only the calculation?

i don't know if it's true, but i heard that on early firmware versions, people had complained that the elevation gain was too much, so garmin started smoothing it.

HI Mistamb, I made some test importing .fit file into GPSSee and Basecamp and yes, could be that the problem stay in the calculation. I will report here the analysis soon.