Search Issue Tracker
Fixed in 2021.3.35f1
Fixed in 2021.3.X, 2022.3.X, 2023.3.X, 2023.3.0b1, future release
Votes
0
Found in
2021.3.33f1
2022.3.15f1
2023.2.3f1
2023.3.0a17
Issue ID
UUM-58128
Regression
Yes
The Rendering Profiler module statistics are zero when Application.targetFrameRate is set
Reproduction steps:
1. Open the attached “BreakTheProfiler.zip” project
2. Open the Profiler window (Window > Analysis > Profiler)
3. Enter the Play mode
4. Observe the Rendering Profiler module in the Profiler window
Expected result: The Rendering Profiler module shows rendering statistics
Actual result: The Rendering Profiler module’s statistics are all zero
Reproducible with: 2021.3.6f1, 2021.3.33f1, 2022.3.15f1, 2023.2.3f1, 2023.3.0a17
Not reproducible with: 2021.3.5f1
Reproducible on: Windows 11, macOS 13.6.2 (M1 max)
Not reproducible on: No other environment tested
Note: Deleting the “Application.targetFrameRate = 30;” line in the “BreakTheProfiler.cs” script fixes the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment