Enable tearing and explicit sync with wayland backend

[Fxzzi]

Is there an existing issue for this?

• I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

• The issue occurs on upstream gamescope without any modifications

Current Behavior

Using gamescope with minecraft and the wayland backend (wrapper command = gamescope -f -W 2560 -H 1440 -w 2560 -h 1440 --force-grab-cursor -r 170 --force-windows-fullscreen --) explicit sync and tearing do not seem to be enabled. I experience explicit sync flickers which I do not experience without gamescope, and tearing is also not active on my monitor, as checked with hyprctl monitors.

Running the game without gamescope fixes the issues however I then get cursor grab issues.

Steps To Reproduce

1. Launch game with gamescope on wayland backend
2. Make sure tearing is enabled for gamescope like so in hyprland config: windowrulev2 = immediate, class: ^(gamescope)$
3. Check tearing enabled in `hyprctl monitors and see its disabled
4. Observe explicit sync flickers which have not been present for months since Hyprland and other compositors now support it.

Hardware information

- Distro: Arch Linux
- CPU: AMD Ryzen 5 5600X 6-Core Processor
- GPU: NVIDIA Corporation GA104 [GeForce RTX 3070]
- Driver Version: 565.57.01

Software information

- Desktop environment: Hyprland latest master or 0.45.1
- Session type: wayland
- Gamescope version: gamescope version 3.15.14 (gcc 14.2.1)
- Gamescope launch command(s): `gamescope -f -W 2560 -H 1440 -w 2560 -h 1440 --force-grab-cursor -r 170  --force-windows-fullscreen --` as an example

Which gamescope backends have the issue you are reporting?

• Wayland (default for nested gamescope)
• DRM (default for embedded gamescope, i.e. gamescope-session)
• SDL
• OpenVR

Logging, screenshots, or anything else

No response

[Algorithm0]

Sorry, my answer won't help you. But can you help me? Tell us exactly how you launch a gamescope when you don't use your desktop environment?