Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0a4
2019.4
2019.4.0f1
2020.1
2020.2
Issue ID
1254640
Regression
Yes
VSync gets disabled in the Game view when maximizing and then minimizing the Game view
How to reproduce:
1. Create a new project
2. Enable stats in the Game view
3. Make sure VSync is enabled (In the Game view check the Free Aspect->VSync (Game view only) option)
4. Enter Play Mode
5. Maximize the Game view (Click the vertical ellipsis at the top right of the Game view and check the "Maximize" option)
6. Minimize the Game view (Click the vertical ellipsis at the top right of the Game view and un-check the "Maximize" option)
Expected result: The framerate remains synchronized
Actual result: The framerate is not synchronized even though VSync is still enabled
Reproducible with: 2019.3.0a4, 2019.3.16f1, 2019.4.0f1, 2020.1.0b13, 2020.2.0a15
Not reproducible with: 2017.4.40f1, 2018.4.23f1, 2019.3.0a3
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2020.2):
https://github.cds.internal.unity3d.com/unity/unity/pull/1316
https://ono.unity3d.com/unity/unity/pull-request/110579/_/fix-vsync-stop-on-unmaximized-1254640