JustCauseWhyNot
JustCauseWhyNot
I'll try out your branch. Thanks for informing me about it, and putting in the work.
Running `Exec=env __GL_SARPEN_ENABLE=1 __GL_SHARPEN_VALUE=50 __GL_SHARPEN_IGNORE_FILP_GRAIN=17 MESA_VK_WSI_PRESENT_MODE=mailbox gamescope --rt -w 1970 -h 1108 -W 1440 -H 2560 -F nis --sharpness 10 -S fit -- gamemoderun /home/justcausewhynot/Games/WarThunder/launcher` with your branch launches the...
That fixed auto crashing :+1:, but I'm still noticing significant latency or what feels like it no matter the framerate.
`Exec=env __GL_SARPEN_ENABLE=1 __GL_SHARPEN_VALUE=50 __GL_SHARPEN_IGNORE_FILP_GRAIN=17 ENABLE_GAMESCOPE_WSI=1 MESA_VK_WSI_PRESENT_MODE=mailbox gamescope --rt -w 1970 -h 1108 -W 1440 -H 2560 -F nis --sharpness 10 -S fit -- gamemoderun /home/justcausewhynot/Games/WarThunder/linux64/aces`  And if I use...
> full command I used for testing: `GDK_BACKEND=wayland __GL_SYNC_TO_VBLANK=0 __GL_SHARPEN_VALUE=50 __GL_SHARPEN_IGNORE_FILP_GRAIN=17 MESA_VK_WSI_PRESENT_MODE=immediate gamescope --immediate-flips -r 120 -o 120 -f -w 1970 -h 1108 -W 1440 -H 2560 -F nis --sharpness...
No crashing, and it actually feels way better. But I still am having issues. I do thank you for all you've done to help and contribute.
I'll 100% give this a try!
On portage I've made a local ebuild of gamescope where I've set it to a live version which when built will always pull the latest commit, and in the ebuild...
If I try and build your branch it fails to compile. Here's my [build.log](https://gist.github.com/JustCauseWhyNot/5a032e7c12e9d06fe5f5791cb7d2d7d2)
I will try that out today. I don't know why github didn't show a notification for your new message.