Open GabMus opened 4 months ago
Replying to https://github.com/ValveSoftware/gamescope/issues/1279#issue-2268136774
does setting the nested refresh rate to something higher help at all (ex: using -r 1000 -o 1000
)
if you're unsure if it helps, try running w/ vulkan immediate (aka tearing) present mode:
MESA_VK_WSI_PRESENT_MODE=immediate gamescope -r 1000 -o 1000 ...
Unfortunately neither helps, still have the exact same issue
I was completely unable to replicate this issue with xonotic, still running at 4k, capped or uncapped framerate, using regular opengl or zink for rendering
Sorry if I keep adding comments, I'm doing some testing real time
So far the common thread seems to be Proton
Replying to https://github.com/ValveSoftware/gamescope/issues/1279#issuecomment-2088175380
What version of gamescope are you running? If it is 3.14.3, see if you have the issue on 3.14.2
also, after that, try installing gamescope-git and see if you also have this issue on the latest commit
Problem is definitely still present on gamescope-git
, but it seems to be gone with gamescope 3.14.2-1
.
The only problem is that this particular version doesn't seem to have HDR working for me, defeating the entire purpose of using gamescope for my particular usecase
Problem is definitely still present on
gamescope-git
, but it seems to be gone with gamescope3.14.2-1
.The only problem is that this particular version doesn't seem to have HDR working for me, defeating the entire purpose of using gamescope for my particular usecase
I'm not 100% sure, but I think that my custom 'version' that sits between version 3.14.2 and 3.14.3 might allow HDR to work for you: https://github.com/sharkautarch/gamescope/releases/tag/3.14.21
I'm sorry, but with the recent xz drama still fresh and given that you don't seem to have any apparent relation with the gamescope project I'm hesitant to install a package of which the source doesn't come directly from the original author, in this case Valve.
I'm sorry, but with the recent xz drama still fresh and given that you don't seem to have any apparent relation with the gamescope project I'm hesitant to install a package of which the source doesn't come directly from the original author, in this case Valve.
no worries, I often feel the same way with other stuff too
Since my 3.14.21 ‘version’ actually just targets a specific commit point in the ValveSoftware repo, you can simply clone the official ValveSoftware/gamescope repo, and do a git checkout 14a1db3
to get the exact same result
(For reference, if you look at that commit: https://github.com/ValveSoftware/gamescope/commit/14a1db3a57612e5cfbba6d4c19688eafdc6c4043 and then click on ‘browse files’ and then click the commit history button (icon kinda looks like a clock going in reverse (counter clockwise)) you’ll see that this commit is just slightly ahead of the official 3.14.2 release)
Just checked 14a1db3: HDR doesn't work but the bug isn't present
Just checked 14a1db3: HDR doesn't work but the bug isn't present
welp, I'll let you know if I find another commit point where HDR might work for you :/
As the title says, I experience "stutters" that can best be described as temporary complete freezes, only while moving the mouse, even in the game menu.
This only happens when the mouse moving is set to 4000hz polling rate; if I disconnect the same mouse's dongle and use it with a cable instead (switching to 1000hz), the problem disappears.