Search Issue Tracker
Fixed
Fixed in 2021.3.17f1, 2022.2.6f1, 2023.1.0a25
Votes
0
Found in
2021.3.13f1
2022.1.22f1
2022.2.0b13
2023.1.0a18
Issue ID
UUM-20083
Regression
Yes
GPU Usage Hierarchy columns in the Profiler window change when scripts are recompiled
Steps to reproduce:
1. Open the user’s attached project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Open Window > Analysis > Profiler
4. Enable GPU Usage Profiler Module
5. Enter Play Mode
6. Observe the Hierarchy of the GPU Usage
7. Expand the Hierarchy and select an element (e.g. search and select the “SSAO“ element)
8. Open the “Assets/DummyBehaviour.cs“ script and modify it
9. Wait for the scripts to reload
10. Observe the Hierarchy of the GPU Usage
Expected result: The Hierarchy columns are the same
Actual result: After scripts are recompiled the Hierarchy columns change
Reproducible with: 2021.1.0a6, 2021.1.28f1, 2021.3.13f1, 2022.1.22f1, 2022.2.0b13, 2023.1.0a18
Not reproducible with: 2020.3.41f1, 2021.1.0a5
Reproducible on: Windows 10
Note: Look at the attached video (“Hierarchy.mp4“) for clarity
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment