Search Issue Tracker
Fixed in 1.4.1
Votes
0
Found in [Package]
1.3.0
Issue ID
1389858
Regression
No
OnMove() debugs a different value than Input Debugger when quickly pressing two different D-pad buttons in a row
Reproduction steps:
1. Connect the controller
2. Open the "SampleScene" Scene in the attached project "Scifi Platformer.zip"
3. Open the Input Debugger from Window > Analysis > Input Debugger
4. From the devices list select the controller and open it
5. Enter the Play mode
6. Press down on D-pad
7. Quickly press right on D-pad
8. Observe the Console output and Dpad Value in the XInputControllerWindows device window
Expected result: Values are (1.0, 0.0) in both outputs
Actual result: Value in Console stays (0.0, -1.0), but in the XInputControllerWindow Value changes to (1.0, 0.0)
Reproducible with: 0.9.1-preview (2019.4.34f1, 2020.3.25f1), 1.2.0, 1.3.0 (2019.4.34f1, 2020.3.25f1, 2021.2.8f1, 2022.1.0b2)
Could not test with: 0.9.0-preview (2019.4.34f1, 2020.3.25f1) - errros in the Console
Note:
- Reproducible with Xbox Series X, Xbox One, DualSense controllers
- Not reproducible with DualShock4
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
- Packman: The same asset data is displayed differently in "Import" and "Remove" popups
- Reference to a deleted GameObject becomes "None" instead of "Missing" when the GameObject is restored with undo after entering and exiting Play Mode
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
- Blur shader doesn't work when the "Scene Color" Node is attached to the UI "Output" Node
Resolution Note (fix version 1.4.1):
Fixed in: 1.4.1