Skip to content
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

Xbox Controller Triggers have a wrong default value #206

Open
producation opened this issue Dec 3, 2023 · 1 comment
Open

Xbox Controller Triggers have a wrong default value #206

producation opened this issue Dec 3, 2023 · 1 comment

Comments

@producation
Copy link

Environment

  • OS: MacOS 12.7.1 (M1 Max Silicon)
  • Version 1.9.17
  • Xbox One (S) Controller Model 1708

Describe the bug
Without using the triggers at the back of the Xbox One S Controller LT (Axis 5) & RT (Axis 6) they act like they are half pressed. When I press them over the deadzone the Axis shows the real value (like in the picture below the Axis 6; there it is slightly pressed). So the Triggers act completely normal if in use but if not used they fall back to half pressed.

I also tried to play around with to offset in a negative way: between an offset of -0.62 and -0.38 (with my Deadzone) it stays initialy at 0 but when I press the trigger it starts at a negative value and has a pretty big dead zone around 0 before it grows pretty fast to 1 with the trigger not even full pressed.

The Incoming Log of the Controller did not work either.

To Reproduce
Steps to reproduce the behavior:

  1. Add Gamepad module
  2. Select Xbox One Controller S from the Dropdown List in the Gamepad Inspector
  3. Enable Log Incoming in the Gamepad Inspector / Module List

Expected behavior
Axis 5 and 6 should start at 0 and just go up 1. It doesn't need to have negative values.

Additional context
I tested the controller in other applications/games and it works as it should be. Unfortunately I don't have another controller to test.

Bildschirmfoto 2023-12-03 um 01 01 30
@EmerickH
Copy link
Contributor

I've just tested and it works normally with a wired Xbox 360 controller (smooth values from 0 to 1).
Did you connect the controller via Bluetooth or USB? Can you try the other method to see if it changes anything?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants