-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Wrong inputs when controller is set to no SODC cleaning. #2
Comments
Thanks for the feedback. I just got a leverless stick with UFB, I will add a SOCD cleaning option and fix the display |
@Chinta03 I just fixed it. You can test in the latest release. Note I probably should evolve the view for |
Hey @lucasteles,
I am using a Universal Fighting Board Fusion, set to Controller (XInput STANDARD GAMEPAD) mode. SODC in the InputDisplay Config to SOCD: Neutral. And I am running Windows 10 if this can help. Cheers! |
@Chinta03 I see. I've tested before with a pad (using a d-pad + analog) to validate the SOCD clean modes. In which mode do you connect the board (which buttons did you hold) on the PC? The app reads the inputs as Windows does, that's the problem, using my I need some time to investigate how to bypass this UPDATE: |
For my setup. I'm not using any of the Analog inputs, but only the "DPAD" inputs to press opposing directions. |
@Chinta03 how did you set this mode up? I could not find it in the Brook docs. |
@lucasteles That would be the XBOX 360 mode, so connecting the USB while holding 3P. |
Description:
When the controller is set to no SOCD cleaning in order to display on stream the actual inputs on the hitbox controller, the Input Display application does not always show the proper input.
Also a lack of feature to pick which SOCD cleaning to use.
Prerequisites
Reproduction steps
2.1 Left + right
2.2 Left + Up + Down
Actual results:
Some inputs combo result in the wrong input in the Input Display.
Expected result:
Show the right input according to the SOCD cleaning rule.
The text was updated successfully, but these errors were encountered: