Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 2023.2.X
Votes
0
Found in
2020.3.48f1
2021.3.25f1
2022.2.20f1
2023.1.0b17
2023.2.0a15
2023.3.0a3
6000.0.0b11
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Add comment