Search Issue Tracker
In Progress
In Progress in 6000.6.X
Votes
0
Found in
6000.0.8f1
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-74919
Regression
Yes
The frame rate is inconsistent and not maintaining a stable target FPS when using Application.targetFrameRate
How to reproduce:
1. Open the “PauseTest2022” project
2. Open the SampleScene
3. Enter Play Mode
4. Observe the FPS in the Game View
Expected result: The frame rate maintains a stable 30 FPS without fluctuations
Actual result: The frame rate is fluctuating rapidly between 29-30 FPS
Reproducible in: 2020.2.0a5, 2021.3.40f1, 2022.3.35f1, 6000.0.8f1
Not reproducible in: 2020.2.0a4
Reproducible on: Windows 10, Windows 11 (user’s)
Not reproducible on: No other environment tested
Notes: Also reproducible in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment