What about Gradient Lag?

Which beta? I had this exact problem with .12. I did one ride yesterday with .13 and the lag was not there. 

I'm not sure if we are describing the some issue. I understand that with climb pro, the gradient calculation is irrelevant, what matters is the data that comes with the preloaded route. I think what you describe in the video, it could be simply a route with bad data or a problem with the GPS accuracy. Did his exact route work fine in previous versions?

Regarding the gradient lag, it's still there with 14.13. I have my Garmin 1040 set up to record data every second, and the delay is well over 15 seconds. It's useful for long steady climbs, but impractical to know the gradient of a particular short segment.

Yea, the gradient lag per se is still there. But in .12 there was a significant dissonance between real life and what is showin in preloaded data. With recent beta I did not have the same problem. More rides ahead of me this week to conclude this 

That would be interesting to confirm. I'm quite happy with my 1040 as it is except for the gradient field.

Route was created in GC , and I have been pretty keen to put route point each 100 m or even less

gradient lag it has nothing to do with climb pro delay

I have every second recored , segment was 27 km long ,but climb pro has split in diff small segments

so if I don't know where the climbs finish (I ride this course before), Garmin was unusable , I would say rubbish 

I was defending Garmin, but not anymore

Again, which beta?

I can understand your frustration. It's an expensive device. Let's see if Garmin can fix these bugs for the next release.

today with new beta 14.13

-navigation, useless

Rubishh

pin point to a location then navigate , route calculation error

-I was zoom in 100 times because my garmin was zoom out the course over and over and over and over and over again

Rubbish 

photos.app.goo.gl/e8nyVeE61n1kBxJm6

14.12

I was riding in the mountains yesterday, 2500 m elevation gain