Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.57f1
6000.2.3f1
6000.3.0b1
6000.4.0a1
Issue ID
UUM-117108
Regression
No
Touch inputs stops registering after 20-100 touches in the Device Simulator view
Steps to Reproduce:
1. Open the attached “IN-113970” project
2. Open the “Combat” Scene (Assets/Scenes/GameScenes/Combat.unity)
3. Enter Play Mode
4. Open the Simulator view
5. In the Simulator view, tap repeatedly until game stops taking inputs (Tap on non-interactable in-game objects to prevent the game from stopping)
6. Observe the Console window for touch feedback
Expected results: Touch input is always registered and logged
Actual result: after 20-100 touches, the input is no longer registered
Reproducible with: 2023.3.0a5, 6000.0.57f1, 6000.2.3f1, 6000.3.0b1
Reproducible environments: Windows 11 (by reporter), Windows 10
Not reproducible environments: macOS 15.6.1 (M3 Max)
Reproducible with these devices:
By reporter - Samsung Galaxy A53, CPU: Exynos 1280, GPU: Mali-G68
Not reproducible with these devices:
VLNQA00641 - Google Pixel 9 (Pixel 9), CPU: -, GPU: Mali-G715, OS: 15
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12
Note: After the input stops registering, switch to Game view and then back to Simulator view to unfreeze it
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit Button text is not rendered when the Button has fixed height with specific Icon font
- Unable to bind RenderTexture to the VisualElement's StyleBackground property
- SVG fails to import when 'stroke-miterlimit' is less than 1
- Test Runner fails to create a script in the active path when selecting a file as the active path
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
Add comment