Search Issue Tracker
Fixed
Votes
0
Found in
2020.3.41f1
2021.3.13f1
2022.1.22f1
2022.2.0b15
2023.1.0a18
Issue ID
UUM-19834
Regression
No
VSync doesn't take effect when enabling it through Quality settings
Reproduction steps:
# Create project
# Go to “Project Settings > Quality”
# Change VSync Count to “Every Second V Blank”
# Enter the Play Mode
# Open “Game View > Stats”
# Observe the Frame rate
Expected result: Frame rate is capped at 30 FPS
Actual result: Frame rate is uncapped
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b15, 2023.1.0a18
Reproducible on: Windows 11
-
tamana
Feb 06, 2023 03:05
I am confused as to why the Unity team marked this issue as a duplicate. The issue they marked as a duplicate only occurs during runtime, but this issue occurs only in the Editor. The duplicate issue was reported as fixed in 2023.1.0b2, but after checking, I discovered that it was only fixed during runtime and the fps is still capped at the monitor refresh rate if I have "VSync" enabled in the Editor. Can you please reopen this issue?
-
tamana
Nov 25, 2022 07:08
Yes, I can enable VSync on Game View's toolbar. But it only limit the frame rates to monitor refresh rate. If I'm using 360 FPS gaming monitor, the fps will still goes beyond 60.
What I'm reporting was definitely bug.
Like, what you're saying is "Every Second V Blank still present on the editor, but it doesn't do anything. Please use the other one instead."
And the other one is not what I was looking for. Could you elaborate, please?
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-17522