Search Issue Tracker
Fixed in 2023.1.0b8
Fixed in 2023.1.X, 2023.2.X, 2023.2.0a5
Votes
0
Found in
2023.1.0b4
2023.2.0a2
Issue ID
UUM-27023
Regression
Yes
The "GPU Usage" module shows no info when Profiler recording is enabled
Reproduction steps:
1. Open the attached “Test Project” project
2. Open the “Egyptian_Temple/DEMO” Scene
3. Enter Play Mode
4. Open the Profiler window
5. Add the “GPU Usage” module in the Profiler
6. Start recording and end it after a few seconds
7. Press on the “GPU Usage” Frame Chart in any frame
Expected result: “GPU Usage Detail Panel” Hierarchy shows “Total”, “DrawCalls” and “GPU ms” with some values
Actual result: “GPU Usage Detail Panel” Hierarchy shows “Total”, “DrawCalls” and “GPU ms” with 0.0
Reproducible with: 2023.1.0b1, 2023.1.0b4, 2023.2.0a2
Not reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.7f1, 2023.1.0a26
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment