That's the whole point of NV_present_video, if gives you that expected time of the next frame. The Vulkan equivalent is VK_GOOGLE_display_timing.AnyOldName3 wrote: ↑28 Nov 2018, 13:45We do fixed timestep with interpolation for the physics, but that's not something applicable here - you need to know which two things to interpolate between, which involves knowing the expected time that the next frame will be displayed, which is the whole problem in the first place with that type of stutter.
If we take a running average of frametimes, that would help reduce the impact of one frame taking an unexpectedly long time, but would also mean that one frame affected even more frames than it does now. Overall, it might be good and it might be bad.
https://www.khronos.org/registry/OpenGL ... _video.txt
So for people have the supported extension in their hardware and software stack, we can then solve this particular issue.It also allows an application to request when images should be displayed, and to obtain feedback on exactly when images are actually first displayed.