https://bugs.winehq.org/show_bug.cgi?id=56676
Bug ID: 56676 Summary: native wayland resolution with 32bit games on wow64 grabs input Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: zlice@crtdrift.us Distribution: ---
Enabling wow64 (64bit wine without separate 32bit) to get native wayland wine running seems to have issues when rescaling input. Fallout 3 and KOTOR have similar related issues.
Fallout 3 - if you are at a different resolution than what is set in the ini, the game opens a popup saying to run the launcher because your input does not support the resolution. This popup seems to freeze all input related to the window manager (labwc), where the mouse is locked and keyboard shortcuts will not work. You can use tab/arrows to press the 'ok' button which will close the popup. Changing to the resolution with wlr-randr to match the ini file runs fine afaict.
KOTOR - this game changes resolution a lot for startup and cutscenes. It also has a lower resolution compared to most games and does not hit 1080p. Similarly input is trashed and does not work as expected. The game does not start. I assume if the game did start it would constantly want to change resolution for cutscenes.
Using XWayland does not appear to have the same issues. But it does not change resolution appropriatey (and with it, refresh rate).
I was only able to get 32bit games running under native wine+wayland with the wow64 mode. Not sure if I missed something with the build or if 32bit is not properly set up yet. KOTOR had an error about using the null/noa(?) driver. Fallout 3 just didn't run, assert(!status) for vkCreateInstance at winevulkanloader.c:271
I can file separate bug for resolution scaling in wayland vs the input grab.
System
- kernel 6.9.0 - wine 9.8 - void linux - labwc 0.7.2 (wayland wlroots)