Search Issue Tracker
Fixed in 1.1.0-pre.6
Votes
2
Found in [Package]
1.1.0-preview.1
Issue ID
1331571
Regression
No
[Input] D-Pad directional with Multi Tap does not trigger
Steps to reproduce:
1. Download and open the project "InputBugs.zip"
2. Open Assets/Scenes/SampleScene.unity
3. Enter Play Mode
4. Click on the "ExampleObject" GameObject in the Hierarchy
5. Notice that the Control scheme under Player Input changes depending on the input device
6. Push the left stick of the Gamepad to the right twice
7. Notice "Action happened" gets printed in the console
8. Press the right D-pad twice
Expected Result: "Action happened" gets printed in the Console
Actual Result: "Action happened" does not get printed in the Console
Reproducible with: 1.0.0, 1.1.0-preview.1 (2019.4.26f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17)
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (fix version 1.1.0-pre.6):
Fixed in Input System package: 1.1.0-pre.6