Search Issue Tracker
Won't Fix
Votes
2
Found in
2020.3.46f1
2021.3.20f1
2022.2.10f1
2023.1.0b7
2023.2.0a5
Issue ID
UUM-29314
Regression
No
Frame rate stutters in macOS Player when vSyncCount is 2 or more
Reproduction steps:
1. Open “vSyncCountProject“
2. Open “SampleScene“
3. Build And Run
4. Observe frame rate stats for 30 seconds
Expected result: frame rate does not stutter, and the average frame rate is half of the screen’s refresh rate
Actual result: occasionally frame times slightly decrease or double, and the average frame rate is below expected by one or more
Reproduced in: 2020.3.46f1, 2021.3.20f1, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5
Reproduced using: macOS 13.0.1 (Intel)
Not reproduced using: Windows 11
Notes:
1. The user reports consistent 120 FPS when vSyncCount is 1 but 57-58 FPS (without reaching 60) when vSyncCount is 2
2. Unable to test in Play mode because vSyncCount has no effect in Play mode
Comments (1)
-
igorhart
Apr 27, 2023 08:35
That's not cool.
I would fix that myself but generating Xcode project source for Mac OS platform doesn't work for some reason.
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.