Search Issue Tracker
By Design
Votes
19
Found in [Package]
1.1.0-preview.2
Issue ID
ISXB-259
Regression
No
[Input System] OnPointerDown sometimes doesn't get triggered when pressing a button shortly after releasing another button
Steps to reproduce:
1. Open the attached project ("1324518.zip")
2. Open "SampleScene"
3. Build to a device
4. Press one button
5. While releasing the pressed button, press the other button
Expected results: OnPointerDown is triggered whenever a button is pressed
Actual results: OnPointerDown is sometimes not triggered when a button is pressed shortly after releasing another button
Reproducible with: Input System 1.1.0-preview.2, 1.1.0-preview.3 (2019.4.24f1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a13)
Not reproducible with: Input System 1.0.0, 1.0.1, 1.1.0-preview.1 (2020.3.4f1)
Reproducible on:
iPhone XR (13.4.1)
VLNQA00013, Samsung Galaxy S6 Edge Plus (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
Notes:
- The case seems closely related to Case 1267026 (https://issuetracker.unity3d.com/product/unity/issues/guid/1267026/), as the behaviour in that case can be triggered following the steps from this scenario. However, The mentioned issue doesn't seem to reproduce from 1.1.0-preview.3, only this issue remains.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Quick state transitions such as these can occasionally be lost on the default 60Hz polling frequency, if this causes significant issues for your game consider increasing it to a higher number which should solve the issue
https://docs.unity3d.com/Packages/com.unity.inputsystem@0.9/api/UnityEngine.InputSystem.InputSystem.html#UnityEngine_InputSystem_InputSystem_pollingFrequency