xwayland: Implement wp_tearing_control_v1 (!665) · Merge requests · xorg / xserver · GitLab
gitlab.freedesktop.org
See wayland/wayland-protocols!65 Depends on

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!

  • Felix@feddit.deEnglish
    7·
    1 year ago

    I know this might sound sumb to some. But I have a freesync monitor, so as long as I stay within my freesync range, I should still be completely tear free, even with V-sync disabled, right?

      • mccord@kbin.social
        3·
        1 year ago

        I’m on KDE and setting software cursor via KWIN_FORCE_SW_CURSOR=1 fixed that for me in games like PoE where the cursor began to lag heavily if there are fps drops from like 144 to 90. If you need hardware cursor KWIN_DRM_NO_AMS=1 should also help.

    • UrbenLegend@lemmy.mlOPEnglish
      2·
      1 year ago

      I am not sure as I’ve never used VRR on Wayland with an AMD GPU before, but that does sound like how its supposed to work. That’s what I do with my Nvidia card when using Gsync or Freesync in X11.

      • Felix@feddit.deEnglish
        1·
        1 year ago

        At least that’s how it used to work on Windows (10) Just disable v-sync ingame and freesync should take care of the tearing. Although over here, some people say that you have to enable v-sync, then Wayland by itself has v-sync, kinda making freesync irrelevant?¿? I guess I’m just gonna wait for a new release of Xwayland and for it to land on Arch’s repos so that I can test it out.