Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
1.8.0-pre.1
Issue ID
ISXB-664
Regression
No
Player Input is showing the wrong corresponding Input when using Xbox controller
Reproduction steps:
1. Open the attached “NewInputTests.zip” project
2. Build And Run
3. Connect the Xbox controller
4. Select “Xbox” on Devices dropdown in the Player
5. Move around both Joysticks of the controller and observe the Player
Expected result: Xbox controller in the Player corresponds with the inputs of the connected Xbox controller
Actual result: Xbox controller in the Player does not correspond with the inputs of the connected Xbox controller
Reproducible with: 1.4.4 (2021.3.16f1), 1.7.0 (2021.3.16f1), 1.8.0-pre.1 (2021.3.16f1)
Reproduced on: Windows 10
Notes:
- Not reproduced by CQA
- User noted that the issue reproduces with these devices (via Bluetooth and cord): Xbox Series S controller, Xbox 360 Controller, Xbox Elite Wireless Controller Series 2, third-party Xbox 360 controllers
- User noted that the issue is only reproducible on one of their machines so the issue might be specific to that machine
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note:
We can no longer reproduce this issue using the latest Unity + Input System package with 3 different Xbox controllers.
If you can still reproduce this with the latest versions, please reopen the case.