wine wayland windows not tearing (regression)

[nwnbark]

Hi, i recently tried wine wayland driver/winewayland.drv=b and noticed how the game can get in solitary, and in DS, but it never tears, i tried disabling DS, no_hardware_cursors = 1, but it still didn't tear. Btw the problem is exclusive to wine wayland which is weird because i saw that in a pull (#11228) hyprland supported tearing just fine.

  "vrr": false,
  "solitary": "55666ad0b8d0",
  "solitaryBlockedBy": null,
  "activelyTearing": false,
  "tearingBlockedBy": [
    "NOT_TORN"
  ],
  "directScanoutTo": "0",
  "directScanoutBlockedBy": [
    "USER",
    "SW"
  ],

Hyprland 0.54.0 built from branch main at commit 859bbb11e16029bfa5ad6a1418bde23f29bd7d86 dirty (config/actions: fix misuse of ActionResult's error type ( 14221)).
Date: Thu Apr 30 08:30:18 2026
Tag: v0.54.0-284-g859bbb11e, commits: 7219

Libraries:
Hyprgraphics: built against 0.5.1, system has 0.5.1
Hyprutils: built against 0.13.0, system has 0.13.0
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.11.0, system has 0.11.0

Version ABI string: 859bbb11e16029bfa5ad6a1418bde23f29bd7d86_aq_0.11_hu_0.13_hg_0.5_hc_0.1_hlg_0.6
no flags were set

KDE wayland tears the game so i don't think is my PC, i've also tried different games, proton-cachyos and proton-ge to no avail.

i also found by bissecting that last time tearing worked with winewayland was before 17e77e0, but im completely lost on how current compositor impl blocks and damages.

[nwnbark]

wine wayland tearing can be restored using the following patch:

diff --git a/src/protocols/types/SurfaceState.cpp b/src/protocols/types/SurfaceState.cpp
index 7e1baaad8..b2e693073 100644
--- a/src/protocols/types/SurfaceState.cpp
+++ b/src/protocols/types/SurfaceState.cpp
@@ -88,8 +88,8 @@ void SSurfaceState::updateFrom(SSurfaceState& ref) {
         bufferDamage = ref.bufferDamage;
     } else {
         // damage is always relative to the current commit
-        damage.clear();
-        bufferDamage.clear();
+        // damage.clear();
+        // bufferDamage.clear();
     }
 
     if (ref.updated.bits.input)

though i dont really know if that patch fucks a bit how hyprland is supposed to handle those 2 vars. So long i've tested it for a week and nothing out of the ordinary.

[MintJapan]

I had the same issue (in my case i usePROTON_ENABLE_WAYLAND=1), but I found that vanilla proton doesn't have this issue.
Switching to vanilla Proton (likely any version; I’ve confirmed on Proton 10 or later) is a temp fix for this.
I was very foolish, vanilla proton originally doesn't support wayland 😭😭😭😭😭😭😭

[MintJapan]

It seems this hasn't been fixed in the latest version v0.56.2 yet ☹️

❯ hyprland --version
Hyprland 0.56.2 built from branch v0.56.2 at commit efb50993780079460b0cbed1363e2166a2de1d9f clean ([gha] Nix: update inputs).
Date: Wed Aug 5 14:13:21 2026
Tag: v0.56.2, commits: 7661

Libraries:
Hyprgraphics: built against 0.5.1, system has 0.5.1
Hyprutils: built against 0.14.0, system has 0.14.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.14.0, system has 0.14.0

Version ABI string: efb50993780079460b0cbed1363e2166a2de1d9f_aq_0.14_hu_0.14_hg_0.5_hc_0.1_hlg_0.6
no flags were set

I checked my hyprland.lua:

hl.monitor({
    output   = "DP-1",
    mode     = "highres",
    vrr = 2
})

hl.config({
     ...
     allow_tearing = true
     ...
})

hl.window_rule({
    name  = "steamgames",
    match = { class = "steam_app_.*"},
    immediate = true
})

and hyprctl monitors with running a game (THE FINALS with the latest proton-cachyos-native):

Monitor DP-1 (ID 0):
        2560x1440@164.99899 at 0x0
        active workspace: 1 (1)
        special workspace: 0 ()
        reserved: 0 0 0 0
        scale: 1
        transform: 0
        focused: yes
        dpmsStatus: 1
        vrr: true
        solitary: 55875a0918d0
        solitaryBlockedBy: null
        activelyTearing: false
        tearingBlockedBy: next frame is not torn
        directScanoutTo: 55875a0918d0
        directScanoutBlockedBy: null

tearingBlockedBy doesn't say missing candicate so it's recognizing the game window.

GPU: RX 9060XT 16GB

Should I ping to developers as written in issue guidelines? This discussion got 5 upvotes but not 👍️, so should I not?

[erstarr]

same difference.

[erstarr]

@vaxerski 5 upvotes.

[vaxerski]

#16035