Search Issue Tracker
Fixed in 2021.3.17f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment