Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
1
Found in
2019.3.0a4
2020.1.9f1
2021.1
Issue ID
1285873
Regression
Yes
Game Panel buttons cannot be pressed when using Touch Screen
Reproduction steps:
1. Create an empty Project
2. Enable Play mode
3. Try to press the Game Panel buttons like "Maximize on Play", "Stats", etc. using a touch screen
Expected result: The buttons are registered as pressed
Actual result: The buttons register hover by changing color slightly but are not pressed
Reproducible with: 2019.3.0a4, 2019.4.14f1, 2020.1.11f1, 2020.2.0b11, 2021.1.0a5
Not reproducible with: 2018.4.28f1, 2019.3.0a3
Notes: In most cases, the buttons don't work flat out, but in some cases, the buttons work until you enable Play mode, clicking them with a mouse makes them work with Touch Screen again.
Comments (3)
-
WookieWookie
Sep 22, 2021 16:28
This is NOT FIXED in 2020.3.2f1.
-
mografi_joe
May 12, 2021 21:51
Yes, this is not fixed for me either.
-
petey
May 10, 2021 22:59
Please fix this in 2020 LTS, its really frustrating having to use another device when I need to click something in the game view.
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (fix version 2021.2):
Fix so that pen and touch work in gameview in version 2021.2.0a1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.11f1