Search Issue Tracker
Active
Votes
0
Found in [Package]
1.8.2
Issue ID
ISXB-1118
Regression
No
[Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
Steps to reproduce:
1. Create a new project
2. Install Input System package
3. Setup On Screen Controls for an Android device
4. Build to Android
5. Press the screen with 1 finger and before releasing press the screen with a second finger
6. Log TouchID's and UIElements hit, observe how the second touch is not translated into UI event line OnPointerDown
Expected results: Second touch is translated into UI Event line OnPointerDown by InputSystemUIInputModule
Actual results: Second touch is not translated into UI Event line OnPointerDown by InputSystemUIInputModule
Reproducible with according to the user: Input System 1.8.2 (2021.3.44f1)
Notes:
-According to the user the issue reproduces mostly on low end Android devices when the framerate is below 30fps
-Forum post: https://forum.unity.com/threads/input-system-1-8-2-released.1590456/#post-9908010
-A workaround for this issue is to replace the cache of control references m_PointerTouchControls with the cache of touch IDs (integers)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
Add comment