Search Issue Tracker
Fixed
Votes
1
Found in
3.5.0f1
Issue ID
440186
Regression
No
Application.targetFrameRate inconsistent with documentation
According to docs: "targetFrameRate is ignored in the editor".
In practice:
- it works in the editor as long as vsync is off
- once set, it keeps its value until reset again
Repro:
- switch off vsync in current platform's quality settings
- set a frame rate from script:
function Awake () { Application.targetFrameRate = 20; }
- play, notice the setting takes effect (FPS==20)
- stop, comment out the script
- play, notice the setting is still on (FPS==20)
Expected:
- either expose targetFrameRate as a setting (and change docs) or disable it in the editor
Not a regression, same behaviour in 3.4.
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