Search Issue Tracker
Fixed
Fixed in 2023.1.0b8, 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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment