You are not logged in.
Were the games affected by "__GL_SYNC_TO_VBLANK=0"?
Offline
Were the games affected by "__GL_SYNC_TO_VBLANK=0"?
Doesn't seem like it. If I start Lutris and give the env variable to the game, or go on steam and put __GL_SYNC_TO_VBLANK=0 %command% in launch option, freezes still happen.
Offline
As for software, I use awesomewm and picom as my window manager/compositor.
Is it also a problem if you kill picom?
Offline
As for software, I use awesomewm and picom as my window manager/compositor.
Is it also a problem if you kill picom?
Nope, the stutters seem to disappear after I kill picom as well. Though, I'm getting screen tearing, as expected.
Offline
I'm getting screen tearing, as expected.
That's not "expected".
Are you still running w/ "__GL_SYNC_TO_VBLANK=0" ?
Offline
I'm getting screen tearing, as expected.
That's not "expected".
Are you still running w/ "__GL_SYNC_TO_VBLANK=0" ?
I've tested in on Minecraft (running via PolyMC with the env setting), firefox (via __GL_SYNC_TO_VBLANK=0 firefox), and Satisfactory (Steam proton title, with __GL_SYNC_TO_VBLANK=0 %command% launch option) and in all 3 cases I am getting screen tearing. I've tried exporting the setting as well, and it's the same result.
Offline
The plan was to try steam w/o picom and also w/o downforcing vblank via "__GL_SYNC_TO_VBLANK=0"
Tearing isn't overly surprising when you export that to the game.
Offline
The plan was to try steam w/o picom and also w/o downforcing vblank via "__GL_SYNC_TO_VBLANK=0"
Tearing isn't overly surprising when you export that to the game.
Restarted my PC, cleared the launch options so it no longer forces __GL_SYNC_TO_VBLANK=0 to the game and screen tearing still happens. Still the same thing with firefox and Minecraft too.
When I turn picom on momentarily, the screen tearing is gone.
Last edited by Miuzore (2022-10-19 13:14:10)
Offline
Can you configure VSYNC in the game?
Offline
Can you configure VSYNC in the game?
Yes. I have a 60 hz monitor, and I've tried vsync with various FPS cap settings (unlimited - 120 - 60) and without vsync, but tearing still happened no matter what.
Offline
Try w/o picom but "__GL_SYNC_TO_VBLANK=1" (fps caps are not the same as vblank alignment)
Ftr:
I have a 60 hz monitor
That means "one"?
Offline
Try w/o picom but "__GL_SYNC_TO_VBLANK=1" (fps caps are not the same as vblank alignment)
Screen tearing still happens, tried with vsync and without.
Ftr:
I have a 60 hz monitor
That means "one"?
Yup.
Offline
Try the game w/o vulkan "PROTON_USE_WINED3D=1 __GL_SYNC_TO_VBLANK=1"
Offline
Try the game w/o vulkan "PROTON_USE_WINED3D=1 __GL_SYNC_TO_VBLANK=1"
Tried, basically unplayable. Screen tearing still does happen though.
I don't think it's a Vulkan-specific issue, as I am getting screen tearing literally everywhere - Firefox on videos, when scrolling through a page (happens on steam too), and of course, in games, be it native (Minecraft for instance) or non-native (Satisfactory).
Offline
Okay, I'm going to mark this as solved. I have been using an autostart command at the start to run "picom --experimental-backends", since it's what I started to use like a year ago, and I didn't have any issues with it. Changing it to just regular "picom" command solved it, and I think the triple buffer option mentioned earlier in the thread did help things too. I don't have a large sample size, as I've been using my PC for like few hours, but I haven't experienced any stutters since.
Offline