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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment