Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1115291
Regression
No
FPS readout in the "Statistics" window outputs bogus values in the Editor when layout changes
Reproduction steps:
1. Open the attached project named "Case_1115291"
2. Play the Scene
3. Observe the FPS counter
4. Drag the animator window into the same tab as the Scene view
5. Observe the FPS counter again
Expected result: FPS remains stable
Actual result: FPS drops significantly
Reproducible with: 2017.4.22f1, 2018.3.8f1, 2019.1.0b6, 2019.2.0a7
Notes:
Depending on where the animator window is positioned different results are achieved. Watch the User video for more details
Also reproducible with a fresh non-HDRP project
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
- 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
Resolution Note:
low priority and unlikely to be fixed.