Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.27f1
2022.3.2f1
2023.1.0f1
2023.2.0a20
2023.3.0a3
6000.0.0b11
Issue ID
UUM-40440
Regression
No
Periodic frame stutter when Vsync is enabled with multiple monitors and differing refresh rates
Reproduction steps:
1. Connect three monitors that all are set to different refresh rates (i.e. first is set to higher than 60Hz, second - to 60Hz, third - to lower than 60Hz)
2. Open the attached “FrameDropRepro” project
3. Build and Run the project
4. Observe the frame rate counter in the top right corner of the Player for a few minutes
Expected result: The frame rate never drops below 60 FPS
Actual result: The frame rate occasionally drops below 60 FPS indicating a dropped frame
Reproducible with: 2021.3.27f1, 2022.3.2f1, 2023.1.0f1, 2023.2.0a20
Reproducible on: macOS 13.3 (Intel)
Note: The reproduction is inconsistent and may require waiting for a long time or relaunching the built Player multiple times to reproduce the issue.
Note2: please see the corresponding slack thread here; https://unity.slack.com/archives/C0105CH72UV/p1687367495176459
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Hardware limitations mean we can't vsync. Workaround is turn off vsync and use on demand rendering to limit frame rate.