-
Notifications
You must be signed in to change notification settings - Fork 75
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
Turbo A+B Seem to be Shifted onto Regular B [Regression] #237
Comments
Just checked on Linux. A works fine, B is meshed A+B turbo, and turbo A, turbo B, turbo R, and turbo L all fail to do anything. EDIT: Attempted to bisect, but due to the divergent state of the intermediate commits, that's just not viable. |
I noticed it acting weirdly with B first and kinda haphazardly tested A before opening this, so A is probably fine. Edit: Yeah, tested Aria of Sorrow and pressing and holding A jumps once as normal. |
Should be fixed now. |
I can confirm that my ability to violently twerk via button press in Harmony of Dissonance has been restored. Looks good now, thanks. |
Sorry about that, there was a merge conflict that I resolved wrong. |
The latest Win64 buildbot build (64f211c) has a problem where A and B seem to act as both Turbo A and Turbo B when pressed. The actual Turbo button inputs no longer do anything themselves, so it's like they were somehow shifted onto the regular A and B inputs. The previous build I have (c7dba6b) works properly.
The text was updated successfully, but these errors were encountered: