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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 0.9.0-preview):
resloved in develop, will appear in 0.9-preview