Search Issue Tracker
Won't Fix
Won't Fix in 1.3.X
Votes
0
Found in [Package]
1.3.0
Issue ID
ISXB-26
Regression
No
(MacOS) Left JoyStick on Wireless Xbox One controller presents non zero value when application is launched
Reproduction steps:
1. Open the attached project "WirelessControllerIssue.zip"
2. Connect Xbox One controller via Bluetooth
3. In "File > Build Settings" make sure that the "Test" Scene is added in Scenes in Build
4. Build and Run
5. Observe the "Left JoyStick" X, Y values
Expected result: The X, Y values of the left stick starts at (0, 0)
Actual result: The X, Y values of the left stick starts at non (0, 0) values
Reproducible with: 1.1.1, 1.3.0 (2019.4.37f1, 2020.3.32f1), 1.3.0 (2021.2.17f1, 2022.1.0b14, 2022.2.0a8)
Note: When the project is opened for the first time incorrect value is visible in the Input Debugger
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
We'll just have to be honest that we won't be getting around to fixing it anytime soon. Sorry.
Workaround is to reset values on startup.
Resolution Note (1.3.X):
We'll just have to be honest that we won't be getting around to fixing it anytime soon. Sorry.
Workaround is to reset values on startup.