[Bug 48943] New: assasins creed 2 (uplay) camera spinning with dualshock 4
https://bugs.winehq.org/show_bug.cgi?id=48943 Bug ID: 48943 Summary: assasins creed 2 (uplay) camera spinning with dualshock 4 Product: Wine Version: 5.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: animegirl(a)stronzi.org Distribution: --- Created attachment 66918 --> https://bugs.winehq.org/attachment.cgi?id=66918 log latest archlinux, latest wine-staging. -- 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=48943 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- Lutris is not supported in this bug tracker; please test with plain Wine-Staging or (ideally) upstream Wine. -- 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=48943 --- Comment #2 from Anya <animegirl(a)stronzi.org> --- i tested with plain wine-staging in lutris -- 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=48943 --- Comment #3 from Zebediah Figura <z.figura12(a)gmail.com> --- Does the bug occur in upstream (non-Staging) Wine? -- 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=48943 --- Comment #4 from Anya <animegirl(a)stronzi.org> --- Yes, same happens with mainline wine. -- 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=48943 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, With a bit of search I found this in the AppDB: --- quote The Legend of Heroes: Trails of Cold Steel --- If in-game camera starts constantly spinning, disable your gamepad (wine control or other means) or fix the button mapping (in my case with DualShock 4 - Rx,Ry (L2 and R2 buttons) and Z,Rz (right stick) axis were mixed up, as well as some other buttons, connecting the gamepad over Bluetooth with ds4drv fixed that) --- end quote --- https://appdb.winehq.org/objectManager.php?sClass=version&iId=35588&iTesting... Please run 'wine control' and check the configuration of your device. Regards. -- 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=48943 --- Comment #6 from Anya <animegirl(a)stronzi.org> --- Yes, button mapping is fucked up, by gamepad works fine with other games/apps, -- 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=48943 --- Comment #7 from Rafał Mużyło <galtgendo(a)o2.pl> --- Well, not relevant to this game, but *perhaps* relevant to the problem: 1. I've seen something similar with my gamepad in a different game where the game acts as if a direction was constantly pressed in the title screen, even though gamepad is only plugged in, not used at all 2. that gamepad is discovered as both js and event...but the mapping of axes (as shown by relevant 'wine control') differs between these two, which strikes me as not quite sane (because AFAIK I didn't do any extra calibrating/mapping for the pad) -- 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=48943 Rafał Mużyło <galtgendo(a)o2.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |galtgendo(a)o2.pl -- 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=48943 --- Comment #8 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Rafał Mużyło from comment #7)
Well, not relevant to this game, but *perhaps* relevant to the problem:
1. I've seen something similar with my gamepad in a different game where the game acts as if a direction was constantly pressed in the title screen, even though gamepad is only plugged in, not used at all 2. that gamepad is discovered as both js and event...but the mapping of axes (as shown by relevant 'wine control') differs between these two, which strikes me as not quite sane (because AFAIK I didn't do any extra calibrating/mapping for the pad)
Hello, I guess event and js device are handled by different code parts and they are treated as independent devices? When the device is not used in the application, the workaround is to disconnect it, but I understand that the OP wants to play the game with the gamepad? @OP, can you try disabling one of the device at a time in 'wine control': js and event for your gamepad, and see if it behaves better with one or the other? Regards. -- 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=48943 --- Comment #9 from Rafał Mużyło <galtgendo(a)o2.pl> --- (In reply to Olivier F. R. Dierick from comment #8)
I guess event and js device are handled by different code parts and they are treated as independent devices?
Of course they are. The thing is that they still should be using the same axes for the same pad presses is both paths.
When the device is not used in the application, the workaround is to disconnect it, but I understand that the OP wants to play the game with the gamepad?
Yeah, the *workaround*. The solution would be figuring out why the bogus events are produced in wine, even though: a) pad is not in physical use b) neither js nor event device is producing any events on its own - not according to native monitoring tools -- 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=48943 --- Comment #10 from Rafał Mużyło <galtgendo(a)o2.pl> --- Perhaps I should mention, that around wine 4.21 I've tried randomly poking driver_joyGetPosEx, but didn't get any positive effect. -- 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=48943 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #11 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, If the axis are incorrectly mapped, non-existent axis will emit bogus events, directly inside Wine. There are already multiple 'axis/button mapping is wrong' bugs: https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bu... Since nobody gave more detailed information on what happens in 'wine control' or when disconnecting the device, I assume that it's a mapping issue and will simply quote bug 29985 and mark duplicate: --- quote comment 1 from bug 29985 --- So you want to remap your axis? Take a look here under "DirectInput": http://wiki.winehq.org/UsefulRegistryKeys --- end of quote --- --- quote comment 5 from bug 29985 --- The bug is about Wine picking "wrong" mapping for your joystick. The workaround for it is to remap axis via registry. If you need help with that - ask forum. --- end of quote --- Regards. *** This bug has been marked as a duplicate of bug 29985 *** -- 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=48943 --- Comment #12 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...well, perhaps not that particular bugs, but sure - I'd be surprised it a true duplicate of this particular bug didn't exist. Yet... 1. Could a solution be found for wine to not randomly pick different *default* mappings of the same physical device only because it's a different logical device ? On one hand, I can see where that would sometimes be useful, on the other, it looks a bit too random. 2. The bogus events are almost certainly generated by wine. -- 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=48943 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #13 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate. -- 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)
-
WineHQ Bugzilla