Search Issue Tracker
Fixed
Fixed in 2021.3.35f1, 2022.3.18f1, 2023.3.0b1, 7000.0.0a1
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment