https://bugs.winehq.org/show_bug.cgi?id=44751
Bug ID: 44751 Summary: In Ex Machina (Hard Truck Apocalypse) wheels are always turned to the left. Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: thatguyyoucannottrust@gmail.com Distribution: ---
Created attachment 60762 --> https://bugs.winehq.org/attachment.cgi?id=60762 Wheels are turned to the left.
Game works perfectly (especially compared to Windows 10, where I get 10fps and graphical glitches), but as soon as the gameplay starts, the wheels of the car turn to the left and stay in that position.
It's the same on all trucks and I don't know if there's a way to fix it.
Same game in Windows has no such problem.
https://bugs.winehq.org/show_bug.cgi?id=44751
--- Comment #1 from Eichhorn thatguyyoucannottrust@gmail.com --- The problem is the same in the sequel (Ex Machina: Меридиан 113).
https://bugs.winehq.org/show_bug.cgi?id=44751
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Could it be that a controller is plugged in that sends a wrong signal? That was always the case when I had this issue.
https://bugs.winehq.org/show_bug.cgi?id=44751
Eichhorn thatguyyoucannottrust@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED Distribution|--- |Other
--- Comment #3 from Eichhorn thatguyyoucannottrust@gmail.com --- (In reply to Fabian Maurer from comment #2)
Could it be that a controller is plugged in that sends a wrong signal? That was always the case when I had this issue.
Thanks for the pointer, I have found the problem!
If the mouse is connected when the game launches, there will be the problem. If I unplug the mouse and plug it in after `wine` starts, everything works as expected.
If that helps, I'm using `libinput`.
Since this may be my localized problem and not something to do with `wine`, I'd close the bug. Thanks again!
https://bugs.winehq.org/show_bug.cgi?id=44751
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=44751
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #5 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
https://bugs.winehq.org/show_bug.cgi?id=44751
--- Comment #6 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Eichhorn from comment #3)
Thanks for the pointer, I have found the problem!
If the mouse is connected when the game launches, there will be the problem. If I unplug the mouse and plug it in after `wine` starts, everything works as expected.
If that helps, I'm using `libinput`.
Since this may be my localized problem and not something to do with `wine`, I'd close the bug. Thanks again!
Is this still an issue? Can you test if the same happens with other applications?