Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.48f1
2021.3.25f1
2022.2.20f1
2023.1.0b17
2023.2.0a15
2023.3.0a3
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-35466
Regression
No
[macOS] Performance degradation in Builds when setting QualitySettings.vSyncCount to 2
How to reproduce:
1. Open the user-attached “FPS Fail.zip” project
2. Build and Run the user project with the “Sample Scene” added (File → Build Settings)
3. In the Player select the “QualitySettings.vSyncCount: X” button to change its vSyncCount to 2
Expected result: Stable performance regardless of vSyncCount and no jittering
Actual result: Performance is unstable ~55-59FPS and jittering is slightly visible
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.20f1, 2023.1.0b17, 2023.2.0a15
Reproducible on: macOS M1 Max Ventura 13.2.1 (Silicon), macOS Ventura 13.1 (Intel)
Not reproducible on: Windows 11
Notes:
- On Intel macOS it appears that the FPS is even worse ~30-33FPS
- User stated that the issue only happens with ProMotion, but changing it to a different refresh rate still reproduces the issue
- Not reproducible in the Editor
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.