Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X, 2022.1.X
Votes
0
Found in
2020.2.0a15
2020.3
2021.2
2022.1
Issue ID
1382934
Regression
Yes
The Profiler Rendering module shows the Scene rendering statistics as zero when profiling the Editor
How to reproduce:
1. Open the attached project "ProfTest"
2. Open the scene "PreviewBundle" (Assets/Preview Bundle.unity)
3. Open the Game view window (Window > General > Game)
4. Open the Profiler window (Window > Analysis > Profiler)
5. Expand the Target Selection drop-down and select "Editor"
6. Click on the Rendering Profiler module
7. In the Module details pane, inspect the values of SetPass Calls, Draw Calls, Total Batches, Tris, Verts
Expected result: The values are shown as non-zero
Actual result: The values are shown as 0
Reproducible with: 2020.2.0a15, 2020.3.24f1, 2021.2.4f1, 2022.1.0a16
Not reproducible with: 2019.4.33f1, 2020.2.0a14
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mesh.GetIndexBuffer() requires Mesh's 'Read/Write' flag to be enabled to get its index buffer data in Builds
- [Backport] [Sprite Atlas V1] Editor crashes when calling SpriteAtlasUtility.PackAtlases
- Deterministic builds have different files when built from the same project
- PlayerBuildInterface.ExtraTypesProvider no longer provides types to IL2CPP
- Touch input is reset in Device Simulator when Unity Remote is killed
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a4
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b10
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.14f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.31f1