Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a10
2019.4
2020.1
2020.1.0b10
2020.2
Issue ID
1251391
Regression
Yes
Editor lags for a second when moved to another monitor with different scale and maximized
How to reproduce:
1. Create and open a new project
2. Move Editor window from one monitor to another and double click the title bar to maximize it
Expected result: no lag appears before maximizing the window
Actual result: Editor lags for a second before maximizing the window
Reproducible with: 2019.1.0a10, 2019.4.0f1, 2020.1.0b12, 2020.2.0a14
Not reproducible with: 2018.4.23f1, 2019.1.0a9
Note:
- only reproduces if one of the monitors has display scale set to more than 100% (as an example 125%) (For Windows operating system go to Settings > System > Display > Scale and layout and set "Change the size of text, apps, and other items" to 125% or higher)
- in lower specification devices Application.Reload loading window may appear
- tested and reproduces with Direct3D11, Vulkan and OpenGLCore graphics APIs
-
myanko
Mar 19, 2021 14:06
I'm also getting this issue when moving a window from screens with different resolutions and not getting this issue with any other tool on Windows. (Unreal, lumberyard, modo, chrome, etc)
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
- IL2CPP Player crash on memset in VCRUNTIME140D when selecting UI GameObject
- [BiRP] GetScriptableCullingParameters() uses the wrong projection matrix when rendering two forward+ passes in XR
- Texture becomes lower quality when the texture is downloaded with script
- [tvOS] Multiple warnings in the Console when building for tvOS Platform on Intel Macbook
- [Android][Vulkan] Shader is rendered incorrectly in the Player when using Vulkan Graphics API
Resolution Note:
This behavior is required in order to refresh editor window resources. Scripts need to be reloaded to refresh new dpi resources.