[Bug 33436] New: Tomb Raider (2013): Game does sometimes not respond to mouse move
http://bugs.winehq.org/show_bug.cgi?id=33436 Bug #: 33436 Summary: Tomb Raider (2013): Game does sometimes not respond to mouse move Product: Wine Version: 1.5.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: felixhaedicke(a)web.de Classification: Unclassified Sometimes the game does not react properly to mouse movement events (camera gets stucked). This happens reproducible in some game scenes. By switching to window mode (pressing Alt+Return) or back to fullscreen mode, these issues can be temporarily avoided. And the mouse issues are overall much less serious in window mode. Not all systems are equally affected by this bug. The graphics performance seems to matter. On a Laptop with an Intel GPU (which is much too slow for this game), it happens in almost every scene. And on a PC NVIDIA GeForce 560 Ti (normally almost > 60 FPS), this bug only occurs sometimes if StrictDrawOrdering is enabled. The game uses raw input mouse events. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 --- Comment #1 from Felix Hädicke <felixhaedicke(a)web.de> 2013-04-21 14:10:47 CDT --- Created attachment 44244 --> http://bugs.winehq.org/attachment.cgi?id=44244 First workaround patch (using mouse event correction values) I did some research and found this first (admittedly inelegant) workaround. The problem seems to be that the desktop->cursor.x / desktop->cursor.y values get changed in a way that relative raw input mouse events can not be properly calculated. This is caused by frequent SetCursorPos() calls. This patch introduces correction values used for the raw input events. But this workaround does not always give back full movement freedom. Sometimes (probably because absolute instead of relative mouse move events are used almost all the time) there is a movement restriction on the left, right, top and bottom. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 --- Comment #2 from Felix Hädicke <felixhaedicke(a)web.de> 2013-04-21 14:18:03 CDT --- Created attachment 44245 --> http://bugs.winehq.org/attachment.cgi?id=44245 Second workaround patch - disable SetCursorPos function I don't know why the game frequently calls SetCursorPos(), but disabling this function (makting a stub out of it) helps and seems to be a better workaround for this game. At least if XInput2 is used, the movement restrictions of the other patch seem to be gone - but this ist not really intensely tested. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 --- Comment #3 from Andrey Gusev <andrey.goosev(a)gmail.com> 2013-04-23 10:13:07 CDT --- It does exist for me too. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 chizu(a)spicious.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chizu(a)spicious.com --- Comment #4 from chizu(a)spicious.com 2013-07-16 16:04:47 CDT --- (In reply to comment #2)
Created attachment 44245 [details] Second workaround patch - disable SetCursorPos function
I don't know why the game frequently calls SetCursorPos(), but disabling this function (makting a stub out of it) helps and seems to be a better workaround for this game. At least if XInput2 is used, the movement restrictions of the other patch seem to be gone - but this ist not really intensely tested.
Testing with wine-1.6-rc5, this doesn't solve the problem for me. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 --- Comment #5 from chizu(a)spicious.com 2013-07-16 16:25:07 CDT --- As suggested in bug 33479, reverting 76bbf106a28c4caa82873e8450bde7d4adc765bf allows the work around of disabling SetCursorPos to function again. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 DL <dredgingthelake(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dredgingthelake(a)gmail.com --- Comment #6 from DL <dredgingthelake(a)gmail.com> 2013-09-28 01:42:04 CDT --- Same issue occurs with Bioshock although these reverts didn't seem to help. Switching from windowed mode back to fullscreen does work around the issue, though. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 Andrey Gusev <andrey.goosev(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrey.goosev(a)gmail.com --- Comment #7 from Andrey Gusev <andrey.goosev(a)gmail.com> --- Confirming. With the second workaround patch attachment 44245 issue is gone. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 DenTaKu <dentaku(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dentaku(a)web.de --- Comment #8 from DenTaKu <dentaku(a)web.de> --- Same here with Wine 1.7.10 on Ubuntu 12.04 64 Bit and nVidia driver 319. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33436 Adam Bolte <abolte(a)systemsaviour.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte(a)systemsaviour.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.
http://bugs.winehq.org/show_bug.cgi?id=33436 --- Comment #9 from Adam Bolte <abolte(a)systemsaviour.com> --- I just finished Tomb Raider (with related 100% completion achievements) on 1.7.11 (with patches for bug #33125 and bug #35408), and I can confirm this bug also. NVIDIA GTX 660M, StrictDrawOrdering disabled, playing in fullscreen at native monitor res (1920x1080). Xfce 4.8 desktop (Debian wheezy) in case it's related. What seems to happen after a cutscene, or after closing a menu (such as the campfire menu or the map) is that the mouse cannot rotate completely any more. It's as if it's stuck in an invisible window, and it's hitting the edges of said window when you move the mouse too much in any direction. I think that's a more accurate description. However I never tried Alt+Return to fix it, as I could always get the mouse behaviour to return to normal simply by clicking a mouse button. Since left-clicking doesn't do anything in game without zooming first, I always just remembered to click whenever I anticipated the issue would appear. I want to point out that this behaviour is not unique to Tomb Raider. I don't recall all the games I've noticed it in, but I know Outlast was one of them. In a review of Outlast on Wine back on Dec 1st 2013 I wrote: "I did experience a Wine issue whereby the mouse would occasionally (usually after a cut-scene or climbing a ledge) appear to hit a virtual wall and would not turn the character past a certain point. This is solved by left-clicking, and is not an issue unique to Outlast. A minor annoyance, but worth noting." http://steamcommunity.com/id/boltronics/recommended/238320/ Lastly, I did also notice a mouse issue in the Tomb Raider main menu; occasionally the selected item would be the item underneath the one that the mouse was hovering over. I'm not sure if the problems are related since it only happened occasionally - whereas the one this bug report is about was consistently reproducible. -- 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=33436 sacrediou <vmerlet(a)april.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmerlet(a)april.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=33436 james stone <jamesmstone(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamesmstone(a)gmail.com --- Comment #10 from james stone <jamesmstone(a)gmail.com> --- This bug still present in Wine 1.7.28 -- 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=33436 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69(a)gmail.com, | |sebastian(a)fds-team.de --- Comment #11 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Based on comment #5 this is likely a dupe of bug #33479. You may want to try out the patch from wine-staging (no need to revert commit 76bbf106a28c4caa82873e8450bde7d4adc765bf): https://github.com/wine-compholio/wine-staging/blob/master/patches/server-Cl... -- 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=33436 n8bk <n8bk13(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |n8bk13(a)gmail.com --- Comment #12 from n8bk <n8bk13(a)gmail.com> --- For me neither the workaround patch (comment #2), nor the patch from comment #11 worked for Tomb Raider - the mouse cursor still seems to hang after reaching screen border. On the other hand the patch from comment #2 provided a workaround for Rome Total War bug, which doesn't allow to move cursor to command panel in battle map view in screen resolutions higher than 1152x864. Tested on wine 1.7.46 in Funtoo. -- 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=33436 --- Comment #13 from n8bk <n8bk13(a)gmail.com> --- Ok, my bad that I tested it on ebuild version. Now I built a git version of wine and installed Steam and Tomb Raider on clean wineprefix. As expected I couldn't fully rotate a camera, but after applying the patch (comment #11) problem was gone. -- 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=33436 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net, | |super_man(a)post.com --- Comment #14 from super_man(a)post.com --- (In reply to n8bk from comment #13)
Ok, my bad that I tested it on ebuild version. Now I built a git version of wine and installed Steam and Tomb Raider on clean wineprefix. As expected I couldn't fully rotate a camera, but after applying the patch (comment #11) problem was gone.
This is dupe and fixed then. -- 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=33436 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #15 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, resolving as dupe of bug 33479 Regards *** This bug has been marked as a duplicate of bug 33479 *** -- 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=33436 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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 (1)
-
wine-bugs＠winehq.org