Search Issue Tracker

Duplicate

Votes

2

Found in [Package]

0.9.3-preview

Issue ID

1390878

Regression

Yes

[Mobile] Input is not registered when pressing more than 1 time on the same pixel

Package: Input System

-

How to reproduce:
1. Download the attached project "InputSystemBug.zip"
2. Open Device Simulator and enter Play mode
3. In Device Simulator window, Press/click the button in the Scene 2 times (both presses/clicks have to be on the same pixel)

Expected result: The button is highlighted with a gray color when pressed
Actual result: The button is not highlighted with a gray color and becomes white (same behavior when pressing on background in the Scene)

Reproducible with: 0.9.3-preview (2019.4.34f1, 2020.3.25f1), 1.2.0 (2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2)
Not reproducible with: 0.9.2-preview (2019.4.34f1, 2020.3.25f1)

Reproducible on:
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
iPhone 11 (iOS 13.5)

Notes:
- Can be reproduced with Device Simulator in Editor and on physical mobile devices
- The issue reproduces only when pressing on the same pixel twice, so it's very hard to reproduce on real devices

  1. This is a duplicate of issue #1330014

    OnClick isn't triggered on the second click when the mouse isn't moved and Simulate Touch Input from Mouse or Pen is enabled
Log in to vote on this issue

Comments (2)

  1. mylastggeast

    Jan 11, 2022 05:28

    Update: this might be a duplicate of https://issuetracker.unity3d.com/issues/onclick-isnt-triggered-on-the-second-click-when-the-mouse-isnt-moved-and-simulate-touch-input-from-mouse-or-pen-is-enabled?_ga=2.22047288.2084275108.1641875662-1118946236.1635148951 which has been merged in 1.3.0
    After updating to 1.3.0 I cannot reproduce the error anymore

  2. mylastggeast

    Jan 05, 2022 06:02

    "The issue reproduces only when pressing on the same pixel twice, so it's very hard to reproduce on real devices"
    The above is true but on low-pixel density devices (eg low spec Android devices) this is much easier to reproduce apparently, especially when for example exiting a sub-menu by tapping a 'back' button rapidly twice in a row. In general, I would expect this to be noticeable by many users and disregarded as 'poor input handling by the game' or 'lag'.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues