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!
renton82 How fast is "fast?" A recent trail run with 5x seemed to do fine. I'll see what the 5x+ does this week as I'll be descending pretty quickly from 14,000 feet
Just don't use it as your main altimeter for skydiving! Right now, the 5X Plus is totally useless for any jumping related activitiy. On the ride to altitude it is generally about 1500ft of and on the jump it is dangerously inaccurate. After opening at 2100 ft, watch showed still about 10000 ft! To rely on this (when for example using Jumpmaster) will kill you! I did 14 jumps over the weekend with varoius settings/calibrations/cleaning of sensor/resetting to factory settings -- nothing worked!
Right now, the 5X Plus is totally useless for any jumping related activitiy.
Right now any Fenix 5 / 5 Plus, D2, Forerunner 935 are totally useless for any altimeter related activities ! Hope the will fix this issue soon! As i said, report it to beta team, maybe they can do something! For now, my 5 Plus is inside its box ready to return to Amazon if the will not solve this bug soon.
I just got off the phone with Garmin and they have had many many reports of this being an issue. I urge you to call Garmin and send them your data as I was told this will help them with the issue. As for a timeline, no such luck. Until then, our watches aren't overly useful.
I just got off the phone with Garmin and they have had many many reports of this being an issue. I urge you to call Garmin and send them your data as I was told this will help them with the issue. As for a timeline, no such luck. Until then, our watches aren't overly useful.
I have reported all my data to beta team many times I also tell them until which fe version of 5X works fine (6.83b). I think it's not so hard to compare 2 fw version and find what's different between the 2!
I own a Fenix5. I try to downgrade to 6.0 later today.
6.83 is the latest fw that works fine for altimeter for Fenix 5 and Fenix 5 X(obviously, you have to downgrade to 6 before, than update to 6.83). Unfortunately with Fenix 5 Plus you can't downgrade to any versions because ALL versions are bugged!
Two things i noticed on my Fenix 5 plus (firmware: 3.53) today:
1.) While driving a hilly road today in a car, i did manually recalibrate the watch several times during flat road sections. I then compared the altitude of the watch with the one shown on my on-board navigation system. The strange thing was, that after each calibration, the just entered altitude value on my watch was frozen for 30...60 seconds before it jumped in 2 to 4 measurements to the same altitude that my car navigation system displayed. I sometimes noticed a similar behaviour when i scroll to the altitude widget (green diagram). It takes some seconds before the value reaches the correct value. Looks as if there is a filter-function which starts from old/previous values?
2.) When restarting the watch, the previously calibrated altitude gets lost and the watch shows a wrong altitude. :confused:
