Search Issue Tracker
Fixed in 2020.2
Votes
0
Found in
2019.1.0a11
2019.3
2019.3.10f1
2020.1
2020.2
Issue ID
1239354
Regression
Yes
[macOS][OpenGL] VSync Count does not lock the framerate upon launching the Player with QualitySettings.vSyncCount = 1
How to reproduce:
1. Open user-submitted project (vSync_OpenGLCore_bug.zip)
2. Open the SampleScene
3. Make sure OpenGLCore is the primary graphics API in the Player Settings
4. Build and run the project in full screen
Expected result: the project starts with vSyncCount 1 and the framerate is locked
Actual result: the project starts with vSyncCount 1, but the framerate is unlocked
Reproducible with: 2019.1.0a11, 2019.3.13f1, 2020.1.0b8, 2020.2.0a11
Not reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.1.0a10
Notes:
Does not reproduce in the Editor
Does not reproduce with Metal
Setting vSyncCount to 0 and then back to 1 locks the framerate correctly
Could not reproduce on Windows
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
- Double-clicking a script in the Inspector window does not open the External Script Editor
- [Android] ASTC HDR check may cause issues with RenderDoc
- [CPULM] Enabling indirect denoising and gaussian AO filter causes bright halos
- [Android]APK fails to be registered when building using Keystore with the build
- Fix doc and typo in Scene TemplatePipeline
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a14