Search Issue Tracker
By Design
Votes
1
Found in [Package]
1.1.0-preview.3
Issue ID
1319692
Regression
No
[Input System] Stick events are spammed in Play mode when using a PS4 controller and not moving the joysticks
How to reproduce:
1. Open the user's attached project "Test PS4 controller.zip"
2. Connect a PS4 controller to the computer
3. From the Project tab, open Assets/Scenes/SampleScene.unity
4. Enter Play mode
5. Observe the Console tab
Expected results: no messages are logged in the Console if the left joystick is not being moved
Actual results: "Stick moved: (0.0, 0.0)" is spammed in the Console even though the controller is not being interacted with
Reproducible with: 2019.4.22f1, 2020.2.7f1, 2020.3.1f1, 2021.1.0b12, 2021.2.0a9 (Input System 1.0.2, 1.1.0-preview.3)
Could not test with: 2018.4.33f1 as it requires outdated versions of Input System
Notes:
- The issue is not reproducible with Nintendo Switch Pro and Xbox One controllers
- The issue is reproducible on macOS (Player and Editor), Windows (Player and Editor)
- The issue doesn't seem to reproduce on Linux (Player and Editor) as no messages are logged at all even when moving the left joystick
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
- Shader transparency, discard, and clip are not working when using the Player
- Error is thrown when clicking on warning in the console
- Long IL2CPP build time when project has a .ufbx library wrapper
- Cursor doesn't change to the resizing when using the Rect Tool and the Sprite is too close to the bottom of the Scene View
- InvalidOperationException exception is thrown when Editor Default Text Rendering Mode is set to "Bitmap" and Editor Font is set to "System Font" and an array is expanded in the Inspector Window
Resolution Note:
Action was set to "Pass-Through". By design, there is no filtering whatsoever applied to these actions. If the state changes in any way (which it does here; the still will constantly wiggle around by small amounts), the action performs. Setting the action to "Value" instead immediately solves the problem.