-
-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve frame timing (a.k.a. reduce input lag) #147
Labels
Comments
I'm still using ver 5.1 and frequently checking for new compatible versions to upgrade. |
this seems like a pretty interesting issue, any recommended reading to start to figure this out? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, compton doesn't really pay any kind of attention to frame timing. A frame is rendered whenever the main loop is free (i.e. not events received in a round of the main loop) and there is damage.
It's amazing this worked so well as it did (because there are so many ways this could break). But, there are increasing number of reports of input lags when vsync is enabled. Most notably, window lags behind the mouse cursor when it's dragged around.
A lag of one frame is unavoidable when vsync is enabled, because the screen update has to sync with vblank, so it cannot update as soon as the mouse moves. However, the current input lag of compton seems to be far higher than one frame.
We might be able to resolve this problem by carefully scheduling frames.
The text was updated successfully, but these errors were encountered: