As an AMD user on Wayland who primarily uses Steam/Proton, I haven’t had any Wayland-related issues with gaming at all. This isn’t surprising, since the compositor used by Steam Deck (Gamescope) is also Wayland-based.

FYI: If you ever do have compositor-related issues (X11 OR Wayland), you can almost always fix the issue by running the game in a nested Gamescope instance by editing the game’s launch command.

545 will have better wayland support. For now X11 is a better choice i guess. (i don’t own an nvidia gpu)

Last I looked it still wasn’t working well enough, so I decided to stick with Xorg. But that was a few months ago.

With recent drivers and recent enough DEs it is usable to a certain extent. There are some known issues documented in the release notes of each version. Here’s for 535. TL; DR the major blockers are: (1) Variable Refresh Rate doesn’t work for some older cards; (2) GAMMA_LUT is not implemented (no night light) and (3) Nested X11 clients have synchronisation issues that might result in some flickering or dupicate frames, it’s more noticeable on things that refresh slowly, although much better recently. Also (4) NvFBC capture doesn’t work with nested X11 clients which might or might not be important for some people.

I’m using it with Plasma; it’s OK, no major concerns but my setup is pretty basic.

I haven’t had issues with games and Wayland, but I’m sticking with Xorg for now because KDE Plasma and the tiling window managing plugin I use still behave erratically. I often see visual bugs in the compositor overall, and the fact that apps die if we need to restart it is a deal breaker to me. Maybe these are related to Nvidia, but as far as gaming goes, I haven’t noticed much of a difference.

I would personally stick with X11 for now. Last time I tried Wayland it worked but all sorts of just strange issues started popping up everywhere. Nothing big but annoying and frustrating to fix. This was using KDE Plasma.

Gnome and Wayland works very well, with amd or Nvidia. If you’re a kde user you may run into more issues.

This blocks nVidia on Wayland until we get enough applications away from X11. There are some people who think of this as no big deal, or there are a lot of use cases where people don’t run into this, but I’ve seen enough applications stutter, drop frames, or mess up entirely under Xwayland because of the lack of implicit sync.

The 535 series gets us much farther in a lot of ways on Wayland, but we still have so far yet to go due to this issue. We’re still not there in regards to VRR, either, as nVidia has stated VRR (gsync) isn’t reported by the nvidia-drm module, but there has been a public statement that they are trying to get it into the 545 release.

As far as VRR itself is concerned, Mutter itself under version 44 needs a rebase to support it, but that’s a Mutter issue. Plasma users are going to have a better experience than Gnome users at this point, which I find very odd to say, but that’s more of a testament to the Plasma devs being absolutely awesome on another level lately, and is not to detract from the good work the Gnome project has been doing.

TL:DR We’re not quite there, even still, for a very small list of reasons now as opposed to a large list just a year ago.

Nvidia or not, stick with X11 until you have a reason to use Wayland.

I need Wayland for my packaging work, and one of my devices requires Wayland so I use it for that and it’s a decent experience, but Wayland still has drawbacks (weaker automation API, some programs still don’t work) so I wouldn’t recommend switching off X11 unless you have a reason.