Skip to content
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

How to prevent screen tearing / get vsync. #7

Open
xander-st-aubyn opened this issue Aug 11, 2024 · 2 comments
Open

How to prevent screen tearing / get vsync. #7

xander-st-aubyn opened this issue Aug 11, 2024 · 2 comments

Comments

@xander-st-aubyn
Copy link

In picom to get a tear free accelerated experience I have to specify a glx backend and vsync.. How can I get the same on fastcompmgr?

@tycho-kirchner
Copy link
Owner

tycho-kirchner commented Aug 11, 2024

Good question. Once I have more time (currently busy writing thesis) I am planning to use xcb to send more compositing requests in a bulk, thus reducing the time frame where tearing can occur. I suspect this will not be enough though and then I'll likely port wait_vblank from xfwm4 or another compositor to fastcompmgr. If you want to help, you could test, whether tearing is reduced on your machine when running dcompmgr from Dana Jansens, clonable via git clone git://git.openbox.org/dana/dcompmgr and report your results back. Compilation may be cumbersome, so you could also run my attached binary ./dcompmgr --no-fade.
dcompmgr.tar.gz

On this website https://www.vsynctester.com I get almost no tearing with dcompmgr, even when using no GLX backend.

@xander-st-aubyn
Copy link
Author

This was on EL9 (rocky if it matters) and I am currently in a fully setup openbox environment on FC39. I have no issues being told to go compile something if its more or less clone (./configure) make && make install. I was happy your make file included an uninstall ;)

I will do that and report back!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants