Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.2.0a19
2021.2.0b8
2022.1
Issue ID
1361200
Regression
Yes
UI Buttons are not interactable when running Build with FullScreenMode.MaximizedWindow and resolution lower than native
1. Create a new HDRP project
2. Delete all GameObjects from the scene
3. Add attached "Canvas.prefab" and "BugTester.cs" files to the project
4. Place Canvas prefab in the scene
5. Add BugTester Component to the Canvas GameObject
6. Drag Canvas and its Child GameObjects to the properties of BugTester Component (Text1 to Text, Text2 to Text 2, Canvas to Scaler)
6. Add Camera and Event System GameObject to the scene
7. Select Event System GameObject in the Hierarchy and Replace Standalone Input Module with InputSystemUIInputModel
8. Save the Scene
9. Navigate To Edit --> Project Settings --> Player --> Other Settings and change Active Input Handling to Both
10. Build and Run the Project
11. Press "J"
12. Hover your mouse over one of the Buttons
Expected result: The Button should turn green and be interactable
Actual result: The Button does not turn green and cannot be interacted with
Reproducible with: 2021.2.0a19, 2021.2.0b10, 2022.1.0a6
Not reproducible with: 2019.4.30f1, 2020.3.18f1, 2021.1.20f1,2021.2.0a18, 2022.1.0a7, 2022.1.0a8
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a7