[Bug 47536] New: Overwatch stops getting mouse input after alt-tabbing ( regression
https://bugs.winehq.org/show_bug.cgi?id=47536 Bug ID: 47536 Summary: Overwatch stops getting mouse input after alt-tabbing (regression Product: Wine Version: 4.12.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Through bisect, I've found this commit 82c6ec3a32f44e8b3e0cc88b7f10e0c0d7fa1b89 causes issues in Overwatch (a Blizzard game). To be specific, if the game is set to use Fullscreen or Windowed mode and you alt tab out of it even one time, it no longer allows you to aim. Instead, mouse cursor just kind of floats around the window, and I can even click in menus. The only way to recover it from that state is to relaunch it. The issue also doesn't seem to affect Borderless Windowed mode. Reverting that commit fixes the issue. I should note that during my testing, I had to use staging patches, as some of it are required to make it playable, but I don't know which ones it actually needs so I couldn't just apply them selectively. I am not really sure with which debug channels I should create the log with to help find the issue, so let me know which ones you need and I will record a log with them. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Alexandr Oleynikov <sashok.olen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sashok.olen(a)gmail.com, | |zzhang(a)codeweavers.com Regression SHA1| |82c6ec3a32f44e8b3e0cc88b7f1 | |0e0c0d7fa1b89 Keywords| |regression -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Alexandr Oleynikov <sashok.olen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Overwatch stops getting |Can't aim in Overwatch |mouse input after |after alt-tabbing |alt-tabbing (regression |(regression -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #1 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Created attachment 64937 --> https://bugs.winehq.org/attachment.cgi?id=64937 Send activate message after showing a minimized window -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #2 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Hi, could you try this patch and see if it fix the problem for you? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #3 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- Unfortunately it does not. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #4 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- I can't seem to run Overwatch on wine-staging 4.12.1, getting error of 0xe0010160. What graphics card are you using and what's your Overwatch version? Are you using any other workarounds? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #5 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- I have an Nvidia GTX 1070 and I use nvidia driver 418.52.17 (it should work with newer drivers too however). I also use latest master of staging, as afaik all d3d11 apps in current tagged 4.12.1 release simply don't work at all, and also DXVK. It should also be noted that Battle.Net requires some optional dependencies installed to just launch and an arial verb from winetricks, so maybe that's why you're getting a crash? You could also try using Lutris to set up the prefix. It makes the setup much more convenient and doesn't interfere with the prefix all that much (and not in ways that could introduce this issue). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #6 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Is your game version 1.38.0.3.60547? Could you upload a log with default channels? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #7 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- Created attachment 64941 --> https://bugs.winehq.org/attachment.cgi?id=64941 standardchannels It is currently at that version, sorry I didn't mention it in my previous comment. Here's a log with default debug channels. I used DXVK when recording it, but I can assure that it happens with Wined3d too. It doesn't seem like there is anything interesting in it though. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Torge Matthies <openglfreak(a)googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |openglfreak(a)googlemail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Justin <winehq(a)junaru.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq(a)junaru.com --- Comment #8 from Justin <winehq(a)junaru.com> --- Confirming that the bug still exists on current wine-staging-git from AUR (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wine-staging-git) both with and without Zhiyi Zhang's patch. Hardware: RX580 amdgpu, mesa 19.1.3-1, dxvk 1.2.1 No Overwatch specific workarounds used apart DLL overrides for d3d11 (builtin,native) and dxgi (builtin, native) for "Battle.Net Launcher.exe" in winecfg (Battle.net doesn't like DXVK, so this disables it just for the launcher). Also tried running Overwatch (1.38.0.3.60547) on both GNOME and XFCE4 to rule out that the issue is somehow WM specific - the bug persists in both GNOME and XFCE4. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #9 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- Seems like Proton guys also encountered issues with that commit: https://github.com/ValveSoftware/wine/commit/91b92633da9a6c990072fd3a82fb585... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Simon the Sorcerer <sur3(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sur3(a)gmx.de --- Comment #10 from Simon the Sorcerer <sur3(a)gmx.de> --- I found out I can get crosshair control again when doing: - Alt+Enter (Switching to windowed mode) - wmctrl -R Overwatch (Terminal Command [sometimes only works when executed as root]) - Switching back to the Overwatch window confirming Crosshair is working - Alt+Enter (Switching back to Full Screen) - Esc Esc (Eliminating Mouse drift) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #11 from Simon the Sorcerer <sur3(a)gmx.de> --- Ok it seems to be even easier you dont need the wmctrl -R command, just switching to an other window and then back to overwatch while being in windowed mode fixes it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Can't aim in Overwatch |Can't aim in Overwatch |after alt-tabbing |after alt-tabbing |(regression | -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #12 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Could you try if https://source.winehq.org/git/wine.git/commitdiff/3898ad408bb7ad50555ce6bce0... fixes the issue for you? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #13 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Please retest. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 --- Comment #14 from Simon the Sorcerer <sur3(a)gmx.de> --- Re-tested in Overwatch 2 with Wine-staging 7.22. In Multi-Monitor Setup sometimes Aim still is lost after dying in-game and you have to move the mouse cursor back over the window to be able to aim again which is annoying but much better than previous behaviour. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #15 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Closing since the original bug is fixed. Please open a new bug for the rest of the issues. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=47536 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 8.0-rc3. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla