Ascent during an activity

I think you should read this:
https://forums.garmin.com/forum/on-t...on-fast-decent

It is about descent but watch is using barometric pressure in the same way during ascent.

I think you should read this:
https://forums.garmin.com/forum/on-t...on-fast-decent

It is about descent but watch is using barometric pressure in the same way during ascent.

Of course it's because this! I think if this bug will not resolved in next release, I'll sell this piece of s**t cause it's useless for my needs! I have reported so many times to beta team that I have lost hopes they will fix this. The only workaround is to roll back to 6.83 or below fw version.

slight crosspost from reddit

I have had the 5x for about a month and it's worked well up until about 3 mtb rides ago.

It is vastly underreporting ascent, for example I ride a trail today that I know has 1200+ elevation and the Garmin only recorded 200ft. Other trails I normally do are the same.

I have altimeter set to auto calibrate but have also tried setting the value based on an iPhone app I have

Is my watch broken or is there some setting I need to check?

At the least is there an option to just use GPS altitude data for my rides and skip the watch like I had on my Garmin 620?

edit: forgot to add, I'm on the latest beta firmware, 9.2

The update process erases existing data on the watch, including elevation and the satellite almanac.

This can make the acquiring your location and autocalibrating the barometric altimeter at the start of your next activity a much slower process.

Since you have now done an 18 mile TT, you should have a new almanac (takes about 12.5 minutes to download over the GPS signal). Subsequent GPS acquisition and altimeter autocalibration should occur faster.

The update process erases existing data on the watch, including elevation and the satellite almanac.

This can make the acquiring your location and autocalibrating the barometric altimeter at the start of your next activity a much slower process.

Since you have now done an 18 mile TT, you should have a new almanac (takes about 12.5 minutes to download over the GPS signal). Subsequent GPS acquisition and altimeter autocalibration should occur faster.

Well, this makes sense. Great post. I'll acquire a signal on GPS while I am getting ready and see if this helps. I assume also with more and more activities it should become more accurate.

The update process erases existing data on the watch, including elevation and the satellite almanac.

This can make the acquiring your location and autocalibrating the barometric altimeter at the start of your next activity a much slower process.

Since you have now done an 18 mile TT, you should have a new almanac (takes about 12.5 minutes to download over the GPS signal). Subsequent GPS acquisition and altimeter autocalibration should occur faster.

While that may or may not be true it did not help in my case. I've now gone on 3 additional rides and each are still way off on elevation. It is still vastly underreporting. I've tried reseting the watch to defaults and still have the same issue.

Same here, vastly under reporting elevation gains every singe time. usually reporting about 1/3rd of the actual elevation. Oddly, elevation descent is mostly fairly accurate every time.

I wish there was a connect setting to turn on elevation correction by default and before connect sends to strava as it gets annoying having to login and correct for every activity on both sites.