Altimetro still not working

I am sorry you are having an issue. However, reviewing your graphs, your altimeter is working but I do not know what your elevation will be when you use your Elevation Correction feature on your Garmin Connect web account for each activity you have synced. What a non-working Altimeter will look like on the Elevation Graph is no value or extremely high or low altitude. Often the altitude will be +/- tens of thousands.

You mentioned manually calibrating your barometric altimeter. Since you calibrated prior to your outdoor Track Runs, your elevation should be within +/- 50 feet for each activity.

Please go to www.garminconnect.com, sign-in to your Garmin Connect account. Go to the far left Tool Pane and Select Activities.

- When you pull up each of your Track Runs, what is your exact elevation that shows using the "Elevation Correction" feature seen on the far right side of the activity?

By researching what the real elevation is vs. what your barometric altimeter is providing you, should make it clear if there is a legitimate altimeter failure. Also, keep in mind your elevation is not going to be perfect. Your barometric altimeter will fluctuate with coming and going pressure but your overall average will usually be within +/- 50 feet as long as you continue to calibrate your altimeter prior to every outdoor activity.

Hi Chris,

Thanx for the answer

Just done what you suggested about elevation correction ... 

I know exactly what Is the altimetry of my Activity because Is Always the same Road ... If u see the graphs the Activity Is on the same track ...

Whit the altitude correction on the web site the Activity passed from 250 m of d+ (incorrect) to the real One of 40 ... 

Sometimes i run on ultra Trail event and the altitude Is important to know ... 

Now i have the altitude correction activate on the web site ... I wonder what happen during the Activity on the device ... 

Just for more informations i've the same issues reported in this thread

 https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/fenix-6-series/226128/ascent-wrong-since-software-9-0#pifragment-1292=9

Exactly the same ... Spikes of altimetry that increase the Ascend quote ... 

Please note, your Elevation Correction on your Connect web account will only correct that one specific activity using the map elevation to be 100% accurate. It will not impact your watch. I see what you are describing now. It is the sharp spikes abnormally increasing or decreasing the accuracy of your ascent and descents for the track you are running.

My sincere apologies your replacement Instinct altimeter is giving you the spikes in your readings. You are correct that it is an issue with your altimeter for the behavior to be taking place.

The same for me.

Starting from version 17.50 I started to record height differences greater than 50% compared to real values. Elevation profiles appeared jagged instead of smooth as in previous versions. I contacted Garmin support (Italy) who initially said they fixed it with version 18.10. I have been using the watch for a few weeks but even with version 18.10 the problems have not been solved. I then contacted support again who replaced the watch under warranty.
Initially it worked correctly: the calculated elevation was approximately correct and the elevation profile smoothed like previous v.17. Subsequently the new watch updated from factory v.11 to v18.10 (unfortunately I didn't disable the update as suggested on the forums) and the issue is back exactly as before.

Garmin is providing an update with a bug reported by hundreds of users and does not currently allow downgrades.
All of this is completely absurd. I contacted support by phone asking for a downgrade, but they replied that it is not possible to downgrade.

Please, if anyone has a "gupdate.gcd" file of a stable version (before v.17.00) write me so I can use the wearable correctly.

I bought Garmin Instinct mainly for mountaineering usage and it is frustrating not being able to count on a fundamental function such as the calculation of the altitude profile, not because the device is damaged but because the manufacturer has released an update with a bug.

Can we talk about planned obsolescence in this case? Judge for yourself