gamescope: update to 3.16.17.

[RomainLanz]

Testing the changes

• I tested the changes in this PR: YES

Local build testing

• I built this PR locally for my native architecture: x86_64 (libc)

[gmbeard]

@RomainLanz It might be worth including the following patch also. I've noticed some slight stability improvements when setting CAP_SYS_NICE on the gamescope binary manually. What do you think?

diff --git a/srcpkgs/gamescope/INSTALL b/srcpkgs/gamescope/INSTALL
new file mode 100644
index 00000000000..efac07fe86a
--- /dev/null
+++ b/srcpkgs/gamescope/INSTALL
@@ -0,0 +1,5 @@
+case "${ACTION}" in
+post)
+	setcap CAP_SYS_NICE=eip usr/bin/gamescope
+	;;
+esac

[RomainLanz]

I haven't personally encountered any stability issues running gamescope without adjusting its priority.

I see the Arch Wiki does recommend setting CAP_SYS_NICE, which could indeed bring some improvements.

However, it also comes with caveats, like Vulkan environment variables being ignored and the Steam overlay no longer working, so it might not be ideal for all setups.

• Using this command will cause some vulkan environmental variables to be ignored: for example, if you specify the GPU for Gamescope to use by setting MESA_VK_DEVICE_SELECT. See here. You can use ananicyAUR or similar to get around this limitation.
• Using this command is known to stop the Steam In-Game Overlay from working, which can be especially troublesome with games which require the use of it in order to access their multiplayer functionality.

[Johnnynator]

_wlroots_hash should be updated to the commit that is referenced by gamescope. ( 54e844748029d4874e14d0c086d50092c04c8899)

[RomainLanz]

Good catch!

I also don't see any reference to OpenVR in the current install script, even though it's bundled inside as a subproject at commit ff87f683f41fe26cc9353dd9d9d7028357fd8e1a.

I noticed the script sets -Denable_openvr_support=false. Does anyone know why it was disabled?