Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X
Votes
1
Found in
6000.0.49f1
6000.1.3f1
6000.2.0b3
Issue ID
UUM-107781
Regression
No
Game View Scale changes when a SceneView is opened on a different screen with a different Display Scale
How to reproduce:
1. Open the project “IN-102289_GK2Updated”
2. Move the Scene Tab (can be any Editor tab) to a different screen
3. In the Game View Tab set the Scale to the lowest possible value
4. Change the Scale level on that screen via the OS options (Windows: Settings → Display → Select Monitor → Scale)
5. Click and/or move the mouse on either the Game Tab Unity Editor Window or the Scene Tab Window
6. Observe the Game View Tab
Expected result: The scale does not change automatically
Actual result: The scale changes erratically
Reproducible with: 6000.0.49f1, 6000.1.3f1, 6000.2.0b3
Could not test with: 2022.3.62f1 (custom scripts depend on newer package methods)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- For the issue to reproduce, make sure that all the errors are clearable (Console → Clear)
- Sometimes changing the Display Scale is not required to reproduce, however this seemed to be the best way to reproduce the issue consistently
- The setup used:
Main Editor Window with the Game View Tab: 3840x2160 (150% scale), 2560x1440 (250% scale)
Scene View Tab: 3840x2160 (350%, 400% scale)
Comments (1)
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
- Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
- Event "XRInputSubsystem.trackingOriginUpdated" triggers twice when recentering the view
- UITK TextField value is overwritten incorrectly by the converter result when Binding Mode is set to "To Source"
- Out of memory crash when selecting more than 80000 Assets simultaneously
- UI Toolkit Button text is not rendered when the Button has fixed height with specific Icon font
abdukirCDM
Jun 12, 2025 07:23
I did reproduce the same issue. It happens when you have two differently scaled screens. Making the screens same scale fixes the issue but its not usable