Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2018.4.22f1
2020.2
Issue ID
1256325
Regression
No
[macOS] VSync in Quality Settings has no effect and screen tearing is visible when in Game View
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. In the Scene View, move the "Cube" in any direction
4. Observe the Game View
Expected result: No screen tearing is visible
Actual result: VSync doesn't affect screen tearing
Reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.3f1, 2020.2.0a21
Not reproducible with: 2017.4.40f1
Workaround: Enable the Game View VSync option (located under Aspect Ratio options in the top Game View toolbar)
Note: Not reproducible on Windows
Documentation: https://docs.unity3d.com/Manual/class-QualitySettings.html
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note:
The player VSync Count setting is only used within the Unity Player and it is ignored in the editor context. The best workaround is indeed to use the Game View VSync toggle (which doesn't provide a strong vsync guarantee either, but can help).