Anyone know how the Wayland driver in WINE will impact? I mean Wine works on XWayland so far, so what can we expect to get better with native Wayland support? I’ve searched a bit in web, but its hard to find some definitive answers (lots of general WINE and Wayland topics, often outdated).
From my testing of the Wayland backend when it was still hidden behind a registry setting, it’s mainly for DPI awareness. For example, I use a 1440p screen with 1.25 scaling. Currently Wine through Xorg therefor sees my desktop as 1152p high. With the Wayland driver it would still correctly identify as using a 1440p screen.
Do you happen to know if you still need the HDR layer when using Wayland directly? I know gamescope didn’t require it for a while now but I never saw anything about it for Wine.
Anyone know how the Wayland driver in WINE will impact? I mean Wine works on XWayland so far, so what can we expect to get better with native Wayland support? I’ve searched a bit in web, but its hard to find some definitive answers (lots of general WINE and Wayland topics, often outdated).
From my testing of the Wayland backend when it was still hidden behind a registry setting, it’s mainly for DPI awareness. For example, I use a 1440p screen with 1.25 scaling. Currently Wine through Xorg therefor sees my desktop as 1152p high. With the Wayland driver it would still correctly identify as using a 1440p screen.
I’ve been using the unstable branch for this exact reason. Otherwise I’d have to change my scaling every time I launch a game.
Well, HDR works in Wine Wayland, and X11 can never do it without gamescope.
Do you happen to know if you still need the HDR layer when using Wayland directly? I know gamescope didn’t require it for a while now but I never saw anything about it for Wine.
Yes. The Mesa implementation for this stuff isn’t merged yet. Once it is merged, the layer will be irrelevant.
did they update gamescope to work with xorg?