Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2022.2.0b3
2023.1.0a4
Issue ID
UUM-10474
Regression
No
Using UI Toolkit Default Inspectors results in performance degradation in the Inspector
Reproduction steps:
- Open the user attached project
- In the Assets folder press on “Hoge” asset
- Observe the Inspector
Expected result: Content in the Inspector is displayed instantly
Actual result: Content in the Inspector is slowly appearing
Reproducible with: 2022.2.0b3, 2023.1.0a4
Could not test with: 2020.3.37f1, 2021.3.7f1, 2022.1.12f1 (UI Toolkit default inspectors are not introduced)
Reproduced on: Windows 10
Note: the workaround for this issue is to switch by switching back to the IMGUI Default Inspector in Project Settings
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note:
This is indeed a regression in performance but we cannot fix this performance as a simple bug fix. The reason performance has regressed is because the default inspectors are now drawn using UI Toolkit instead of IMGUI. UI Toolkit has to actually new/allocate each element, layout and style them, before anything can be drawn. It's a framework approach choice that is optimized for all-frames-but-the-first-frame, which is...the majority of frames, but it suffers a bit on the first frame performance.
We did a lot of work to alleviate this issue on the regular GameObject components inspector to time-slice the generation of UI and make the first frame a lot snappier. But for a large single debug inspector, we can't do much yet.
With all that said, we are actively working on this performance problem in UI Toolkit and this regression should gradually diminish in future versions.
If this is a show-stopper for you, you can switch back to the IMGUI Default Inspector in the Project Settings, and continue working with that option enabled.
Resolution Note (2023.1.X):
This is indeed a regression in performance but we cannot fix this performance as a simple bug fix. The reason performance has regressed is because the default inspectors are now drawn using UI Toolkit instead of IMGUI. UI Toolkit has to actually new/allocate each element, layout and style them, before anything can be drawn. It's a framework approach choice that is optimized for all-frames-but-the-first-frame, which is...the majority of frames, but it suffers a bit on the first frame performance.
We did a lot of work to alleviate this issue on the regular GameObject components inspector to time-slice the generation of UI and make the first frame a lot snappier. But for a large single debug inspector, we can't do much yet.
With all that said, we are actively working on this performance problem in UI Toolkit and this regression should gradually diminish in future versions.
If this is a show-stopper for you, you can switch back to the IMGUI Default Inspector in the Project Settings, and continue working with that option enabled.