--sw-opti is broken when used together with --benchmark
#12
Comments
|
We have started deprecation process for Will close this after |
colonelpanic8
pushed a commit
to colonelpanic8/picom
that referenced
this issue
Aug 6, 2023
colonelpanic8
pushed a commit
to colonelpanic8/picom
that referenced
this issue
Aug 6, 2023
yshui
pushed a commit
that referenced
this issue
Mar 19, 2024
small changes small changes picom upto date sync with yshui, full anim support small changes small changes rounded corner delay fix fixed open window type anim, closes #12 AUR pkg, closes #15, thanks fxzzi fix lerping on shadows, closes #4 picom upto date sync with yshui, full anim support animations added, picom upstreamed yshui/next shadow fix shadow fix randr extension randr anim fix randr_mon position fix pos fix multi monitor desktop switch fixed fix for vertical stacked monitors closes #26 revert opacity rule index on next: 5a8c61d revert opacity rule Add running section to README.md Properly animates depending on wintype animation property in config fixed window unmap crash fixes animations on destroying/unmapping windows xrender fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use these two together without any
--vsync, and with a low--refresh-ratecan cause screen to be updated more frequent than the refresh-rate.In
swopti_handle_timeout, the timeout calculation is flawed. It can't handle the case when it's called with little time in between. BecauseSWOPTI_TOLERANCEmakes it think those two calls are in the same refresh slot.The text was updated successfully, but these errors were encountered: