Altimeter is wrong on fast decent

From time to time my watch also does not accept calibration input being necessary a soft reset.
Unfortunately I have to calibrate it frequently in oppose to my cheap weather station the is always right...

From time to time my watch also does not accept calibration input being necessary a soft reset.
Unfortunately I have to calibrate it frequently in oppose to my cheap weather station the is always right...

This is another thing... your weather station hasn't altimeter mode... you set it for known altitude and it stays so... also if you set your Fenix 5X on "barometer mode" and you leave it at the same altitude you don't have to calibrate it... Fenix 5X leaved on auto mode has to decide if pressure change is due to an altimeter variation or atmospheric pressure change.

I understand but once Garmin sells this called "auto mode" IMHO it should work, otherwise take off... Why getting beat for that?
Just to be clear I'm a Garmin customer since GPS II Plus plus and I love my Fenix5 and I still have a completely functional F1. I'm just saying that they don´t need those functions that everybody knows doesn't work nether those annoying bugs that are never fixed.

, the only fix is to roll back to 6.83b.

Thanks for the reminder of which sw ver that handled elevation best. Now downgraded and I'm almost always run with both my v800 and 5x and then merge in data from v800 if those are better. This was the first time this year I used the elevation data from 5x.

Someone could try new 9.20 beta? Now i'm on 6.83 and if also this beta doesn't solve this bug i'll stay with 6.83.

Ok, i have just tested by myself, the bug is still here also with 9.20!

Thanks for testing it out.
hope they address this on next fw. release!

Thanks, then I stay with 6.83 for my hill repeats today.

Hello,
I have experienced the same problem with the Chronos, Fenix and VA3.

I got my Chronos end of 2016, but when Garmin changed from FW10.X to 11 the altimeter became slow and for my usual tracks, which go up and down quite frequently, total ascent displayed by the Chronos was far too low (the profiles looked smoothend... and quick descents/ascents were just not visible in the graph).
As Garmin was not able to solve this issue, I returned my Chonos and bought a Garmin VA3. The watch worked well, altimeter reading and total ascent figures were correct and comparable to the Chronos with FW versions 10.x and before.
Unfortunately Garmin changed now the Firmware of the VA3 to version 5.0, which shows now the same altimeter problems - at least in cycling mode.
This is the video of the altimeter reading I made yesterday: https://www.youtube.com/watch?v=IArAxYXg3Q4&feature=youtu.be

I have posted also the report with some altimeter graphs on the VA3 subforum:
https://forums.garmin.com/forum/into-sports/health-fitness/vivoactive-3-aa/1362527-vivoactive-3-altitude-reading-is-slow-fw5

Today I bought myself a Garmin Fenix 5, installed FW 7.5beta, and switched auto updates off. Jsut made a short bike ride, just 1.5h, but so far, everything was fine.