Search Issue Tracker
Fixed in 0.9.0-preview
Votes
0
Found in [Package]
0.2.6-preview
Issue ID
1141689
Regression
No
[Windows][DualShock] A plugged-in DualShock gamepad keeps sending Acceleration and AngularVelocity input.
GitHub: https://github.com/Unity-Technologies/InputSystem/issues/494
Though the constant input value change doesn't cause problem normally, when users try to use the Input Detect to bind Actions, it interferes the real input, like bug 1136357
Repro:
1. Download package and project at: https://github.com/Unity-Technologies/InputSystem
2. Open an existing or create a new InputAction Asset
3. Use the Input Detect to bind an Action (◉ button next to the dropdown menu)
4. Observe the bond input
5. (Optional) Open Input Debugger and observe the DualShock device input
Acutal: A plugged-in DualShock gamepad contantly sends Acceleration and AngularVelocity input.
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 (fix version 0.9.0-preview):
resloved in develop, will appear in 0.9-preview