I have the same problem with the Forerunner 645. Is there already a solution for this problem? Will there be an update from Garmin??
scotthunter2 I don't have a 645. Does it have the option to set the barometer mode to "auto", "altimeter", or "barometer"?
This would make sense. I don't understand why Garmin would take away the mode selection and effectively render the altimeter useless in most situations. I know they omitted a few features from the Fenix line so that people would not buy the cheaper 645 for hiking and stuff, but in doing so they have crippled an important part of the watch's function.
I wish Garmin could wake up and read this - this is not the first time this issue has been raised yet they seem more focused on updating the music player.
As I've said before, the 645 is actually remarkably good as a navigation aid for hiking. The orienteering capability of the watch isn't talked about much as most people who buy this watch are runners only. It's just a shame that the dodgy altimeter lets it down.
I bought this watch instead of the 245M because of the barometric elevation. My wife and I just hiked in Maine and the reported elevation from my watch was over 500 feet more than the stated elevation for the mountain we climbed. I'm OK with 20 or 30 feet, but 500? The weather was stable all day so I can't see where that had any effect.
Last week I went skiing in the Alps, at the altitude of 2600m my forerunner 645 indicated that we were at 3325m. That's a difference of more than 700m!! The weather was stable and the altimeter was calibrated in the morning. I can understand that there may be a slight difference, but this is really too much and completely unreliable. This wouldn't be allowed for this money?! When does Garmin come with a proper solution/update? Or any tips?