I have had issues with the elevation readings all summer long. I consistently am missing at least 50%(and usually more) of my total elevation gain while cycling or mountain biking. I usually end up enabling the Elevation Correction. I have been in contact with support. On the first call, they told me to upgrade to the beta software and clean the sensor. I did both, and it still read erroneously. On the next call, I was instructed to default it back to factory settings and try again. After doing this, repairing all my sensors, etc, the elevation gain was still off by at least 50%. On the next call, they agreed to replace it under warranty. I recieved the new device, set it up, and it is doing the EXACT SAME THING. I now believe there is a software bug with 9.20. Does anyone else experience this? I can't believe I am the only one who has this issue, on 2 completely separate devices. Anyone from Garmin Support on here that can address this? This is a 600 dollar device and I believe it should work correctly. I hate having to use the USGS tables for elevation as they are highly inaccurate when mountain biking.
I had same problem on 9.2. 9.73 has stopped the smoothing but gave me double the correct elevation for my 10km commute yesterday so it's still not right. I agree that it's massively annoying for cycling to have the wrong elevation on such an expensive device. Worked okay on firmware 8 so if it's important you may be able to look up how to downgrade back to that until it's properly fixed.
I’m experiencing exactly the same thing with my Fenix 5 on firmware 9.20 (did a hilly sportive yesterday over 2,000M of climbing and my watch showed 1302M) and when I tried to download 9.73 it just didn’t seem to recognise it, so it remains on 9.20. I’ve messaged Garmin support but no response. The watch is only 6 weeks old so I’m considering just returning for a refund. Pity - it looks good.. Interested to see what people say about 10.51, but it appears to me that even the beta versions have undergone minimal testing before being released.
FWIW I am new to the F5s having lost my VA3 in a lake last week. The VA3 has the same problems tracking elevation long term, with strong smoothing and a general negative slope on the data. This is one reason I came to the F5 line, it drove me nuts. I am happy to report the beta 10.51 tracks very well. I took a 3.5 mile hike in and out of a gorge or two, which totals 70 floors with a lot of stop and go with the dog. Hill top off by 10 feet, gorge bottom by 12 feet, return at car, 11 feet. I would have been happy with 100 feet! I didn't even use the GPS since I wanted to try the other mode. The VA3 would have been off by more than 200 feet by the end. Hopefully this will go to VA3 users also.
Yes quite, however unless I'm mistaken Alpha testing comes first by the test teams at the development site after the acceptance testing and before releasing the software for beta test?
FWIW I am new to the F5s having lost my VA3 in a lake last week. The VA3 has the same problems tracking elevation long term, with strong smoothing and a general negative slope on the data. This is one reason I came to the F5 line, it drove me nuts. I am happy to report the beta 10.51 tracks very well. I took a 3.5 mile hike in and out of a gorge or two, which totals 70 floors with a lot of stop and go with the dog. Hill top off by 10 feet, gorge bottom by 12 feet, return at car, 11 feet. I would have been happy with 100 feet! I didn't even use the GPS since I wanted to try the other mode. The VA3 would have been off by more than 200 feet by the end. Hopefully this will go to VA3 users also.
That's encouraging - 9.20 was driving me nuts too. I've just loaded up beta 10.51 and hopefully will experience the same success.
Update: After downloading the latest beta(10.51) I tested it this afternoon. My elevation gain was within 50 feet of the USGS tables. So far it is promising. The real test will come when I go mountain biking next.
