https://bugs.winehq.org/show_bug.cgi?id=42631
Bug ID: 42631 Summary: 7 Days To Die mouse cursor wrongly move to bottom right Product: Wine Version: 2.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: tim110011@163.com Distribution: ---
The game works fine under windows system.
When moving mouse slowly, cursor wrongly move to bottom right.
Set mouse sensitivity to 1.00 make this problem more obvious.
System: Fedora 25 x64 Xfce Desktop kernel 4.9.13 nvidia Geforce gtx 750Ti nvidia 1.375.26 Driver wine 2.3
This problem alse exist in wine 1.9.12 https://appdb.winehq.org/objectManager.php?sClass=version&iId=29521&...
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #1 from tim110011@163.com --- This problem also exist in wine 1.7.27
Bug 42644: "click with either mouse button game cursor moves torwards the right bottom of the screen" also exist
https://bugs.winehq.org/show_bug.cgi?id=42644
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #2 from tim110011@163.com --- When moving mouse slowly to upper left or click mouse button, cursor wrongly move to bottom right. This problem and Bug 42644 also exist in wine 2.4, no dll override.
https://bugs.winehq.org/show_bug.cgi?id=42631
eutychios23@gmail.com eutychios23@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eutychios23@gmail.com
--- Comment #3 from eutychios23@gmail.com eutychios23@gmail.com --- how do we get this confirmed?it also happens when you enable the in-game opengl renderer.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #4 from eutychios23@gmail.com eutychios23@gmail.com --- i meant even instead of also.
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |major
--- Comment #5 from tim110011@163.com --- Also see Bug 42717. It seems this bug exist in every Unity3D game. Raised importance from normal to major. This bug also exist in wine 4.5
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #6 from tim110011@163.com --- Sorry for my typo, this bug also exist in wine 2.5
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #7 from eutychios23@gmail.com eutychios23@gmail.com --- good maybe some moderator will confirm it as a duplicate,it is a very annoying bug.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #8 from eutychios23@gmail.com eutychios23@gmail.com --- *** Bug 42644 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=42631
Karl Morrison basickarl@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |basickarl@gmail.com
--- Comment #9 from Karl Morrison basickarl@gmail.com --- Bug also affecting me.
PlayOnLinux 4.2.2
Distributor ID: elementary OS Description: elementary OS Freya Release: 0.3.2 Codename: freya
Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty
4.4.0-78-generic
nvidia-340 driver
wine 1.6.2
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #10 from Karl Morrison basickarl@gmail.com --- https://issuetracker.unity3d.com/issues/screen-dot-lockcursor-under-linux-br...
If you read the following link above it states, quote:
"I just found something which should've been obvious; if you're still experiencing this problem in October 2015 and it's related to the mouse acting strange when using lockCursor, keep in mind that lockCursor is in fact obsolete and the docs suggest using Cursor.lockState instead."
Perhaps something to look into.
https://bugs.winehq.org/show_bug.cgi?id=42631
Gijs Vermeulen acescopezz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |acescopezz@gmail.com
--- Comment #11 from Gijs Vermeulen acescopezz@gmail.com --- (In reply to Karl Morrison from comment #10)
-snip-
You are using an ancient Wine version, can you upgrade to 2.9?
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #12 from eutychios23@gmail.com eutychios23@gmail.com --- Happens with wine 2.8 and 2.8-staging i checked
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #13 from Karl Morrison basickarl@gmail.com --- Actually this can be closed. 7 Days To Die officially supports Linux now. Just install it via Steam on Linux.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #14 from eutychios23@gmail.com eutychios23@gmail.com --- It is not just about 7 days to die its a wine bug that affects many games.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #15 from eutychios23@gmail.com eutychios23@gmail.com --- Check https://bugs.winehq.org/show_bug.cgi?id=42872 it affects all unity games.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #16 from eutychios23@gmail.com eutychios23@gmail.com --- Actually tim110011@163.com i suggest you merge it with https://bugs.winehq.org/show_bug.cgi?id=42872 .
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #17 from Karl Morrison basickarl@gmail.com --- I agree, it is still a problem, however it is not a problem related to 7 Days To Die. Perhaps open an issue on Wine in general relating to this issue and close this one (as it sits in the 7 days to die area).
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #18 from Karl Morrison basickarl@gmail.com --- Or perhaps just rename the title of the thread (And remove "7 days to die") to include the unity engine.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #19 from eutychios23@gmail.com eutychios23@gmail.com --- tim110011@163.com has to do it its his bug report.
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|7 Days To Die mouse cursor |Strange mouse movement in |wrongly move to bottom |many 3D games, every game |right |that using the Unity-engine | |is affected with this bug
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tim110011@163.com
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Fedora See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=42717
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=42872
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #20 from tim110011@163.com --- This bug was initially reported as a normal bug, only affecting game "7 Days to Die".
Now this bug affects every Unity-enging game, and even some other-engine 3D games like FalloutNV.https://bugs.winehq.org/show_bug.cgi?id=42872
It is likely this bug also caus Fallout4 camera drift.
"Moving mouse, clicking left or right mouse button, scrolling mouse wheel or clicking mouse wheel", cause mouse cursor move to bottom right of screen, it feels like drift or +1px.
Someone think this bug relate to joystick, someone think this is a unfixed Unity3D "upstream bug". I suspect there is something wrong in mouse signal handle code. Are there something like this? MOUSEPOS_X = MOUSESIG_X+1; MOUSEPOS_Y = MOUSESIG_Y+1;
Linux native port of "7 Days to Die" is not affected by this bug. (It suffers from 3 other bugs: random crash or guaranteed crash or frequently crash)
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=37151
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=36565
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=33758
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=37995
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=32913
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|Fedora |---
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #21 from tim110011@163.com --- Clearly, it is camera focus drifting, not mouse cursor.
This bug also affect Fallout 4. After cleared vanilla mouse button behavior in game setting: Moving mouse, clicking left or right mouse button, clicking mouse wheel cause camera focus ghostly drift. Lower view sensitivity setting make this problem more obvious.
Tested with: Fedora 25 x64 Xfce Desktop kernel 4.11.3 nvidia Geforce GTX 750Ti nvidia 375.66 Driver plain wine 2.10
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Strange mouse movement in |Mouse input cause camera |many 3D games, every game |drift in multiple games: |that using the Unity-engine |Unity-engine games, |is affected with this bug |Fallout4, etc
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #22 from eutychios23@gmail.com eutychios23@gmail.com --- OMG its everywhere!!!
https://bugs.winehq.org/show_bug.cgi?id=42631
Eric Culp eculperic@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eculperic@gmail.com
--- Comment #23 from Eric Culp eculperic@gmail.com --- Created attachment 58414 --> https://bugs.winehq.org/attachment.cgi?id=58414 Patch to fix mouse drift
I'm not sure why this happens, but there is a (1, 1) pixel diff even when the mouse doesn't move. I made a patch that just subtracts (1, 1) from the mouse coords in dinput.dll. This fixed the issue in the game I experienced the bug in, but I don't know if it introduces bugs elsewhere. Presumably there is a bug elsewhere that is introducing this (1, 1) diff.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #24 from Eric Culp eculperic@gmail.com --- After some more testing, the above patch appears to introduce the opposite bug sometimes (drifting to the top left). However, just clicking the mouse no longer causes any movement.
Someone more familiar to the code would have an easier time fixing this issue. There are many layers of indirection and almost no comments, so it's difficult for a newcomer to discover why the code exists, why it does what it does, and where its data comes from (doubly so if you aren't very familiar with windows apis like me).
In particular about this code, if the input MSLLHOOKSTRUCT has a point included in it (hook->pt), why does it call GetCursor to get another point? Why aren't they trivially equal? If it needs to return relative movements, can't it subtract from m_state->lX and m_state->lY?
https://bugs.winehq.org/show_bug.cgi?id=42631
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #25 from Sebastian Lackner sebastian@fds-team.de --- Could you please check if this is a duplicate of bug 38791? I have added a staged patchset in Wine Staging 2.10.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #26 from eutychios23@gmail.com eutychios23@gmail.com --- Will test with wine 2.10-staging once it is available in my distro(prob a couple of days) and report back.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #27 from eutychios23@gmail.com eutychios23@gmail.com --- Still happens with wine staging 2.10, but the only game i have to test is 7days2die windows version.
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=38791
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #28 from tim110011@163.com --- Still drift in Fallout4 with wine 2.10-staging. Unlike "+1xpx AND +1ypx" feeling in 7 Days to Die, Fallout4 drift like "+nxpx OR +nypx" depended by the direction of which 3D-surface youre looking at.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #29 from Eric Culp eculperic@gmail.com --- I'm pretty sure this is a duplicate of 38791. I added logging to the clipping functions in server/queue.c and it is indeed attempting to clip on a rect where top==bottom and left==right. If I apply that patch, it fixes the issue completely (at least for Darkfall Rise of Agon, which is the game I was reproducing with).
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #30 from Eric Culp eculperic@gmail.com --- Also, the patch in wine staging (https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-Cl...) only fixes 1 clipping issue, while the patch in bug 38791 fixes 2 clipping issues, so if wine-staging didn't fix it, you could try patching it yourself with the version from the bug.
https://bugs.winehq.org/show_bug.cgi?id=42631
faalagorn@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |faalagorn@gmail.com
--- Comment #31 from faalagorn@gmail.com --- Since like other mentioned, this is most likely a duplicate of both Bug 42717 Bug 42872 (and duplicated Bug 42644), I will be posting only here form now on, since it's the oldest and probably most details bug report) (the rest should be marked as duplicate after confirming it's the same bug IMO).
I also was hoping that fixes in wine-staging 2.10 (from what I understand from Bug 38791) would fix it for Unity games, but unfortunately I can confirm it still exist in Escape from Tarkov after trying it today. I can check My Summer Car and Jalopy later, but it EfT it seems the same sadly.
From all the reports, it seems that the bug exists in Fallout: New Vegas and
Fallout 4 as well, can someone confirm it's the same issues being dealt with? If so, can someone confirm the bug does not appear in other Bethesda games based on similar engines, like Skyrim (regular and enhanced), Fallout 3 or Oblivion? I may test that later if the need arise.
Hopefully, the patches from wine-staging 2.10 are a start to nailing down this issue, eventually fixing it altogether :).
https://bugs.winehq.org/show_bug.cgi?id=42631
bellamorte42@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bellamorte42@gmail.com
--- Comment #32 from bellamorte42@gmail.com --- How the hell is this still an issue? Yes it exists, and in more games than Fallout. When moving the mouse there is a constant pull to the lower right. Or if you play inverted like I do, to the upper right.
https://bugs.winehq.org/show_bug.cgi?id=42631
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #33 from winetest@luukku.com --- bug 31839 is most likely about the same issue.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #34 from tim110011@163.com --- (In reply to winetest from comment #33)
bug 31839 is most likely about the same issue.
I don't think so, it seems like the game initialize mouse cursor position to (0,0) , that bug seems relate to wine-directx/opengl renderer. When i play Diablo 3, i didn't notice any camera drifting issue caused by mouse input.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #35 from bellamorte42@gmail.com --- As an added piece of information. When in game in a 'mouse mode' (navigating menus, etc) the mouse moves as expected. But in 'control modes' either first or third person the problem occurs.
https://bugs.winehq.org/show_bug.cgi?id=42631
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #36 from eutychios23@gmail.com eutychios23@gmail.com --- Fixed for me in 7 days to die (windows) with wine 2.11-staging!!!
https://bugs.winehq.org/show_bug.cgi?id=42631
cetedus@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cetedus@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #37 from tim110011@163.com --- Wine 2.11-staging fixes 7 Days to Die ( tested game version: 15.2b8 ). Camera in Fallout4 is still out of control, maybe it's another bug? FalloutNV is not affected by this bug ( tested with wine 2.10-staging ).
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #38 from eutychios23@gmail.com eutychios23@gmail.com --- Also tested my summer car it is fixed with wine 2.11-staging,maybe fallout is a totally different bug
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #39 from winetest@luukku.com --- (In reply to eutychios23@gmail.com from comment #38)
Also tested my summer car it is fixed with wine 2.11-staging,maybe fallout is a totally different bug
Could you also comment on bug 42717? I would suggest merging that bug since it seems to be duplicate issue.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #40 from eutychios23@gmail.com eutychios23@gmail.com --- So the bug related to unity engines is resolved? Is Fallout 4 built with unity engine?
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #41 from eutychios23@gmail.com eutychios23@gmail.com --- Fallout 4 uses Bethesda's Creation Engine, so i believe it is 90% sure, that the bug related to Fallout 4 is totally different and needs a separate bug entry.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #42 from tim110011@163.com --- Still exist in Fallout 4 with wine-2.13-Staging.
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=43443
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #43 from tim110011@163.com --- See also Bug 43443, this bug requires further investigation.
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=27156
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #44 from tim110011@163.com --- See also Bug 27156, old mouse jumps bug revived?
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=27255
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=27455
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=30068
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=14074
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #45 from tim110011@163.com --- Further investigation with fallout4:
Camera reset/recoil is caused by Enable "Automatically capture the mouse in full-screen windows" setting in winecfg
Camera drift is caused by click/release left/right mouse button or scroll mouse wheel up/down, only after (enough) mouse movement. Click/release mouse wheel will not drift. Camera drift direction is same with previous mouse movement direction, drift speed is determined by previous mouse movement speed. It gives me "accumulated drift/sudden speed up" feeling.
while (mouse_move) { if (mouse_move_whatever_direction > threshold && mouse_signal) { drift_direction = mouse_move_current_direction; drift_speed = mouse_move_speed; do_drift_or_sudden_speed_up; } }
kernel: 4.12.13-300.fc26.x86_64 (Fedora26 Xfce) wine: 2.17-staging CPU: Intel Pentium G3420 mainboard: Gigabyte B85M-D2V Video Card: nVidia Geforce GTX750 Ti Video Driver: nVidia 375.66
setting: Disable: 'Allow the window manager to decorate the windows' Disable: 'Allow the window manager to control the windows' Enable: 'Emulate a virtual desktop 1920x1080'
dll override: use winetricks install: xact
This is a wine bug or xorg bug?
https://bugs.winehq.org/show_bug.cgi?id=42631
Karl Morrison basickarl@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|basickarl@gmail.com |
https://bugs.winehq.org/show_bug.cgi?id=42631
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
https://bugs.winehq.org/show_bug.cgi?id=42631
bugzilla@biechl.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla@biechl.net
--- Comment #46 from bugzilla@biechl.net --- Created attachment 59398 --> https://bugs.winehq.org/attachment.cgi?id=59398 Cursor trace of Fallout4
wine2.8+staging WINEDEBUG=-all,+event,+cursor for upper part, WINEDEBUG=-all,+dinput,+cursor for lower Game in fullscreen (1280x720) Xubuntu 16.04 AMD R290X using Mesa 17.2.2-0 (padoka stable repo) 3 Monitors (no difference in the logs, when I deactivate 2 of them within the OS) No DLL overrides
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #47 from bugzilla@biechl.net --- (In reply to bugzilla from comment #46)
Created attachment 59398 [details] Cursor trace of Fallout4
wine2.8+staging WINEDEBUG=-all,+event,+cursor for upper part, WINEDEBUG=-all,+dinput,+cursor for lower Game in fullscreen (1280x720) Xubuntu 16.04 AMD R290X using Mesa 17.2.2-0 (padoka stable repo) 3 Monitors (no difference in the logs, when I deactivate 2 of them within the OS) No DLL overrides
I don't think this bug is related to Fallout4 - we might need to file a new bug report - but I'll leave this here for now:
I don't know much about the internals of wine and windows, but I've tried to trace the problem a bit, here is what I've come up with:
see attachment: fallout4_cursor-trace.log - Part 1
In the last 4 lines there is again a rather big jump on the x-axis: from 183 to 0. Prior to the jump there is a ConfigureNotify, which isn't there in the previous lines. Also the event id changed from 4449 to 4450. I can see this all over my logs when I'm in 3D camera mode. This does not occur when being in any sort menu.
Also there is something strange with the clipping, don't know if this is normal or not: (WINEDEBUG=-all,+dinput,+cursor), different log.
see attachment: fallout4_cursor-trace.log - Part 2
It first clips with the correct window size (1280,720), then it does another clipping, but with a different window size. "trace:cursor:grab_clipping_window Clip window shrinked" is an added debug output by me, as well as " | clip_rect: (X,Y)-(X2,Y2)".
I'll do a full trace later this day, but this might be of help already?
https://bugs.winehq.org/show_bug.cgi?id=42631
bugzilla@biechl.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #59398|0 |1 is obsolete| |
--- Comment #48 from bugzilla@biechl.net --- Created attachment 59399 --> https://bugs.winehq.org/attachment.cgi?id=59399 Cursor trace of Fallout4
https://bugs.winehq.org/show_bug.cgi?id=42631
unsuspicious.fakename+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |unsuspicious.fakename+wine@ | |gmail.com
--- Comment #49 from unsuspicious.fakename+wine@gmail.com --- Yes, the Fallout input problems look weird / different to me too:
For some people, alt+tabbing out of the (Fallout 4) window or moving it to a different virtual Desktop appears to solve the issue temporarily.
While messing around with alt+tab and holding / releasing keys and mouse buttons in different windows (p.E. pushing button(s) in and releasing them outside the game), I didn't manage to get the mouse fixed, but I DID manage to break it more:
The middle mouse button and ESC key switched functions in the game. ( Also, <tab> in game stopped working and possibly more weird stuff. )
Once they were switched that way, they stayed that way until I alt+tabbed + clicked around more. While I couldn't figure out how exactly it happens, I managed to reproduce it several times (restarted X between attempts).
The feel of this together with the sudden, jerky / big mouse movements (if they are related) makes me thing that the "fallout 4 mouse drift" might not be that much of a "drift" (as seen in other games)... but more of a... "totally messed up input events, even from different sources" sort of bug (Unless those observations are totally unrelated).
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mouse input cause camera |Mouse input cause camera |drift in multiple games: |drift or jump in multiple |Unity-engine games, |games: Unity-engine games, |Fallout4, etc |Fallout4, etc
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mouse input cause camera |Mouse input cause camera |drift or jump in multiple |drift or jump in multiple |games: Unity-engine games, |DX11 and Unity-engine games |Fallout4, etc |( fixed in Unity-engine | |part )
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=43602
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mouse input cause camera |Mouse input cause camera |drift or jump in multiple |drift or jump in Fallout 4 |DX11 and Unity-engine games |and Unity-engine games ( |( fixed in Unity-engine |fixed in Unity-engine part |part ) |)
https://bugs.winehq.org/show_bug.cgi?id=42631
Thomas winehq@spam.b2ag.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@spam.b2ag.de
--- Comment #50 from Thomas winehq@spam.b2ag.de --- Hi,
I found a workaround for the mouse issue for Fallout4 by setting "bBackgroundMouse=1" in the controls section of "Fallout4.ini". I was inspired by the this link: wiki.step-project.com/Guide:Skyrim_INI/Controls#bBackgroundMouse which states the engine skrewing up "some actions" in default mouse handling. I also have "Automatically capture the mouse in full-screen windows" (and "Emulate virtual desktop", if that matters) enabled in wine configuration. No jumping camera in Fallout 4 anymore.
Have fun!
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mouse input cause camera |Mouse input cause camera |drift or jump in Fallout 4 |drift or jump in Fallout 4 |and Unity-engine games ( |and Unity-engine games ( |fixed in Unity-engine part |fixed in Unity-engine |) |games, have walkaround in | |Fallout4 )
https://bugs.winehq.org/show_bug.cgi?id=42631
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=42631
Freso bugs.winehq.org@freso.dk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.winehq.org@freso.dk
https://bugs.winehq.org/show_bug.cgi?id=42631
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=44193
https://bugs.winehq.org/show_bug.cgi?id=42631
tim110011@163.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mouse input cause camera |Mouse drift, jump or don't |drift or jump in Fallout 4 |react to small slow |and Unity-engine games ( |movements in Unity-engine |fixed in Unity-engine |games and Fallout 4 (partly |games, have walkaround in |fixed in Unity games, have |Fallout4 ) |walkaround in Fallout4 )
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #51 from tim110011@163.com --- I changed bug title, added "mouse didn't react to small, slow movements"
according to: https://bugs.winehq.org/show_bug.cgi?id=44193 https://forum.winehq.org/viewtopic.php?f=2&t=30864
Bug44193 do exist in wine-2.3. Maybe wine-2.11-staging is a partly fix or there is a regression: when wine-staging-2.11 come out, i tested it carefully in '7 Days to Die'. @Rencer
About the Fallout 4 walkaround: Some old 3d game offer 2 method to handle mouse: "directx mode and hardware mode". It seem the walkaround just force game run on one unbugged mode.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #52 from tim110011@163.com --- Retested with wine-staging-2.11 and wine-staging-3.12:
Game: 7 Days to Die
Result: Fix in staging-2.11 is not a complete fix, low speed mouse movement jumps (very short distant).
How to reproduce: Compare native linux and windows-wine game behavior: "Go to stealth and use that closed eye cursor draw a circle slowly."
Hardware: nvidia geforce gtx 750ti nvidia 390.59
https://bugs.winehq.org/show_bug.cgi?id=42631
Jordan Galby gravemind2a@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gravemind2a@gmail.com
--- Comment #53 from Jordan Galby gravemind2a@gmail.com --- Created attachment 62126 --> https://bugs.winehq.org/attachment.cgi?id=62126 Fix sub pixel raw motion
I had the issue on the Witcher 3, getting slow mouse movement unregistered and hitting seemingly random "walls". I found it came from wine receiving "fractions"/"sub-pixel" mouse motion (motion >0.0 but <1.0). The cause is probably my high dpi mouse that I setup with 'libinput Accel Speed' to "-0.5" (same as xorg.conf "AccelSpeed").
I made this patch on wine-3.14: it accumulates those "sub-pixel" motion and sends to windows when there is a "full pixels" motions (because it does not handle fractions; movements <1.0 are truncated to 0, so ignored).
This is my first patch, so probably not perfect.
Also, this bug could be related and fixed with the patch: https://bugs.winehq.org/show_bug.cgi?id=43794
https://bugs.winehq.org/show_bug.cgi?id=42631
Jordan Galby gravemind2a+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #62126|0 |1 is obsolete| |
--- Comment #54 from Jordan Galby gravemind2a+wine@gmail.com --- Created attachment 62138 --> https://bugs.winehq.org/attachment.cgi?id=62138 Fix sub pixel raw motion v2
My last patch "Fix sub pixel raw motion" had a potential regression, this "v2" is better (and simpler).
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #55 from tim110011@163.com --- Tested 7 Days to Die on wine-staging-3.14 with "Fix sub pixel raw motion v2": It seems mouse movement is fixed. I am using a normal mouse, anyone test this patch with a high dpi mouse?
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #56 from Henri Verbeet hverbeet@gmail.com --- While I haven't reviewed the patch in detail, and you wouldn't want to have e.g. C99 comments in there, it does make sense to me conceptually.
https://bugs.winehq.org/show_bug.cgi?id=42631
Jordan Galby gravemind2a+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #62138|0 |1 is obsolete| |
--- Comment #57 from Jordan Galby gravemind2a+wine@gmail.com --- Created attachment 62161 --> https://bugs.winehq.org/attachment.cgi?id=62161 Fix sub pixel raw motion v3
I fixed it to C99 comments (sorry), and tweaked them to describe a bit more "why" than "how". I guess it would be wiser to consider it as a POC rather than a "submittable fix" for now. For example: - I'm wondering if there could be a better place for `double accum;` ? - should `accum` be initialized to `0` or the current pixel fraction of the absolute position ? - is there a windows API that can handle sub-pixel mouse motion ? (or mouse dpi ?) - etc... (I hope here is the good place to post all this)
The issue I tried to fix was that X11's "raw motion" can be fractions (eg 0.2 px, depending on mouse dpi and AccelSpeed), but windows' INPUT's are LONG, and the code implicitly casted X11's double to LONG. The result was that slow mouse motion were cast to 0.
In The Witcher 3, My **guess** was that everything was fine as long as the game could use absolute mouse position, but as soon as the position went outside the screen (getting clamped (?)) the game seemed to switch to using relative mouse motion (RawMotion) and suddenly slow mouse motion got blocked/ignored (if you moved slow enough then, you'd hit a "seemingly random wall").
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #58 from Henri Verbeet hverbeet@gmail.com --- (In reply to Jordan Galby from comment #57)
Created attachment 62161 [details] Fix sub pixel raw motion v3
I fixed it to C99 comments (sorry), and tweaked them to describe a bit more "why" than "how". I guess it would be wiser to consider it as a POC rather than a "submittable fix" for now. For example:
- I'm wondering if there could be a better place for `double accum;` ?
Putting it in struct x11drv_valuator_data doesn't seem wrong to me.
- should `accum` be initialized to `0` or the current pixel fraction of the
absolute position ?
You could probably make a good argument for using the current fraction. I'm not sure whether it would really matter in practice though.
- is there a windows API that can handle sub-pixel mouse motion ? (or mouse
dpi ?)
Rawinput (WM_INPUT) is supposed to report unscaled/unfiltered values, so wouldn't need to report fractional values. I'm not aware of any API that reports fractional values on Windows. Ultimately, I think mouse input should go through the HID layer, but I wouldn't expect that to happen very soon.
https://bugs.winehq.org/show_bug.cgi?id=42631
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |STAGED Ever confirmed|0 |1 Staged patchset| |https://github.com/wine-sta | |ging/wine-staging/tree/mast | |er/patches/winex11-mouse-mo | |vements CC| |leslie_alistair@hotmail.com
https://bugs.winehq.org/show_bug.cgi?id=42631
Adam Goode adam@spicenitz.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adam@spicenitz.org
https://bugs.winehq.org/show_bug.cgi?id=42631
alasky@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alasky@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=42631
winebugs@c2.hu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugs@c2.hu
--- Comment #59 from winebugs@c2.hu --- System: Manjaro Linux 18.0.0 Kernel: 4.19.6-1 Wine: wine-3.21-114-g1582ae6b04 64bit (build from source with the v3 patch)
I still have problems in a Unity-engine based game, namely Planet Explorers.
First I installed the standard Wine version from the Community repository. (Not a fresh install, but it is updated to the latest) When I installed the game and played with it, I very disappointed to see all the mouse drifting related bugs, that are fixed in the Wine-staging 2.11 version are there again! Hmmm... I uninstalled this version using pacman and deleted the leftover config and other files.
First, I think I have to tell you guys all the procedures what and how I done, because this is the first time that I applied patch to a sourcecode and compiled that patched code. So there is a possibility that I done something wrong...
So, I find this post and see that there is patch to fix this issue. I downloaded the Wine sourcecode, applied the V3 patch and compiled, installed it, followed instructions that I find scattered around the web.
First attempt is a total failure. Because when I run the game I find out the game doesn't even start. It turned out because the game required a 64-bit Wine to be installed. It took hours(!!!) on my laptop with a corei5 processor and 4GB RAM to compile the source...This is my bad, I know...
So, I uninstalled this 32bit installation, poked through my HDD to remove every bit of config files and stuff, that are made by this install.
I started again, and this is the exact steps that I done: (I wrote this down in a text file, so next time I don't have to search for it.)
* git clone https://github.com/wine-mirror/wine.git
Than I downloaded the V3 patch, saved it in the "wine" folder that created when getting the source, and run this command:
* patch -p1 < fix_mouse_sub_pix_raw_motion_v3.patch
It returned the following lines:
patching file dlls/winex11.drv/mouse.c Hunk #3 succeeded at 1773 (offset -1 lines). patching file dlls/winex11.drv/x11drv.h
Than I compiled and installed:
* ./configure --enable-win64 * make * sudo make install
And after hours of compiling when it finished insatlling Wine, I installed winetricks from source too. The game needs the corefonts to be installed and the only way that I know how to insatll those fonts is using winetricks.
This is the steps how I installed winetricks, find the instructions online. I made a folder, cd into that folder, than this commands:
* wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetrick... * chmod +x winetricks * sudo mv winetricks /usr/local/bin * wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetrick... * sudo mv winetricks.bash-completion /usr/share/bash-completion/completions/winetricks * chmod +x /usr/local/bin/update_winetricks.sh
The game runs fine, except all those mouse drifting that is (supposed to be) fixed in that earlier Wine-staging 2.11 version, are there again. The mouse drifts to bottom-right when moving it slowly and it also jumps a little bit to bottom-right every time when clicking with the mouse.
I tried it with 2 different mouse:
Gigabyte GM-M5100 (It is 800 DPI.) https://www.gigabyte.com/Mouse/M5100#ov
And Trust GXT 25 (It is 2000 DPI.) https://www.trust.com/en/product/18307-gxt-25-gaming-mouse
The mouse drift is there with both of them. The Trust mouse has a button to change the DPI, I tried all, but the mouse drift is there in every possible resolution.
Am I applied the patch and compiled Wine in the right way or I messed up something, or the patch really doesn't work?
https://bugs.winehq.org/show_bug.cgi?id=42631
Matthieu M morel.mat@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |morel.mat@gmail.com
--- Comment #60 from Matthieu M morel.mat@gmail.com --- Same issue with the game "Return Of The Obra Dinn - GOG"
System : Linux Mindt 19 Tara Kernel : 4.45.0.43-generic NVIDIA Driver Version: 415.22 Wine version : 415.22
https://bugs.winehq.org/show_bug.cgi?id=42631
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #61 from joaopa jeremielapuree@yahoo.fr --- Does the patch at comment 57 fix your problem?
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #62 from Matthieu M morel.mat@gmail.com --- Nope...It seems to still not work with the "Fix sub pixel raw motion v3"
I an not an expert in compiling, so here is what I have done3, like wrote. ----------------------- 1) Downloaded the archive containing the source of Wine4.0 RC3, and extracted it in a folder 2) Applied the patch with the command (with the file placed in the folder where the source have been freshly extracted):
patch -p1 < fix_mouse_sub_pix_raw_motion_v3.patch
It returned the following lines:
patching file dlls/winex11.drv/mouse.c Hunk #3 succeeded at 1773 (offset -1 lines). patching file dlls/winex11.drv/x11drv.h
3) I compiled it with the missing libraries : *libhal 64-bit development files *vkd3d 64-bit development files
and installed with the commands:
./configure --enable-win64 make sudo make install ----------------------- When trying to execute this freshly compiled Wine in its folder ("./wine /path/where/the/game/is/ObraDinn.exe"), it says "is a 32-bit installation, it cannot support 64-bit applications"... And if I launch the game as I usually do (with the command : "wine ObraDinn.exe"),the game works but the mouse still drifts...
I imagine I did something wrong with the compilation, as I saw that it is a bit tricky on the wiki page : https://wiki.winehq.org/Building_Wine
I will try things if I have spare time, but if somebody have a "ready to use" solution, I am interested.
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #63 from Matthieu M morel.mat@gmail.com --- OK!
I found a solution to my problem :
I used the "wine staging 3.9" version, which is very easy to install with lutris. Now it works, and with quite no effort.
Hoping this info will help.
https://bugs.winehq.org/show_bug.cgi?id=42631
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|gijsvrm@gmail.com |
https://bugs.winehq.org/show_bug.cgi?id=42631
Robert Walker bob.mt.wya@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bob.mt.wya@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=42631
Andrew Eikum aeikum@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aeikum@codeweavers.com
--- Comment #64 from Andrew Eikum aeikum@codeweavers.com --- The fix for the mouse drifting to the bottom-right has been accepted into Wine.
commit 5ff6a116972089f8e112dd4234d57689a60ab4dc Author: Sebastian Lackner sebastian@fds-team.de Date: Mon Feb 18 08:26:11 2019 -0600
server: Improve handling of cursor position clipping for empty rectangle.
https://bugs.winehq.org/show_bug.cgi?id=42631
Johan Gardhage johan.gardhage@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |johan.gardhage@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=42631
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Staged patchset|https://github.com/wine-sta |https://github.com/wine-sta |ging/wine-staging/tree/mast |ging/wine-staging/tree/mast |er/patches/winex11-mouse-mo |er/patches/user32-rawinput |vements |
https://bugs.winehq.org/show_bug.cgi?id=42631
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Staged patchset|https://github.com/wine-sta |https://github.com/wine-sta |ging/wine-staging/tree/mast |ging/wine-staging/tree/mast |er/patches/user32-rawinput |er/patches/user32-rawinput- | |mouse
https://bugs.winehq.org/show_bug.cgi?id=42631
Alex Xu alex_y_xu@yahoo.ca changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |49056
https://bugs.winehq.org/show_bug.cgi?id=42631
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Depends on|49056 |
https://bugs.winehq.org/show_bug.cgi?id=42631
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |znggurj+wine@gmail.com
--- Comment #65 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- *** Bug 42717 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=42631
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.winehq.org/sho | |w_bug.cgi?id=42717 |
https://bugs.winehq.org/show_bug.cgi?id=42631
tinfun@tutanota.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tinfun@tutanota.com
--- Comment #66 from tinfun@tutanota.com --- (In reply to tim110011 from comment #0)
The game works fine under windows system.
When moving mouse slowly, cursor wrongly move to bottom right.
Set mouse sensitivity to 1.00 make this problem more obvious.
System: Fedora 25 x64 Xfce Desktop kernel 4.9.13 nvidia Geforce gtx 750Ti nvidia 1.375.26 Driver wine 2.3
This problem alse exist in wine 1.9.12 https://appdb.winehq.org/objectManager. php?sClass=version&iId=29521&iTestingId=94081
alright let's see but don't count on it yet <a href="https://www.007.com/">James Bond</a>
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #67 from tinfun@tutanota.com --- Yea I mean it could work if you do Unity3D with this bug. But then again what's the point when you can just do https://www.pavingcompanyvaughan.com/
https://bugs.winehq.org/show_bug.cgi?id=42631
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #68 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 69777 --> https://bugs.winehq.org/attachment.cgi?id=69777 Updated patch for Wine 6.6
Updating the user32-rawinput-mouse wine-staging patch for Wine 6.6. This now depends on the HID series, attached to https://bugs.winehq.org/show_bug.cgi?id=50506 instead of the other way around.
https://bugs.winehq.org/show_bug.cgi?id=42631
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #69777|0 |1 is obsolete| |
--- Comment #69 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 69805 --> https://bugs.winehq.org/attachment.cgi?id=69805 Updated patch for Wine 6.6 (bis)
A quick fix for https://bugs.winehq.org/show_bug.cgi?id=50969, restoring some code that was dropped in the rebase, and making explorer.exe listen again to raw motion events.
https://bugs.winehq.org/show_bug.cgi?id=42631
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #69805|0 |1 is obsolete| |
--- Comment #70 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 70033 --> https://bugs.winehq.org/attachment.cgi?id=70033 Updated patch for Wine 6.9
Updating the series for Wine 6.9 (still needs the hid patches too)
https://bugs.winehq.org/show_bug.cgi?id=42631
Julian Rüger jr98@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jr98@gmx.net
https://bugs.winehq.org/show_bug.cgi?id=42631
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=38420
--- Comment #71 from Rémi Bernon rbernon@codeweavers.com --- The mouse not reacting to slow movements is probably better tracked in https://bugs.winehq.org/show_bug.cgi?id=38420
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #72 from Rémi Bernon rbernon@codeweavers.com --- Created attachment 70904 --> https://bugs.winehq.org/attachment.cgi?id=70904 Updated patch for Wine 6.21
Attaching an update now that some patches got upstream.
https://bugs.winehq.org/show_bug.cgi?id=42631
Neko-san nekoNexus@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nekoNexus@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #73 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
The staged patchset user32-rawinput-mouse introduces the issue reported in bug 49667.
Regards.