Search Issue Tracker
By Design
Votes
3
Found in
2021.3.29f1
2022.3.7f1
2023.1.9f1
2023.2.0b5
2023.3.0a3
Issue ID
UUM-45993
Regression
No
Application.targetFrameRate has no effect on the frame rate when used in WebGL Player
Reproduction steps:
1. Open the attached project “WebGLbug“
2. Build and run the Player (File > Build And Run)
3. Observe the Console (RMB > Inspect > Console)
Expected result: The frame rate is capped at 30 FPS
Actual result: The Player is running at the same frame rate as the monitor's refresh rate
Reproducible with: 2021.3.29f1, 2022.3.7f1, 2023.1.9f1, 2023.2.0b5
Reproducible on: Windows 11
Comments (1)
-
uwdlg
Aug 13, 2023 11:50
This doesn't appear to be a regression in the Unity code, but rather a change in how browsers treat WebGL builds, as I have builds online from months ago that used to have the framerate capped but don't anymore.
There is also a related thread on the forums here: https://forum.unity.com/threads/targetframerate-not-working-in-2021-3-1-lts-webgl.1281161/
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
- Separation lines between minimized fields become invisible when scrolling in the Profiler
- Drag & drop and object picker assignment fail when ExposedReference variables are used in a Timeline clip
- AudioSource.time prints out 0 when AudioSource is not playing even if it is manually set
- [Android] Crash on "UnityMotionEventCallbacks::_GetPointerIdImpl" when giving 8 simultaneous touch inputs
- "[Header]" attribute is misaligned when placed before an InputActionProperty field
Resolution Note:
Thank you for reporting a bug to Unity.
This issue will be resolved with an update in Quality Settings and Application documentation under the Unity Engine Scripting API.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.