Search Issue Tracker
Fixed in 6000.1.0b13
Fixed in 6000.1.X, 6000.2.X, 6000.2.0a8
Votes
0
Found in
6000.1.0a6
6000.2.0a1
Issue ID
UUM-89023
Regression
Yes
Multiple simultaneous inputs with the touch screen sometimes leaves button in not default state
How to reproduce:
1. Create a new Unity project
2. Set up the UI Document with the multiple default buttons in it
3. Enter the Play Mode
4. Simultaneously click multiple buttons with the touch controls
5. Observe the results
Expected results: Multiple input doesn't break button behavior
Actual results: Some buttons stay in the clicked or selected state
Reproducible with: 6000.0.29f1
Not reproducible with: 2021.3.46f1, 2022.3.53f1
Reproducible on: Windows 11 (ARM)
Not reproducible on: No other environment tested
Notes:
- Unable to find a regressed version due to hardware limitations
- The issue is more visible with a complete project (e.g. QuizU Sample project)
- Reproducible in both Player and Play Mode but more visible in Player
- Clicking the "stuck" button with the mouse doesn't always resolve the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment