Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.2.18f1
2022.1.0b13
2022.2.0a9
Issue ID
UUM-3417
Regression
Yes
Unity Editor frame rate drops when making many successive inputs
Reproduction steps:
1. Create a new 3D Unity project
2. Open the Profiler (Window -> Analysis -> Profiler)
3. Change the Profiler window to record Editor performance
4. Start pressing the keyboard buttons rapidly
Expected result: Consistent and stable performance
Actual result: Performance degradation
Reproducible with: 2021.2.0a16, 2021.2.18f1, 2022.1.0b13, 2022.2.0a9
Not reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.0a15
Note:
- To document the degradation of performance the FPS metric in the Profiler was used
- 2019.4 and 2020.3 at the lowest went to 100FPS whereas later streams went as low as 60FPS and rarely to 30FPS
- Reproduction is somewhat inconsistent, to reproduce do step 4. then promptly stop and start step 4. again, doing this in intervals helps with reproduction
Comments (1)
-
Pheck
Mar 21, 2022 17:52
We see this issue in our production project and in clean projects. It generates about a 130ms spike for us when we press a key in our production project and a 3ms spike in a clean project. The same input event from a gamepad does NOT cause this issue in either project.
"Max Frame Rate" in nvidia has nothing to do with the repro for us.This issue is currently a major problem for us in the editor as we cant test with keyboard without major perf spikes.
We are using 2020.3.26f1 win10
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
The customer who reported this issue says it no longer represents a problem starting from 2020.3.32f1 and onward. Other reported cases differ sufficiently to be considered as a separate bug, with different reproduction steps.