What about Gradient Lag?

New FW from Wahoo;

hope that will see something similar from Garmin also

• Updated: Improved GRADE data response

You garmin screen is not visible in the video, how can we notice the lag or the lack of it?

I assume the synced data track he used for the overlay matched what he was seeing on the screen.

I don't know what tool you are using, but I think the shown gradient in the video is directly from the recorded altitudes, I don't think the gradient is recorded to the FIT file. But it's a while since I was looking at such file, I can remember it wrong. But if gradient in the video is dynamically from the altitudes it's not the same as that is shown on the 1040. 1040 is smoothing it and it's a small lag relative the (shown) altitude. Which I think it's good, I like the smooth gradient rather than have it flip up and down.

I think his question is did the displayed gradient on device match what you were riding in real time or was it delayed 20 seconds as people are complaining about here and synced correctly when matching to the video after the ride is finished. At least that is my question watching the video. If my device was anywhere close to as responsive as the video shows I wouldn't be in this thread.

Sorry for the mess, but I finally figured out how to insert a picture directly, so I post this again

Last autumn I was doing some testing when there was this big lag, I will do the same again later on with the new version.
It's showing altitude lag, the gradient lag was almost doubled to that. I was running the same short tour with 800, Fenix7 and 1040. The dotted line ("Alt") is not exact it's an estimate of the real altitude, and I found out afterward that the real altitude should be some second/seconds earlier than in the diagram, so the shown lag of altitude is even bigger than it's shown.

Now I have tested 1040, Fenix7 and 800 at the same place as last autumn (but a shorter tour). 1040 with 18.23 and Fenix7 with 14.36.
As I wrote, the dotted line ("Alt") is my estimated real altitudes, it doesn't show small changes in altitude, but start/end of ascend/descend is where it should be. I just turn around at 2.

800 is rather primitive but I have it as a reference.
In the test last autumn 800 and Fenix7 was almost same with start and end of asc/desc. 1040 had a lag of ~10 secs for altitude and additional ~10 secs for gradient. Now they are all almost the same, and the gradient now seems to be calculated along the altitude, not after that is finished with all it's calculating.

It's a very short tour, the top of the height are only some meters, the same with the bottom of the hollow(?) .
Altitudes are in meter.

If this video has been synced to the recorded track, it has nothing to do with the gradient shown while riding. The gradient shown while riding is a value that is computed in real time and not saved to the track. What you get from applications like strava and garmin connect is a value that is calculated afterwards from the elevation data.