Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3
2021.1
2021.1.1f1
2021.2
Issue ID
1326825
Regression
No
Editor Performance significantly degraded when Character is moving while selected by the Inspector
Reproduction steps:
1. Open user attached Project
2. Open Assets\Scenes\SampleScene
3. Enter Playmode
4. Move the character around using WASD and note the Framerate
5. Select the "Player" game object in the Hierarchy and have an Inspector open
6. Move the character around with WASD and note the Framerate
Expected result: The Framerate is relatively the same
Actual result: The Framerate goes from ~140(8ms) to ~30(35ms)
Reproducible with: 2020.3.5f1, 2021.1.3f1, 2021.2.0a14
Could not test with: 2018.4, 2019.4 (Project breaks)
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 (2022.1.X):
IMGUI performance improvements (other than fixing regressions) are out of scope for the foreseeable future.