Strange screen tearing problems on Arch Linux with RX 6600 XT
by Chloroxite from LinuxQuestions.org on (#6K33Y)
Hello! I've been experiencing an issue with my recently installed RX 6600 XT gpu where without any sort of vsync enabled in various games, it'd appear as though portions of the screen were running at a significantly lower framerate than other portions. When enabled it would sort of fix it but then introduce extreme input delay (probably to be expected). I've been wracking my brain on this issue for a few months now. I should note that I did not experience this issue on my old gpu (An RX 570 8gb), nor do I experience this issue under windows 11. This also does not appear to happen outside of 3D graphical applications.
Here's a comprehensive list of things I've tried, and their effects, to the best of my memory:
-Turning TearFree on: caused some other issues where the entire screen would appear to run at a lower fps than reported by fps trackers such as mango hud under some circumstances.
-Turning OFF TearFree AND allowpageflipping: seemed to have no effect.
-Changing proton versions: no effect.
-Enabling vsync: fixed, but introduced horrible input latency. Looking for alternatives.
-Cranking up framerate cap to be significantly higher than refresh rate: Seemingly hides the effect entirely when feasible, but not feasible for heavier games.
-Forcing RADV: Some games were already using this, doesn't seem to have an effect.
-Attempted launching games with different schedulers: Admittedly I'm not sure what I'm doing here, and the effect appears to be nil.
-Launching the game using mesa mailbox mode: for some strange reason has no effect. Doesn't even report mailbox present mode in mango.
-Verifying that xrandr is configured correctly: xrandr is already set to my monitor's native resolution and refresh rate.
-Playing under Wayland: issue was made ever so slightly worse.
-Disabling Picom (my compositer): No effect.
I've been looking everywhere on the internet for solutions and have come up entirely empty. Any suggestions would be very much appreciated. I'll update if I find a fix myself as well.
Here's a comprehensive list of things I've tried, and their effects, to the best of my memory:
-Turning TearFree on: caused some other issues where the entire screen would appear to run at a lower fps than reported by fps trackers such as mango hud under some circumstances.
-Turning OFF TearFree AND allowpageflipping: seemed to have no effect.
-Changing proton versions: no effect.
-Enabling vsync: fixed, but introduced horrible input latency. Looking for alternatives.
-Cranking up framerate cap to be significantly higher than refresh rate: Seemingly hides the effect entirely when feasible, but not feasible for heavier games.
-Forcing RADV: Some games were already using this, doesn't seem to have an effect.
-Attempted launching games with different schedulers: Admittedly I'm not sure what I'm doing here, and the effect appears to be nil.
-Launching the game using mesa mailbox mode: for some strange reason has no effect. Doesn't even report mailbox present mode in mango.
-Verifying that xrandr is configured correctly: xrandr is already set to my monitor's native resolution and refresh rate.
-Playing under Wayland: issue was made ever so slightly worse.
-Disabling Picom (my compositer): No effect.
I've been looking everywhere on the internet for solutions and have come up entirely empty. Any suggestions would be very much appreciated. I'll update if I find a fix myself as well.