World of Warcraft: Difference between revisions
No edit summary |
No edit summary |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
WoW 3.3.5a mostly works with Proton. but mouse camera movement is borked for all monitors except the primary monitor. Video: https://www.youtube.com/watch?v=zl-WrmCkNsY | WoW 3.3.5a mostly works with Proton. but mouse camera movement is borked for all monitors except the primary monitor (camera of chaos). Video: https://www.youtube.com/watch?v=zl-WrmCkNsY | ||
This appears to be caused by some issue with the way the X11 window and mouse cursor positions are being handled in Wine, the behaviour isn't quite the same as on Windows resulting in the camera being borked. | |||
Borked behaviour occurred with Proton-GE, Proton Experimental and Wine-GE so it seems to impact most of the common Wine/Proton variants. | Borked behaviour occurred with Proton-GE, Proton Experimental and Wine-GE so it seems to impact most of the common Wine/Proton variants. | ||
| Line 6: | Line 8: | ||
==== Gamescope ==== | ==== Gamescope ==== | ||
This option is to run the game inside Valve's gamescope compositor. This does work to resolve the camera issue, but you don't get clipboard, which is annoying when trying to copy-paste your login password from your password manager. The window also can't be dynamically resized under gamescope, resulting in incorrect font sizing, letterboxing or pillarboxing. On top of this, gamescope grabs cursor when clicking in the window, which is irritating. | |||
==== Gamescope with clipboard ==== | ==== Gamescope with clipboard ==== | ||
Gamescope clipboard only works in SDL backend at the moment. Using the SDL backend therefore fixes the clipboard. You also have to tell the SDL backend to use Wayland for windowing. | |||
Pass this additional command line argument to gamescope: | |||
--backend sdl | --backend sdl | ||
| Line 15: | Line 19: | ||
SDL_VIDEODRIVER=wayland | SDL_VIDEODRIVER=wayland | ||
Unfortunately this causes the OS mouse cursor to be rendered over the top of the regular cursor. | Camera and clipboard both work now! | ||
Unfortunately, this causes the OS mouse cursor to be rendered over the top of the regular cursor. Ugh! | |||
==== PROTON_ENABLE_WAYLAND ==== | ==== PROTON_ENABLE_WAYLAND ==== | ||
You can force Proton to use Wayland by setting env var: | You can force Proton to use Wayland directly by setting this env var: | ||
PROTON_ENABLE_WAYLAND=1 | PROTON_ENABLE_WAYLAND=1 | ||
Unfortunately this breaks the window border; you get a Wine-rendered border and the window can't be moved or resized properly. This setting is therefore only useful if you want to play in borderless windowed mode. | Unfortunately this breaks the window border; you get a Wine-rendered border and the window can't be moved or resized properly. This setting is therefore only useful if you want to play in borderless windowed mode, within which you can move the window around using Win+Shift+Arrow without the camera breaking. It's no good if you want to run in regular windowed mode. | ||
Latest revision as of 19:30, 8 February 2026
WoW 3.3.5a mostly works with Proton. but mouse camera movement is borked for all monitors except the primary monitor (camera of chaos). Video: https://www.youtube.com/watch?v=zl-WrmCkNsY
This appears to be caused by some issue with the way the X11 window and mouse cursor positions are being handled in Wine, the behaviour isn't quite the same as on Windows resulting in the camera being borked.
Borked behaviour occurred with Proton-GE, Proton Experimental and Wine-GE so it seems to impact most of the common Wine/Proton variants.
Here are some workaround options, although all of them suck in their own ways, none of them give native behaviour like on Windows.
Gamescope
This option is to run the game inside Valve's gamescope compositor. This does work to resolve the camera issue, but you don't get clipboard, which is annoying when trying to copy-paste your login password from your password manager. The window also can't be dynamically resized under gamescope, resulting in incorrect font sizing, letterboxing or pillarboxing. On top of this, gamescope grabs cursor when clicking in the window, which is irritating.
Gamescope with clipboard
Gamescope clipboard only works in SDL backend at the moment. Using the SDL backend therefore fixes the clipboard. You also have to tell the SDL backend to use Wayland for windowing.
Pass this additional command line argument to gamescope:
--backend sdl
You also need to run it with this env var:
SDL_VIDEODRIVER=wayland
Camera and clipboard both work now!
Unfortunately, this causes the OS mouse cursor to be rendered over the top of the regular cursor. Ugh!
PROTON_ENABLE_WAYLAND
You can force Proton to use Wayland directly by setting this env var:
PROTON_ENABLE_WAYLAND=1
Unfortunately this breaks the window border; you get a Wine-rendered border and the window can't be moved or resized properly. This setting is therefore only useful if you want to play in borderless windowed mode, within which you can move the window around using Win+Shift+Arrow without the camera breaking. It's no good if you want to run in regular windowed mode.