Search Issue Tracker
Fixed
Fixed in 2022.3.18f1, 2023.2.7f1, 2023.3.0a7
Votes
0
Found in
2022.3.0f1
2023.1.0b19
2023.2.0a17
Issue ID
UUM-37294
Regression
Yes
Frames in the player are not skipped if the player is moved to a different monitor when using “OnDemandRendering” and “VSyncCount”
How to reproduce:
1. Build And Run the user’s attached “ODRTest.zip” project
2. In the Player, set “RenderFrameInterval” to 10
3. Set “VSyncCount” to 2
4. Move the player to another monitor
5. Observe the FPS, “EffectiveRenderFrameRate”, and “ScreenRefreshRate”
Expected result: FPS is ~30, “EffectiveRenderFrameRate” is 3, and “ScreenRefreshRate” is ~60
Actual result: FPS gets boosted about 200, “EffectiveRenderFrameRate” is -1, and “ScreenRefreshRate” is NaN
Reproducible with: 2022.2.0a16, 2022.2.21f, 2022.3.0f1, 2023.1.0b19, 2023.2.0a17
Not reproducible with: 2021.3.26f1, 2022.2.0a15
Reproduced on: macOS 13.2.1 (Intel)
Not reproduced on: Windows 10 21H2
Notes:
Reproducible when having one or two monitors connected to the computer
FPS issue is reproducible on Google Pixel 3 when having ”TargetFrameRate” set to 60 and “RenderFrameInterval” set to 4 (user’s info). It was not reproducible on iOS
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Resolution Note (fix version 2023.3.0a7):
Fixed in: 2023.3.0a7
Resolution Note (fix version 2023.2.7f1):
Fixed in: 2023.2.7f1
Resolution Note (fix version 2022.3.18f1):
Fixed in: 2022.3.18f1