Here we go again! Today while i'm coming at home from the sea, i tried for the first time navigation and voilà: altimeter was totally wrong! When i was near my home that is about 110m asl, altimeter reported 75m! I tried to calibrate it but when i set correct altitude, it started to count slowly to calibrated altitude like my Fenix 5X did; altimeter was set on continous calibration. More info here: https://forums.garmin.com/forum/on-t...on-fast-decent ! I can't believe it! Luckily this time i bought it on Amazon, so if things don't change quickly, i'll return it and i'll stay with my Spartan Ultra that never had this bug!
Are you looking at the widget or the activity after you’ve stopped? Cause I’ve always have had a delay with the widget telling me my current alt. I just chalk that up to the watch needing time to read then graph the current alt. Are you expecting the widget to be real time?
That run starts and stops at roughly the same altitude. The graph shows that. So i'm asking "what is fast?"
Are we talking motorcycle? Mountain Bike? Road bike? Airplane?
I'm just pointing out that it *seems* to work for my use. I doubt I'm the only one. I'm just trying to understand your use when you say "it doesn't work"
I experienced this yesterday as well while running stairs. The stairs are a known 25m per lap and my watch would often count 0m or 7m and I have no idea why. I returned my 5 because it started acting like this as well. You can see the elevation plot in my run is wonky as well.
This is exactly what I mean! It's not an hardware issue, it's software! With Fenix 5 X you could roll back to 6.xx firmware, but here, the firmware was born bugged and there's nothing you can do! Please report it to beta team as I'm doing for Fenix 5 X and now for Fenix 5 Plus! Maybe they fix this issue soon! Now I have extended my return window with Amazon and bought a Suunto 9 (that works flawlessly with altimeter), if they don't fix this bug until my return window, I think I'll return it! The crazy thing is that this bug is widespread, if you look at links I posted in first page of this thread, you can see that this bug affected D2 line, Fenix 5 lines, Forerunner 935 line and obviously Fenix 5 Plus line!
