Search Issue Tracker
Active
Under Consideration for 1.7.X, 1.8.X
Votes
0
Found in [Package]
1.7.0
1.8.0-pre.1
1.8.0-pre.2
Issue ID
ISXB-683
Regression
No
View button of the Xbox controller does not map its' value in the Input Debugger
Reproduction steps:
1. Open the attached “My project (1).zip“ project
2. Connect the Xbox One controller
3. Open the Input Debugger (Window > Analysis > Input Debugger)
4. Open the Xbox One window by double-clicking on the connected Xbox controller in the Input Debugger
5. Hold down the View button and observe the Value of “select” Name
Expected result: “select” Name Value is 1
Actual result: “select” Name Value is 0
Reproducible with: 1.7.0 (2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a14), 1.8.0-pre.1 (2023.3.0a14), 1.8.0-pre.2 (2023.3.0a14)
Reproduced on: macOS Ventura 13.5.1 (Intel), Xbox One 1914 Model controller
Not reproduced on: Windows 11 Pro, Xbox One 1708 Model controller
Note: Pressing the Share button changes the “select” Name value to 1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment