cross-posted from: https://lemmy.ml/post/1458833

Many Linux users have cited Wayland’s forced vsync as a blocker for gaming related scenarios. This patch adds tearing support into Xwayland!

  • iusearchbtw@beehaw.org
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    3
    ·
    1 year ago

    In what situations is this a blocker for gaming? Like, genuinely, who actually had any significant issues from it? Top 1% Counter Strike pros? I’ve been playing games on Wayland for ages and I never understood how anyone can think the experience is worse, let alone so bad it’s unusable.

    • UrbenLegend@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I play a lot of FPS and third-person games so input latency is incredibly important to me. Honestly, once you try gaming in a truly low-latency environment (VRR, high refresh rate), it’s hard to go back. Every time I try gaming in KDE Wayland on Radeon 680M, I notice mouse input lag and bad frame pacing.

      The only Wayland compositor that I know of that doesn’t exhibit these issues is the one used on the Steam Deck, but I am guessing there’s some special sauce there.

    • nani8ot@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      It really depends on the hardware. With 144Hz vsync isn’t much of an issue for me, but 60Hz is noticeably worse with vsync on.

    • proton_lynx@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Most likely FPS games but probably any kind of game where you need a fast response time. I understand that some people don’t notice input lag with vsync on, but for me it’s unusable. I’m not even close to the “Top 1% Counter Strike pros” but when I’m playing Portal 2, CrossCode, Deep Rock Galactic, Valheim, CS Go, Path of Exile, etc, it bothers me A LOT.