Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2021.2
2021.2.2f1
2022.1
2022.2
Issue ID
1380154
Regression
No
Play Mode FPS is uncapped when setting Interaction Mode to "Custom" and setting Frame Throttling (milliseconds)
How to reproduce:
1. Open project "editor-interaction-cap-bug.zip"
2. Open "SampleScene" Scene
3. Enter the Play Mode
4. Open the Stats window
5. Go to Unity > Preferences > General set Interaction Mode to "Custom" and set Frame Throttling to "33"
6. Observe the FPS in the Stats window
Expected result: Stats window is showing 30 FPS
Actual result: Stats window is showing FPS that is uncapped
Reproducible with: 2019.4.32f1, 2021.2.0a1, 2021.2.1f1, 2022.1.0a16, 2022.2.0a6
Not reproducible with: 2020.3.0f1, 2020.3.30f1
Notes:
- Results with Windows
With: Direct3D11, OpenGLCORE
FPS uncapped without VSync and capped to 30 with VSync
With: Direct3D12, Vulkan
FPS is uncapped with and without VSync
With: OpenGLES2, OpenGLES3
No VSync option but FPS is capped
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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Resolution Note (2022.2.X):
By design. From the docs: "Note: In Play mode, Unity ignores any throttling that you apply using this preference. The editor updates as fast as possible unless you enable the VSync option in the Game view, or set Application.targetFrameRate to a value other than –1."
https://docs.unity3d.com/Manual/Preferences.html