[Bug 45876] New: Call of Duty Black Ops III no mouse input
https://bugs.winehq.org/show_bug.cgi?id=45876 Bug ID: 45876 Summary: Call of Duty Black Ops III no mouse input Product: Wine Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 62382 --> https://bugs.winehq.org/attachment.cgi?id=62382 Call of Duty Black Ops III wine log Hello, I managed to install Windows Media Foundation dlls and regs and the game finally started. It wotks very well with DXVK and has a good framerate. Unfortunately there's no mouse click input in the main menu. Actually there is a cursor but you don't click nowhere hence I started a new game via the keyboard. After the game starts it runs with high FPS but there isn't mouse and you can't navigate (turn right, left, up, down, etc). In the mean time right click works and it triggers the weapon's scope. Installing dx and xact doesn't help. Forced MouseWarpOverride and "Automatically capture the mouse in full-screen windows" doesn't help too. Please, tell me what log flags do you need and I'll provide them. The provided log is from begining of the game to the first level when the actual gameplay begins. -- 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=45876 mo78(a)abv.bg changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mo78(a)abv.bg --- Comment #1 from mo78(a)abv.bg --- I just found something interesting - I tried Call of Duty: WWII in the same Windows Media Foundation prefix and the game suffers from the exact same input problems. In the meantime Shadows: Awakening runs without any input problems in the same prefix. In some way Windows Media Foundation files prevent mouse input in CoD games. Call of Duty: WWII runs without inpit problems in a prefix without Windows Media Foundation regs and dlls but Call of Duty Black Ops III requires WMF and it doesn't start without it so I can't test in a clean prefix. In summary: Windows Media Foundation brakes the mouse input in some CoD games. Any ideas for solving this problem? -- 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=45876 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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=45876 --- Comment #2 from mo78(a)abv.bg --- Wine 3.18 - the problem is here. -- 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=45876 --- Comment #3 from mo78(a)abv.bg --- Wine 3.21 - the problem is still here. Please opt in. Do I soliloquize? -- 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=45876 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Call of Duty Black Ops III |Call of Duty: Black Ops III |no mouse input |and Call of Duty: WWII have | |no mouse input when using | |native mfplat CC| |z.figura12(a)gmail.com --- Comment #4 from Zebediah Figura <z.figura12(a)gmail.com> --- Please be patient, developer effort is stretched thin enough already ;-) This is printed many times in the log: 0042:fixme:rawinput:GetRawInputBuffer data 0x1555bed20, data_size 0x19d0fda8, header_size 24 stub! and may be meaningful. Can you please attach logs for Call of Duty: WWII both with and without native mfplat? -- 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=45876 --- Comment #5 from mo78(a)abv.bg --- Hello thank you for your answer :) Without mfplat the game doesn't run at all. Do you still need the log in this case? Or you mean to just remove it from overrides? -- 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=45876 --- Comment #6 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to mo78 from comment #5)
Hello thank you for your answer :) Without mfplat the game doesn't run at all. Do you still need the log in this case? Or you mean to just remove it from overrides?
In comment 1 you stated that Call of Duty: WWII could run without mouse input issues if native mfplat was not used, or am I misreading? -- 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=45876 --- Comment #7 from mo78(a)abv.bg --- I'm afraid that you don't understand me and this is probably because my bad english. I'm sorry for that. The game requires Windows Media Foundation and doesn't run at all without 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=45876 --- Comment #8 from Zebediah Figura <z.figura12(a)gmail.com> --- I mean the statement "Call of Duty: WWII runs without inpit problems in a prefix without Windows Media Foundation regs and dlls"; what did you mean by this? If you can't point to any games that suffer from this bug when native mfplat is used but run without errors when builtin mfplat is used, on what grounds do you believe that this is a bug related to native mfplat? -- 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=45876 --- Comment #9 from mo78(a)abv.bg --- Oh my God - silly me :) You talk about CoD WWII but I think for Cod Black Ops 3. Excuse me, I'm very sorry. Now, let's make things clear - you want from me to put CoD WWII in a prefix with WMF and to get a log. Then to put it into regular clean prefix and again to take a log. Is that right? And with which flags do you want to get the logs? Thank 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=45876 --- Comment #10 from Zebediah Figura <z.figura12(a)gmail.com> --- Right, that makes more sense. Mostly I'd like to see +rawinput. Though, as long as we're here, I guess I'd also add +event,+hook, just in case it turns out to be unrelated to raw input. -- 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=45876 --- Comment #11 from mo78(a)abv.bg --- Ok, thank you :) You'll have them ASAP as I generate 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=45876 --- Comment #12 from mo78(a)abv.bg --- Created attachment 62879 --> https://bugs.winehq.org/attachment.cgi?id=62879 +rawinput,+event,+hook WMF prefix.log -- 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=45876 --- Comment #13 from mo78(a)abv.bg --- Created attachment 62880 --> https://bugs.winehq.org/attachment.cgi?id=62880 +rawinput,+event,+hook clean prefix.log -- 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=45876 --- Comment #14 from mo78(a)abv.bg --- Here they are. However I'm afraid that I has been wrong. Actually in CoD WWII the mouse input doesn't work too but there is a difference - when I hit escape, at the Exit Game dialog I can choose and click Yes or No with the mouse. This isn't possible with CoD Black Ops III. For this part of my first post: "Call of Duty: WWII could run without mouse input issues if native mfplat was not used" It must be: "Shadows: Awakening could run without mouse input issues if native mfplat was not used" Here is the misstype that I made. Both CoD WWII and CoD Black Ops III have the problem with mouse input but the Shadows: Awakening not. Should I get log from Shadows: Awakening? -- 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=45876 --- Comment #15 from Zebediah Figura <z.figura12(a)gmail.com> --- Sure, if Shadows: Awakening displays a difference in behaviour, please grab logs from there instead. Note that your first two logs only contain DXVK and OpenAL output; they seem to be devoid of any Wine output whatsoever. -- 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=45876 --- Comment #16 from mo78(a)abv.bg --- Created attachment 62887 --> https://bugs.winehq.org/attachment.cgi?id=62887 Call of Duty: WWII +rawinput,+event,+hook clean prefix corrected.log -- 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=45876 --- Comment #17 from mo78(a)abv.bg --- Created attachment 62888 --> https://bugs.winehq.org/attachment.cgi?id=62888 Call of Duty: WWII +rawinput,+event,+hook WMF prefix corrected.log -- 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=45876 --- Comment #18 from mo78(a)abv.bg --- My fault now they are correct :) To summarize: Call of Duty: WWII has no mouse input problems with a clean prefix but has mouse input problems in a WMF prefix. I can however click with the mouse on some Nvidia warnings and on the popup windows for exiting the game. (The game have sound only in the ingame movies but that is another problem already filed from me). Call of Duty Black Ops 3 can't be started in a clean prefix fot it requires WMF. In a WMF prefix there isn't mouse clicks in the menu nowher. Ingame there isn't mouse at all except right click for the weapon's scope. You cant click on the Exit Game popup. Shadows: Awakening works with no problems in a WMF prefix and it's fully playable. It cannot be started in a clean prefix for the game requres WMF. -- 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=45876 --- Comment #19 from mo78(a)abv.bg --- Created attachment 62899 --> https://bugs.winehq.org/attachment.cgi?id=62899 Shadows Awakening +rawinput,+event,+hook WMF prefix -- 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=45876 --- Comment #20 from Zebediah Figura <z.figura12(a)gmail.com> --- Logs don't seem to show a difference in raw input or hooking; I guess this'll need a closer look. -- 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=45876 --- Comment #21 from mo78(a)abv.bg --- I'm sorry to hear that :( -- 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=45876 pattietreutel <katyaberezyaka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka(a)gmail.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=45876 --- Comment #22 from mo78(a)abv.bg --- Wine 4.0 - the problem is still here. -- 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=45876 --- Comment #23 from mo78(a)abv.bg --- Wine 4.1 - the problem is still here. -- 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=45876 --- Comment #24 from mo78(a)abv.bg --- Wine 4.3 - the bug is still here. -- 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=45876 --- Comment #25 from mo78(a)abv.bg --- Wine 4.4 - the bug is still here. -- 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=45876 --- Comment #26 from mo78(a)abv.bg --- With Wine 4.5 there aren't need to use Windows Media Foundation dlls. It runs out of the box but the mouse input problem remains. -- 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=45876 --- Comment #27 from mo78(a)abv.bg --- With Wine 4.5 there isn't need to use Windows Media Foundation dlls. It runs out of the box but the mouse input problem remains so the problem wasn't the mfplat prefix. Should I file a new bug? -- 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=45876 --- Comment #28 from mo78(a)abv.bg --- Nope my mistake. The game still requires to setup Windows Media Foundation like in Shadow: Awakening. I'm sorry for the false alarm. -- 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=45876 --- Comment #29 from mo78(a)abv.bg --- Wine 4.6 - the bug is still here. -- 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=45876 --- Comment #30 from mo78(a)abv.bg --- Wine 4.7 - the bug is still here. -- 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=45876 --- Comment #31 from Nikolay Sivov <bunglehead(a)gmail.com> --- Could you open a bug report for original issue with builtin mfplat libraries? Native libraries are not redistributable so additional issues that come with them are not that interesting. -- 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=45876 --- Comment #32 from mo78(a)abv.bg --- With the Wine mfplat implementation the game doesn't run. The only way for game to run is to prepare a mfplat prefix. -- 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=45876 --- Comment #33 from Nikolay Sivov <bunglehead(a)gmail.com> --- Right, do we have a bug report for that 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=45876 --- Comment #34 from mo78(a)abv.bg --- Apparently 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=45876 --- Comment #35 from mo78(a)abv.bg --- Here it is: https://bugs.winehq.org/show_bug.cgi?id=47084 -- 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=45876 --- Comment #36 from mo78(a)abv.bg --- Wine 4.8 - the bug is still here. -- 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=45876 --- Comment #37 from mo78(a)abv.bg --- Wine 4.9 - the bug is still here. -- 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=45876 --- Comment #38 from mo78(a)abv.bg --- Wine 4.10 - the bug is still here. -- 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=45876 --- Comment #39 from mo78(a)abv.bg --- Wine 4.11 - the bug is still here. -- 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=45876 --- Comment #40 from mo78(a)abv.bg --- Wine 4.12 - the bug is still here. -- 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=45876 --- Comment #41 from mo78(a)abv.bg --- Wine 4.13 - the bug is still here. Please confirm this bug. -- 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=45876 --- Comment #42 from mo78(a)abv.bg --- Wine 4.14 - the bug is still here. Please confirm this bug. -- 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=45876 --- Comment #43 from mo78(a)abv.bg --- Wine 4.15 - the bug is still here. -- 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=45876 --- Comment #44 from mo78(a)abv.bg --- Wine 4.16 - the bug is still here. -- 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=45876 --- Comment #45 from mo78(a)abv.bg --- Wine 4.19 - the bug is still here. -- 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=45876 --- Comment #46 from mo78(a)abv.bg --- Wine 4.20 - the bug is still here. -- 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=45876 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon(a)codeweavers.com --- Comment #47 from Rémi Bernon <rbernon(a)codeweavers.com> --- The mouse input issue should be fixed by 3a9edf9aad43c3e8ba724571da5381f821f1dc56, although I believe the game additional patches to start (maybe just the Steam version, if there's others). -- 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=45876 --- Comment #48 from mo78(a)abv.bg --- Will this be included in 5.12? -- 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=45876 mo78(a)abv.bg changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #49 from mo78(a)abv.bg --- I can confirm - 5.12 solves the problem. Thank 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=45876 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #50 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.13. -- 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