10.0.r2.g23ccc2ee

This one's a tad more closer to actually "being there". However, in my previous release, I was mistaken, while the command will sometimes lead to using the wayland backend, it's not consistent, the only consistent method I've found, is setting the registry key, simply create an empty text file, call it wayland.reg (the name actually doesn't matter, just the extension) and fill it with this

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Wine\Drivers]
"Graphics"="wayland"

Then using protontricks, select whatever game/program you wish to run, it'll complain, just click okay until you reach the menu, select the default prefix, run winereg, click flile, click import registry key, and import the .reg you created. It will then start in wayland...or it'll crash, but that seems very few and far between this time around.

Noteable issues I've found with this build:
First is mouse acceleration, it will either be fine, or way to sensitive, not much I can do about it, but in the vast majority of cases, it's fine.

Second is scaling, if the screen isn't windowed, it'll probably be the wrong resolution for your monitor, same as before, not much I can do.

Finally, controller support, it seems extremely hit or miss. This may be steams input being weird, or something else, but I don't know what causes the issues.

9.22.r1.g891daebf

This is specifically for steam, but you can easily adapt it to lutris, but I'm not doing that for the moment.

To force wayland, you need to pass

env -u DISPLAY %command%

In steam, however, be warned, this has crashed my GPU driver in multiple applications and is still highly unstable, but a number of games work without issue. Exclusive fullscreen still seems improperly implemented, so any application that doesn't use native resolution, will not fill the entire screen.

As of Wine 9.22 it should try the Wayland driver first, and if issues are found, revert to the x11 driver, so use the force command cautiously.

9.0rc3-1-Arch

I've tested this version in quite a few places, but one oddity is that in BG3, you can't run it in Vulkan mode as the shadder compiler crashes out, but even in DX11, it runs better than 8.0 releases that are ran with Vulkan in my testing.

Note that notable oddities are simply as examples of strange behaviors, and not all encompassing.