Search Issue Tracker
Fixed
Fixed in 1.13.0
Votes
0
Found in [Package]
1.12.0
Issue ID
ISXB-1264
Regression
No
The value of the "Select" button is shown as 0 in the Input Debugger when pressed on the Xbox One controller
How to reproduce:
1. Open any project with Input Systems package
2. Open Windows → Analysis → Input Debugger
3. Press the “Select“ button on an Xbox One controller
4. In the Input Debug window find the controller under Devices
5. Double-click on the controller
6. Press the “Select“ button and observe the Value
Expected result: Value is shown as 1
Actual result: Value is shown as 0
Reproducible with: 1.11.2 (2022.3.48f1)
Reproducible on: macOS 15.1.1
Not reproducible on: No other environment tested
Notes:
- Not reproduced by CQA
- Not reproducible with: Xbox 1914 controller
- Not reproducible with: Xbox Controller Series 2 1797 controller
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
- “Assemblies” and “Areas” tabs disappears after switching to Scene tab and back in the Assemblies filter window
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
Resolution Note (fix version 1.13.0):
This issue will be fixed in the next released version.