-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Controls broken in all games since v0.8.1-258-gc01a69d(new control merge) #2609
Comments
Yeah same here, my xperia play controls won't work anymore. |
Also, rebinding the buttons has no effect, the buttons never get remapped, and the GUI doesn't update to reflect any change. |
Yep, controls are absolutely broken since that #2573 pull request was merged into master. Rebinding does nothing. Keyboard controls and XInput controllers like my 360 controller are now broken. Completely. |
I was logging in just to report the same thing. Some of the buttons seem to do one thing, then stop doing anything all together, but the keys that move the analog stick seem to work (as far as I can tell) |
Yeah, something really broke. I'll fix it tomorrow. |
yeah cant play on galaxy s3 . |
If you can compile your own builds, use this branch as a temporary workaround: |
Keymap. Seems to have preconfigured keys, Though im able to play using the built in QWERTY keyboard on my Droid 3 It doesn't seem like it can change from key to key, especially if that key is in use. |
Bug confirmed also in Windows build. Latest build working v0.8.1-231-g5156f12. Not working on v0.8.1-264-g8b27f4e. |
I'm working on this. I must have broken the legacy input path. |
This should fix the issue: #2612 |
This should be fixed now. Sorry for breaking the build. |
Yep, it is. |
Closed, the issue has been fixed. |
As of c01a69d , The defaults do not work as expected; the majority of buttons simply do nothing, and only a few buttons that actually do anything can't allow the user to make a confirmation, making getting in-game, into any game, impossible.
Pull request originated here: #2573
The text was updated successfully, but these errors were encountered: