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!

    • UrbenLegend ( UrbenLegend@lemmy.ml ) OP
      link
      fedilink
      English
      arrow-up
      4
      ·
      3 years 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.

    • taka ( taka@toast.ooo ) 
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 years ago

      It’s not a huge amount of latency, so it’s probably not super noticible to people who don’t pay much attention. I’m pretty sensitive to input lag, and it does feel noticeably worse than both X11 without compositing and windows.

      It is possible to get decent latency currently, with VRR + mailbox + fps cap, but there is still no VRR support if you use gnome.

    • Nyanix ( nyanix@dataterm.digital ) 
      link
      fedilink
      English
      arrow-up
      2
      ·
      3 years ago

      Same boat as UrbenLegend, it’s noticeable when playing FPS’s. It’s like the latency you experience when playing on modern game consoles, if you don’t notice it, then that’s great for you, but oncenyou get used to the low latency responses of PC gaming, it’s really hard to go back, not so much for how it impacts how well you do, but because the latency suddenly feels like you lack control.