Search Issue Tracker
In Progress
Fixed in 2021.3.17f1, 2023.1.0a25
Fix In Review for 2022.2.6f1
Votes
1
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
- [HDRP] Decal Projector with layer mask "nothing" doesn't affect transparent objects when Decal Layers are disabled in frame settings
- "MonoBehaviour.OnApplicationQuit" is still called when quitting is canceled by “Application.wantsToQuit“ returning false
- [2D SG/VFX] Surface options are not shown in Output Inspector when 2D Sprite SG is assigned to VFX
- Collisions are incorrectly registered when setting a joint motor every frame causes
- Terrain shadows flicker while moving the Camera in the Player when Terrain contains GPU instanced materials
Add comment