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.

  • Which distribution? Maybe its an issue with the packaging. 580 is the last version that supports the older 10xx cards and there were some packaging changes in Archlinux. Now your card is newer than that and should not be affected. But maybe your distribution made some changes to packaging that caused the issue?

  • Hey OP, can you try running a nested gamescope session to see if that fixes the issue? I usually always do this as a rule of thumb for all full screen applications due to the many QoL features like real Vsync.

    Actually, can you even do that on Wayland yet, or is that Xorg-only?

    • This is the way. Just recently I used Bazzite’s rollback/rebase feature to debug what turned out to be monitor firmware bug in Gsync triggered in very specific circumstances and not Nvidia drivers’ update. Shit’s lit.🔥

    • 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.

      • 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…

        • 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.

  • NutWrench ( NutWrench@lemmy.ml ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I recently upgraded from Linux Mint 21.3 to 22.2 and my login screen STILL shows the Wayland (Cinnamon) display manager as “experimental.” Wayland runs a lot smoother on 22.2 and it’s a lot less crash-ey, but I don’t think it’s ready for prime time, yet. (Your own mileage may vary.)