Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X, 2020.3.X
Votes
6
Found in
2019.3
2019.4
2020.1
2020.1.0b13
2020.2.0a4
Issue ID
1258663
Regression
Yes
[Linux] Editor doesn't restore window scale when loading saved layouts
How to reproduce:
1. Create a new project
2. In the Editor switch to the "Default" layout using the dropdown in the top right of the Editor window
3. Grab and drag the right side of the Hierarchy window as far left as it can go
4. Save the new layout as "Test" by going to the layout dropdown and selecting "Save Layout..."
5. Load the "Test" layout
6. Observe the horizontal scale of the Hierarchy window
Expected result: The scale of the Hierarchy window didn't change
Actual result: The Hierarchy window is wider
Reproducible with: 2019.3.16f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a4, 2020.2.0a16
Not reproducible with: 2018.4.24f1, 2019.3.15f1, 2020.2.0a3
Note: Tested on Ubuntu 18.04 and Windows 10 (Doesn't reproduce)
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.2):
Loading saved layouts will restore tab proportions. Also, Unity will now remember the correct size and maximized state when restarting the Editor.
Fixed in 2021.2.0a15
Resolution Note (fix version 2020.3):
Fixed in 2020.3.36f1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.13f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.17f1