We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sounds like a job for the Present extension / DRI3K.
On the client side, I believe the compositing window manager is responsible for this, and in the case of ClientRendering it should be pretty easy:
See also: Adding synchronization to the WM spec (wm-spec-list)
The text was updated successfully, but these errors were encountered:
See also #387, #981
Sorry, something went wrong.
See #1754.
We should already have mostly tear free frames thanks to the "flush" screen update flag.
#3560 is related to this.
No branches or pull requests
Sounds like a job for the Present extension / DRI3K.
On the client side, I believe the compositing window manager is responsible for this, and in the case of ClientRendering it should be pretty easy:
See also: Adding synchronization to the WM spec (wm-spec-list)
The text was updated successfully, but these errors were encountered: