[Bug 48046] New: Resident Evil 4 (Steam): Frame rate issues when clicking the left mouse button
https://bugs.winehq.org/show_bug.cgi?id=48046
Bug ID: 48046 Summary: Resident Evil 4 (Steam): Frame rate issues when clicking the left mouse button Product: Wine Version: 4.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: skidrowa@gmail.com Distribution: ---
The game's frame rate tanks when you click the left mouse button and can go as low as 5 FPS if you hold click and move the mouse at the same time. The cursor also flickers between it's current position and the middle of the screen, making it virtually impossible to play using keyboard and mouse.
https://bugs.winehq.org/show_bug.cgi?id=48046
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Ken Sharp imwellcushtymelike@gmail.com --- Nothing to go on at all.
https://bugs.winehq.org/show_bug.cgi?id=48046
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |UNCONFIRMED CC| |z.figura12@gmail.com
--- Comment #2 from Zebediah Figura z.figura12@gmail.com --- (In reply to Ken Sharp from comment #1)
Nothing to go on at all.
While I recognize this isn't the perfect bug report, I feel like claiming "nothing to go on" and immediately resolving the bug as INVALID is a bit of an unfair response. Better to ask (politely) for whatever the bug report is missing and tag it as NEEDINFO.
https://bugs.winehq.org/show_bug.cgi?id=48046
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- To the original reporter, could you please attach default console output from running the program and reproducing this bug?
https://bugs.winehq.org/show_bug.cgi?id=48046
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Component|-unknown |directx-dinput
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- This sounds like the bug Derek was debugging a few days ago. IIRC the game quickly acquires / unacquires the mouse while the mouse button is pressed.
https://bugs.winehq.org/show_bug.cgi?id=48046
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair@hotmail.com
--- Comment #5 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to Matteo Bruni from comment #4)
This sounds like the bug Derek was debugging a few days ago. IIRC the game quickly acquires / unacquires the mouse while the mouse button is pressed.
Maybe, Derek can attach a dinput log then?
https://bugs.winehq.org/show_bug.cgi?id=48046
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dereklesho52@Gmail.com
https://bugs.winehq.org/show_bug.cgi?id=48046
--- Comment #6 from skidrowa@gmail.com --- Created attachment 65669 --> https://bugs.winehq.org/attachment.cgi?id=65669 dinput log
Here's a log using WINEDEBUG=+dinput
https://bugs.winehq.org/show_bug.cgi?id=48046
--- Comment #7 from dereklesho52@Gmail.com --- As Matteo mentioned, the game repeatedly acquires and unacquires the mouse while MOUSE1 is held down. When this happens wineserver usage goes up to 100% of a core, so I'd guess messages aren't being processed by the application.
I think a good next step would be to find out whether a wine bug is causing the game to exhibit this behavior, and then if not, whether Windows handles this without locking up the game.
https://bugs.winehq.org/show_bug.cgi?id=48046
--- Comment #8 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to dereklesho52 from comment #7)
As Matteo mentioned, the game repeatedly acquires and unacquires the mouse while MOUSE1 is held down. When this happens wineserver usage goes up to 100% of a core, so I'd guess messages aren't being processed by the application.
I think a good next step would be to find out whether a wine bug is causing the game to exhibit this behavior, and then if not, whether Windows handles this without locking up the game.
It might be worth checking, if the Unacquire never sets This->acquired to FALSE.
From the log attached,
Here is the first Acquire, 00f8:trace:dinput:SysMouseWImpl_Acquire (this=0xcf994c0) 00f8:trace:dinput:IDirectInputDevice2WImpl_Acquire (0xcf994c0) 0133:trace:dinput:hook_thread_proc Processing hook change notification lp:0 00f8:trace:dinput:warp_check Warping mouse to 643 - 415 00f8:trace:dinput:warp_check Clipping mouse to (3,55)-(1283,775)
Next we have this. In theory the Acquire shouldn't be lost at this point and will return S_FALSE. So, testing this scenario might help. 0112:trace:dinput:SysMouseWImpl_Acquire (this=0xcf994c0) 0112:trace:dinput:IDirectInputDevice2WImpl_Acquire (0xcf994c0) 0112:trace:dinput:SysMouseWImpl_Unacquire (this=0xcf994c0)
https://bugs.winehq.org/show_bug.cgi?id=48046
Neko-san nekoNexus@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus@protonmail.ch
-
WineHQ Bugzilla