Search Issue Tracker
By Design
Fixed in 2021.1.X
Votes
0
Found in
2019.3.0a4
2019.4
2020.1.14f1
2020.2
2021.1
2021.2
Issue ID
1305631
Regression
Yes
vSyncCount does not work and targetFrameRate is not ignored when vSyncCount is used in the Play Mode
How to reproduce:
1. Open the attached "fps" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
Expected results: The text in the middle of the Game view shows ~35 fps
Actual results: The text in the middle of the Game view shows ~300 fps (150 if the VSync is enabled in the Game view)
Reproducible with: 2019.3.0a4, 2019.4.21f1, 2020.2.6f1, 2021.1.0b8, 2021.2.0a6
Not reproducible with: 2018.4.32f1, 2019.3.0a3
Notes:
- Enabling vSync in the Game view through drop-down will set the frames to ~150 but the targetFrameRate will still not be ignored
- In the Build, the targetFrameRate is ignored and you get the correct fps depending on what is vSync set to
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
- The terrain appears darker when "Per-pixel Normal" is enabled
- [Linux] Editor assertion causes Test Runner to fail when executing it in Batch Mode
- Color selection by the mouse cursor is still enabled when the "Esc" button is pressed
- Game view becomes black and the Scene window becomes grey, “ArgumentOutOfRangeException” errors and “Render Pipeline error” warnings appear after changing the name or deleting URP/HDRP global settings file
- Transform Component is not accessible inside the Player when RuntimeInitializeOnLoadMethod is used
Resolution Note:
Global vsync cannot affect editor viewports, because every viewport would wait for vsync separately and that would make everything very slow if lots of windows are open. This bug was fixed in 2019.3.0a4. There's a separate vsync option for the game view, and it works correctly.