Overwatch: Mouse not working for menu entries in fshack build

RicArch97 commented 3 years ago

In Overwatch, the mouse cursor seems to be acquired by the game, as it changes into the Overwatch cursor as usual. However, the menu entries cannot be clicked. Hovering the mouse over them shows no activity.

Quite a shame since the fshack build seems to deal with the annoying input lag issue that is plaguing the regular lutris build. The game is much better playable with fshack, as tested in the practice range, by going there using the keyboard (which Overwatch does not support very well). Aiming and shooting does seem to work perfectly fine. The mouse is necessary in this game however because selecting a hero using a keyboard is simply not supported to avoid insta-locking heroes using keybinds.

This was tested with:

Build: lutris-fshack-6.13-2
Settings: fsync enabled

OS & hardware

OS: Arch Linux x86_64
Kernel: Linux-zen-5.13.5
WM: Sway
GPU: AMD Radeon 6900XT using Mesa 21.1.5 with RADV vulkan driver (no proprietary drivers)

tannisroot commented 3 years ago

I cannot reproduce this issue under Gnome. Could you try to reproduce the issue under Gnome or at least KDE?

RicArch97 commented 3 years ago

It does indeed appear to be working under Gnome.

So it could be a Sway specific issue. If so, do I report this directly to Sway?

Are there steps i could take to debug this issue further, or options i could try? It could just be a simple thing, but i currently wouldn't know what could cause this.

emaxoda commented 3 years ago

@RicArch97 i'm using KDE and here the mouse entries are bugged, they can be used but aren't located where it's supposed to be. video footage ot it I'm using NVIDIA and X11 so i don't know if this problem is related or if i should open another issue

RicArch97 commented 3 years ago

@emaxoda Does this also happen on windowed / borderless windowed?

RicArch97 commented 3 years ago

I've done some more testing. My issue specifically seems to be multi-monitor related in combination with fshack.

First test

Launch the game on my left (side) monitor, which is positioned at 0 0

Mouse worked in menues and game worked as it should.

Second test

Unplugged second monitor (on the left) and updated config accordingly

Everything worked as it should on the main monitor.

Third test

Plugged monitor back in, but changed position to -2560 0 for the left monitor and 0 0 for the main monitor instead of 0 0 for the left monitor and 2560 0 for the main one

This didn't seem to make a difference.

Fourth test

Switched to windowed mode in-game. And then back to borderless windowed

Now the mouse did work in the menues, even with both monitors active. Borderless windowed seemed to have small black bars on top and bottom however. Switching to fullscreen made the mouse inoperable in the menues again.

One note to take is just how good the game runs with fshack. It seems to get rid of input lag completely, feels even better than running the game on Windows.

tannisroot commented 3 years ago

@emaxoda Is the game set to native resolution?

emaxoda commented 3 years ago

@tannisroot if i set the game to native resolution all works as expected, the problem is when i run the game at lower resolutions

--

I tried removing one monitor from my setup (I'm using two monitors) and the clickable ui is still bugged (using full screen and a lower resolution), the clickable ui seems to be following the lower resolution, what i mean is that if i set the screen at 720p the "clickable ui" is resized to a 720p window even when the game is using all the screen.

expected results at native resolution

problem with clickable ui at lower resolutions

as you can see in the first screeshot the mouse pointer is located on top of the back button but in the second screenshot i have to locate the mouse pointer almost in the middle of the screen to trigger the back button

RicArch97 commented 3 years ago

Fixed by setting a primary output for XWayland. X11 expects a primary output to exist, but Wayland cannot provide this by default as it does not work with the concept of primary output. Use xrandr to check the output names for your setup if you have multiple monitors, and set it using xrandr like so: xrandr --output XWAYLAND0 --primary (for example). Closing this issue.

lutris / wine