Gaming on Wayland, or more specifically sway WM, broke for me when updating to nvidia drivers version 580.

Reverting to 570 fixed the problem.

Card: Nvidia RTX 3060 Ti

What exactly happened: some games wouldn’t launch at all (overwatch 2) while others had severe performance issues (Resident evil 5).

Those were the only two games I tried. Both ran through steam and Proton GE version 10.

Though I didn’t test extensively, both games seemed to work fine on Xorg with nvidia drivers 580. So this confirms it’s only problematic for Wayland.

    • thingsiplay@beehaw.org
      3·
      2 days ago

      How do you know its a Wayland issue? Edit: I mean its not the entirely same setup, because Sway WM does not run on Xorg. That means there are other differences in play than Wayland only.

      • LainTrain@lemmy.dbzer0.com
        2·
        2 days ago

        You’re right of course - it could be a Sway issue, but with Sway being engineered from the ground up to be a Wayland compositor, and conforming to that design, I would still blame Wayland.

        To give a comparison: NTFS has many annoying flaws and limitations, but because it’s ultimately a file system created for the NT kernel on Windows, I blame Windows for its limitations.

        Besides common sense would suggest that usually when it comes to launching games a display protocol would have more impact than a choice of WM, though Wayland blurs that line because of it’s unusual architecture compared to what we know and love with the X11 protocol and good old Xorg…

        • thingsiplay@beehaw.org
          1·
          2 days ago

          It doesn’t even need to be Sways issue. What I mean are secondary issues like packaging of Sway or related packaged that are used when using Sway or Wayland. It doesn’t need to be a Wayland issue in itself. I just had in the past issues and quickly blamed something and it turned out something different.