Fsr upscaling causes weird grid-pattern artifacting with --force-grab-cursor

[ZKletsplays]

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

My screen has a resolution of 16:10, 2560x1600. I'm trying to use fsr upscaling to upscale from 1280x800 to my screen's native resolution. However, as soon as I launch any game, the screen always displays a really weird grid-pattern artifacting, like some parts of the screen are rendered lower/higher. This happens when using --force-grab-cursor with the fsr upscaling, and I assume has something to do with the cursor.

This also happens without --force-grab-cursor, but only when you reach a state in the game where the cursor is hidden. For instance, it will be fine in the main menu, but it will artifact when you are actually in game, and is fine when you enter an interface which makes your cursor appear (like an inventory or pause menu etc...).

Steps To Reproduce

1. Launch any game from steam with the launch command: "gamescope -w 1280 -h 800 -W 2560 -H 1600 -F fsr -f --force-grab-cursor -- %command%"

Hardware information

- Distro: Archlinux
- CPU: AMD Ryzen 7 6800H
- GPU: AMD Radeon RX 6650M [Discrete]
- Driver Version: Mesa 24.3.2-arch1.1
- Display (BOE0AC1): 2560x1600 @ 120 Hz (as 1706x1066) in 16" ]

Software information

- Desktop environment: KDE Plasma 6.2.4
- Session type: Wayland
- Gamescope version: 3.15.15
- Gamescope launch command(s): gamescope -w 1280 -h 800 -W 2560 -H 1600 -F fsr -f --force-grab-cursor -- %command%

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

[matte-schwartz]

is this an internal laptop panel or external panel?

[ZKletsplays]

This is an internal laptop panel

[matte-schwartz]

Does disabling PSR with amdgpu.dcdebugmask=0x10 in your kernel commandline change anything? Wondering if it's a similar issue as noted here: https://gitlab.freedesktop.org/drm/amd/-/issues/3388#note_2705971

[ZKletsplays]

Just tried, but to no avail, it really seems like it has something to do with the mouse cursor, of all things. The artifacting still occurs even without --force-grab-cursor. The screen is fine in the main menu, but as soon as you actually load into the game (by that I mean, get past the main menu, and to a point where the cursor is hidden and locked), it happens. Also, really weird things start happening to the mouse controls. The weird mouse movement gets fixed with --force-grab-cursor, but then the artifacting will happen even in the menus, when it otherwise wouldn't.

[matte-schwartz]

Hmm, well that's unfortunate that it didn't work. Fwiw I tried to reproduce this on my own AMD iGPU+dGPU (7845hx/7900xtx mobile) laptop and wasn't able to, but I didn't have much time to check. Will look at it again when I'm back home in a couple weeks.