Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.5.X
Votes
0
Found in
6000.0.58f1
6000.2.6f1
6000.3.0b2
6000.4.0a1
6000.5.0a1
Issue ID
UUM-119452
Regression
No
Player display resolution changes to the native resolution of the monitor when Player becomes unresponsive
How to reproduce:
1. Open the attached "IN-115604" project
2. Open the “SampleScene” scene
3. Build and run the Player (File > Build and Run)
4. Use the drop-down to change to a window resolution which is not the native resolution of the monitor
5. Click the "Freeze" button and start clicking anywhere in the Player window until Unity becomes unresponsive
6. Wait until Unity responds again
7. Observe the result
Expected result: Resolution stays the same
Actual result: Resolution changes back to native monitor resolution
Reproducible with: 2023.1.0a1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b2
Reproducible on: Windows 11 Pro (24H2)
Not reproducible on: macOS 15.3 (M2 Ultra)
Notes:
- You can also change the resolution of the Player inside the project settings (Edit > Project Settings > Player > Resolution and Presentation)
- Bug is only reproducible in Fullscreen
- Bug breaks build, launching again or even rebuilding starts the Player in the native resolution of the monitor, to fix this you have to change the resolution of the build manually again
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search Operator Query blocks cannot be deleted using the keyboard
- Preferences window Overlay Background Color field names have no spaces between the words
- Baking APV causes crash when using Linux/ROCm/Vulkan
- Baking APV using Linux/rusticl/Vulkan generates no probes
- Baking APV with OpenGL causes "Kernel 'ClearBuffer' not found." error
Add comment