Collabora have given an end of year update on how the work towards running the Windows compatibility layer on Wayland is coming along and it sounds good.
Their focus has been to keep up with upstream Wine development, which involved "splitting the driver into a PE and Unix part, updating it for the latest internal driver APIs, and making preparations to support WoW64". A big improvement is that it now supports cross-process rendering, something required for Chromium/CEF applications. On top of that they've also worked on improved support for the linux-dmabuf v4 Wayland protocol (aka dmabuf-feedback), that "allows compositors to dynamically send information about optimal formats and modifiers, e.g., depending on the surface presentation mode (fullscreen vs windowed)" plus many other ehancements.
On the Wine Development mailing list, developer Alexandros Frantzis also touched on when to expect the code in upstream Wine:
Last year, due to the extensive ongoing internal rework in Wine (e.g., win32u), the decision was made to postpone the upstreaming of the Wayland driver until some amount of internal stability had been reached. My impression is that things are a lot more stable now, from the drivers' point of view at least. Is there any upcoming work that people feel would be severely hindered by the upstreaming of the Wayland driver?
Ideally, I would like to start the upstreaming effort (which I expect will take some time) at some point early next year, after the codebase has been unfrozen. Does this sound reasonable?
They also provided a video to show off the latest work that shows: Chrome with accelerated cross-process rendering, LibreOffice, Call of Duty 2 (Demo), Crayon Physics Deluxe, Dagon, Factorio, The Last Express and Phoning Home.
Direct Link
Why is this important? It's because Wayland is gradually replacing X11, and having Wine run on it natively without another compatibility layer in between like XWayland will hopefully improve performance and reduce another layer of complexities to go through for both users and developers.
Article taken from GamingOnLinux.com.
Now, admittedly this was a niche use-case (running old pre-D3D9 games) and some of these issues might be specific to my system and/or build.
What's positive is that wine-wayland had less issues than (Wine with) Xwayland. Both games ran without problem. I'm also quite impressed by the development pace of wine-wayland it seems to progress much faster than I had anticipated!
I had some pretty mixed experience running (vanilla) Wine on Wayland. Of the two games I tried, one had missing UI elements, the other just hang after the intro.
I don't use WINE very often, but so far every game I've tried has worked fine with vanilla WINE and XWayland (using Sway WM). Everything I ran was D3D9 or later though, and this was just in the past couple months using the latest WINE + DXVK.
In any case I'm excited for wine-wayland, to drop some X11 dependencies and possibly improve performance :)
hardpenguin Dec 13, 2022
fenglengshun Dec 14, 2022
Cool.This is literally how I feel whenever new Wayland/Portal things land. Cool.
I guess I tried making Wayland work for me once, it was too much of a pain in the ass. I'll wait until it reaches "just works", all the tools matures, and I don't notice any differences. So it's cool whenever new Wayland things lands, but just that, cool.
Yes, well, I use Mint, which seems to have about that attitude as a distro, so my experience of Wayland is pretty theoretical. So I'm kind of waiting for the time when Clem decides he's ready to go for it. Every Wayland announcement I'm sort of thinking "Wonder how close we are to when Wayland gets boring enough to be 'ready for Mint'?"Cool.This is literally how I feel whenever new Wayland/Portal things land. Cool.
I guess I tried making Wayland work for me once, it was too much of a pain in the ass. I'll wait until it reaches "just works", all the tools matures, and I don't notice any differences. So it's cool whenever new Wayland things lands, but just that, cool.
Patreon
PayPal
See more from me