What about Gradient Lag?

Try installing the Connect IQ APP: Elevation Grade
It can be faster because it adjusts how it is calculated

Tried this app on the 1030 plus, as far as I could see it made no difference at all, just a slow as the built in Garmin function?

@ looigi,

“FWIW: As a possible workaround, there are a couple of IQ gradient fields that I've used on other Edge units that work significantly better than the native gradient field.  IDK about using them on the 1040, but it might be worth a look.  One is Sensible Grade but I don't think it's compatible with the 1040 yet.”

Thanks for this suggestion. Have you used Sensible Grade on a 1030 Plus? I wonder if it can take the lag-plagued, gradient data from a 1030 Plus and spit out a ‘more acceptable’ 2-3 second delay display instead?

mcinner1 - What exactly are you saying here? I have just done a climb with the Data-Field still up, the Elevation Screen and ClimbPro was on. All 3 were showing exactly the same Gradient and Elevation all the way up.

Are you saying that ClimbPro takes precedent of the 1040 Gradient display and it supplies the Data-Field. I have to say the Gradient Data-Field did look more valid on the climb, not afterwards obviously. (This may have been wishful thinking, I only did the climb once.)

I created the Course with Komoot and the .gpx has the Elevation:

     <trkpt lat="46.954343" lon="7.082424">
        <ele>559.199008</ele>
        <time>2022-07-01T10:18:43.365Z</time>
      </trkpt>

Is it possible that the 1040 ClimbPro uses this to calculate Gradient and subsequently feeds it into the Data-Field during a climb? 

MikeF-Swiss said:

mcinner1 - What exactly are you saying here?

The gradient datafield works using the change of the measured barometric pressure as a function of distance, measured by speed sensor or GPS. it has nothing to do with Climb Pro and works even without a course loaded.

Climb Pro uses only the elevation profile of the loaded course as a function of the GPS measured position on the course. It only works with a loaded course and has nothing to do with the gradient datafield.

ClimbPro does report the average grade remaining on a climb, which comes from the course data, but this does not affected the grade data field whose value comes from using the barometric sensor and speed data input.

So my original statement is correct:

However, I use the ClimbPro and Elevation screens so I am still subjected to this crap.

Crap being the Garmin Gradient display, which is worse than useless.

But, ok if you see what Gradient is still to come on ClimbPro, that’s helpful.

The climbing pro graphic is as useless as the gradient.  You’re half way up a hill before it even registers.  What’s the point of implementing duff functionality if you then don’t try and fix it and defend it by saying “it’s normal”.

Ripp off

Power Guide is also connected with gradient lag. 
I posted few days ago about it. 
During ride regarding Power Guide the climb is over but I still ascending   
For the device for this price it should works better