Search Issue Tracker
Fixed in 2020.2.X
Votes
6
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1252043
Regression
No
Holding the "F" key shortcut affects the performance significantly when Scene View is hidden and the Game View is opened
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Enter the Play Mode
3. In the Game View, inspect the shown FPS count
4. Press and hold the "F" key
5. Inspect the shown FPS count again
Expected result: Holding the "F" key shortcut doesn't affect the performance when Scene View is hidden and the Game View is opened
Actual result: Holding the "F" key shortcut affects the performance significantly when Scene View is hidden and the Game View is opened
Reproducible with: 2018.4.25f1, 2019.4.4f1, 2020.1.0b16, 2020.2.0a18
Note: Other key presses affect the performance at less than half of the impact on FPS than the "F" key
Comments (1)
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
evyatron
Feb 24, 2023 09:05
I'm seeing the same issue in 2021.3.0f1, whether the Scene View is hidden or not.
Looking at the profiler it seems to come from UpdateAllMenus - AttributeHelper.ExtractCreateAssetMenuItems() is called dozens of time, as well as Loading.readObject, Menu.FilterMenuItem, and AttributeHelper.GetComponentMenuOrdering.