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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Add comment