Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1330014
Regression
No
OnClick isn't triggered on the second click when the mouse isn't moved and Simulate Touch Input from Mouse or Pen is enabled
How to reproduce it:
1. Open the user's attached project "Input System Touch Input Bug Replication.zip"
2. Open the Input Debug window (Window > Analysis > Input Debugger)
3. In the Input Debug window make sure "Simulate Touch Input from Mouse or Pen" is enabled in the Options dropdown list
4. Enter Play Mode
5. Click on the button twice (don't move the mouse between clicks)
Expected result: The button is clicked twice
Actual result: The second click doesn't trigger the OnClick event
Reproduces on: 1.0.2, 1.1.0-preview.3 (2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17)
Could not test with: 2018.4.35f1 - Input Debugger was not yet available
Notes:
- Not reproducible after moving the mouse between clicks
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 1.3.0):
Fixed in: 1.3.0 (2019.4.0f1)
Fixed by: https://github.com/Unity-Technologies/InputSystem/pull/1449