While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations:
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Bazzite Linux gets a spring cleaning update to end 2025
- Valve reveal the most popular Steam games of 2025
- Native Linux support for Hytale will be launched as "experimental"
- Steam survey for December 2025 shows Linux holding to 3.19% [updated]
- D7VK v1.1 is out with experimental Direct3D 6 support via Vulkan for Windows games on Linux
- > See more over 30 days here
- Will you buy the new Steam Machine?
- Jarmer - Welcome back to the GamingOnLinux Forum
- on_en_a_gros - 2026 Gaming Goals...?
- Klaas - Will you buy the new Steam Frame?
- Klaas - Introduce Yourself!
- Mustache Gamer - See more posts
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
View PC info
View PC info
Fedora 39 didn't have this specific issue for some odd reason, only started happening on Fedora 40 for me.
I did test games with mesa-git via flatpak, but I assume that I need the 24.1 mesa driver actually on the whole system to fix this issue which is most likely caused by implicit sync. Guess I'll have to wait who knows for how long as I couldn't find an article for when the 24.1 driver will be in the fedora repos!
My frame pacing issues were permanent as long as vsync was off, even with smooth frame time graphs. So this is resolved now when using explicit sync in KDE Plasma 6.1 Beta with appropriate Mesa version :smile:
Yes, and please remember your compositor also needs to support explicit sync.
Last edited by ridge on 8 Jun 2024 at 5:11 am UTC
I did manage to run mesa-git on KDE 6.0.5 and the issue still happened. I did hear on reddit that fedora backported the explicit-sync functionality but I'm not exactly sure whether they did. I'll wait for KDE 6.1 and then run mesa-git and see if it's still an issue for me.
I did that on a different machine for a friend, and it worked wonders.
... Actually as a matter of fact I *am* going to do that. Should be able to boot within, I don't know, 30 minutes?
Don't think it's a HW issue as using Vsync fixes the problem.
View PC info
Last edited by Shmerl on 11 Jun 2024 at 4:09 am UTC
It's just that I know that on Fedora 39 // KDE 5.27 I didn't have this issue of occasional stutter so I'm just boggled about it.
Maybe it *was* stuttering and simply had a placebo because I didn't have THAT great hardware then. I have a 7900XTX now and generally do expect to have constant FPS w/ 1080p@75Hz.
View PC info
There was some related amdgpu bug about it. One way to avoid that was to tell GPU to run in higher performance mode when you play such game (there are some perf profiles for that).
Last edited by Shmerl on 11 Jun 2024 at 3:49 pm UTC
View PC info
Oh well, just gotta accept it until I get a VRR monitor.
View PC info
See https://bugs.winehq.org/show_bug.cgi?id=56002 and related.