Search Issue Tracker
Fixed
Fixed in 1.14.0
Votes
7
Found in [Package]
1.14.0
Issue ID
ISXB-810
Regression
No
[macOS] D-pad upper left corner is not logged with the Xbox controller
Reproduction steps:
1. Open the attached “Controller Bug.zip” project
2. Connect the Xbox controller via Bluetooth and enter Play mode
3. Press the upper left corner of the D-pad and observe the text on the Game window
Expected result: “up and left” text is displayed
Actual result: “no press” text is displayed
Reproducible with: 1.8.0 (6000.0.0b12), 1.8.0-pre.2 (2021.3.36f1, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12)
Reproduced on: macOS Sonoma 14.3 (Intel), macOS 14.3.1 (M1) (by user), Xbox Wireless controller
Not reproduced on: Windows 11 Pro
Note: Issue is not reproducible with DualShock, Dualsense and Nintendo Switch Pro controllers
Comments (1)
-
devbobcz
Jan 10, 2025 16:44
Same issue on my project, M1 MAC, Unity 2023.1.19f1, xbox one series gamepad thru bluetooth,
when you use input debugger (Window-Analysis-Input Debugger), all axes of d-pad are fine, but when you sent it do the game as Vector2 (in event from new input system) , the LEFT + UP return nonsense vector.
UP+RIGHT => 0.7, 0.7 OK
RIGHT+DOWN => 0.7, -0.7 OK
DOWN+LEFT => -0.7, -0.7 OKLEFT+UP, or UP+LEFT => 0, 0 TERRIBLY WRONG :(
Thanx for fix it as soon as possible :) Thank you Bob
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (fix version 1.14.0):
This issue has been fixed and will be available in the release of the next patch/minor version.