OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
display-monitors low common DISPUTE

Allow tearing in games without tearing the desktop

omarchyarchendeavouroscachyoshyprlandwaylandamdnvidiadesktop
AUDITED Audited against its sources and confirmed accurate.

Symptom

Either the opposite complaints: a game feels laggy because it is vsynced and allow_tearing seems to do nothing, or the desktop tears randomly after every reboot and after every lock/unlock cycle on an AMD card over DP 1.4 DSC.

Cause

Tearing in Hyprland is opt-in per window and only takes effect when the game is fullscreen and is the *only* thing on that monitor. A notification, bar, overlay or lockscreen on the same output silently disables it. Conversely, unwanted desktop tearing on AMD DSC links is usually a modeset/driver state issue that clears when something forces a re-modeset (users report the hyprsunset restart in Omarchy's update flow doing exactly that).

Fix

To enable tearing for a game (Hyprland 0.55+):


hl.config({ general = { allow_tearing = true } })
hl.window_rule({ match = { class = "cs2" }, immediate = true })

On Hyprland <= 0.54:


general { allow_tearing = true }
windowrule = immediate, class:^(cs2)$

The window must be fullscreen with nothing else drawn on that monitor. If the app freezes instead of tearing, your GPU driver does not support it, so turn allow_tearing back off.

For unwanted desktop tearing, force a re-modeset without rebooting:


hyprctl dispatch 'hl.dsp.dpms({ action = "disable" })'; sleep 2
hyprctl dispatch 'hl.dsp.dpms({ action = "enable" })'
# or on Omarchy
omarchy-restart-hyprsunset

And make sure tearing is not globally on: hl.config({ general = { allow_tearing = false } }).

Verify

In-game frame times stop being quantised to the refresh interval (tearing enabled), or the tear line disappears from the desktop after the re-modeset.

Sources

screen-tearing-in-games-not-enabled