-
Notifications
You must be signed in to change notification settings - Fork 21
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
[Bug] Motion stick deadzone broken as of v3.5.0 #102
Comments
Same thing in v3.5.1 |
Thanks for the report. I'll look into it. |
I tested the virtual controller on hardware tester web page and played around with the settings and could observer everything working as expected in v3.5.1. The stick outputs 0-100 between angles 45 to 90. |
I see the confusion now, the issue isn't present when setting |
The release v3.5.0 has broken the
MOTION_DEADZONE_INNER
andMOTION_DEADZONE_OUTER
settings. Default values of 15 degrees inner deadzone and 135 degrees outer don't apply, and attempting to change the value manually doesn't affect the motion stick. It functions as if both deadzone settings are set to zero, so every input is accounted and the range of motion is 180 degrees to both sides.Works as expected in v3.4.0, the issue appeared only when updating to v3.5.0 (also ruled out any possible system failure as I've also tested it after reinstalling Windows lmao).
The text was updated successfully, but these errors were encountered: