"Allow tearing in fullscreen windows" makes every game feel extremely choppy.

Contrary to how I've used this setting before on other distros, on bazzite it seems to make every game feel horribly choppy despite FPS remaining the same. I'm on all AMD hardware, using Bazzite 42 KDE (The non-steam-gaming-mode version)
20 Replies
Xenia Meraki
Xenia Meraki2mo ago
Most likely it's not that option causing the choppiness. I use that option just fine.
Xenia Meraki
Xenia Meraki2mo ago
No description
SX̌N
SX̌NOP2mo ago
Well I say that because disabling it seems to fix the choppiness, while introducing more input lag Which obviously I'd prefer it to work as intended Admittedly I dont truly know the root cause, only what happens with it enabled/disabled It may also be a VRR issue, uncapping my FPS seems to fix it(?) but I'd prefer using VRR as well
Xenia Meraki
Xenia Meraki2mo ago
https://wiki.archlinux.org/title/Gamescope https://docs.bazzite.gg/Advanced/scopebuddy/ You can also experiment with gamescope and related options mayhap, if you have not already.
SX̌N
SX̌NOP2mo ago
I'll give it a try I wish I knew how to explain the issue better, I love bazzite but i've never had this problem on other distros
Xenia Meraki
Xenia Meraki2mo ago
What games tested so far?
SX̌N
SX̌NOP2mo ago
Deadlock, CS2, both with and without mangohud I'm gonna try a few more Oddly enough Insurgency Sandstorm seems to run fine actually, its not as bad as the others, but still noticable choppiness in motion
Xenia Meraki
Xenia Meraki2mo ago
Some weirdness with Source 2(1?) engine mayhap. And CS2 has been troublesome on linux in general. HDR could also be a problematic setting, potentially.
SX̌N
SX̌NOP2mo ago
From what I'm seeing probably it I'm not sure my display even supports HDR, is there a specific way to see if its being enabled somehow? Once shaders loaded in sandstorm, 120 fps was still WAY smoother than my 141 I use in other games Where bazzite systems are immutable, you'd think this issue would be replicable on other systems- at least ones using AMD okay so.... it just fixed itself?? im sorry i have no idea what tf happened, i think it was maybe shader issues either shader issues or vrr or both
SX̌N
SX̌NOP2mo ago
leaning towards shader issues because enabling this seemed to have it resolve itself after a moment
No description
SX̌N
SX̌NOP2mo ago
CS2 also runs as normal again So im considering this issue fixed i appreciate the pointers btw!
Xenia Meraki
Xenia Meraki2mo ago
https://discord.com/channels/1072614816579063828/1087140957096517672/1391516199828983928 fwiw official dev word is to have both pre-caching and background processing off, as Most of the time games on modern hardware compile shaders on the fly just fine.
SX̌N
SX̌NOP2mo ago
Hm, I wonder what changed then
Xenia Meraki
Xenia Meraki2mo ago
Might be a specific slowless to how CS2 was compiling tho. Curious.
SX̌N
SX̌NOP2mo ago
Well it was also Deadlock as well So youre probably not wrong about source 2 wonkiness also unrelated but DAMN does bazzite just feel smoother when its working right its some black magic
Xenia Meraki
Xenia Meraki2mo ago
:) What you're feeling is most Likely the work of the KDE devs, but they are damn good at what they do indeed.
SX̌N
SX̌NOP2mo ago
i thought i had low latency before but this is like peering through a window- i cant imagine what 200+ hz is like' my 0.1% lows are also WAY higher Plasma 5 was wonky back then but I def noticed crazy improvments with Plasma 6, even on other distros I'd say its smoother than Windows (at least in the games I play)
Xenia Meraki
Xenia Meraki2mo ago
I've been pretty happy with KDE indeed, fantastic devs and software.
SX̌N
SX̌NOP2mo ago
I wish MATE had these levels of improvement MATE + the smoothness of plasma would be godtier
Xenia Meraki
Xenia Meraki2mo ago
Can't have it all. afaik gnome and kde are the projects people contribute the most to and get the most activity.

Did you find this page helpful?