Search Issue Tracker
Fixed
Fixed in 2022.2.3f1, 2023.1.0a4
Votes
0
Found in
2023.1.0a2
Issue ID
UUM-2325
Regression
No
Unsaved changes window is almost impossible to use when closing a lot of unsaved scenes with long paths
How to reproduce:
1. Open the user's attached "SaveTooManyScenesBug" project
2. In the main menu, click Bug -> "Step 1 open scenes"
3. In the main menu, click Bug -> "Step 2 dirty scenes"
4. In the main menu, click Bug -> "Step 3 close scenes"
5. Observe the unsaved changes window
Expected result: The window allows to save or not to save the scenes with no issues
Actual result: The window is way too big and the buttons aren't visible
Reproducible with: 2020.3.35f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a13
Could not test with: 2019.4.39f1 (Bug button didn't appear)
Note: The window can also be used blindly with arrow keys
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment