Search Issue Tracker
Fixed in 5.2.1
Votes
0
Found in
5.0.2p1
Issue ID
699695
Regression
No
Profiler missing statistics of manually rendered camera
How to reproduce:
1. Open attached project
2. Open scene main.unity
- Scene contains some cubes and two cameras. One camera renders the UI and the other camera renders the 3D space. The 3D camera is disabled, but its rendering is called through a script, using Camera.Render()
3. Play the scene
4. Open the Profiler window
- Note how there is only a small number of Draw Calls in the Rendering profiler
5. Enable the Camera Component in the 3D-Camera gameobject
- Note how there is now a huge amount of Draw Calls shown
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
- Sprite Atlas results in suboptimal packing even when "Allow Rotation" is enabled
- References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
- "ShadowCaster2D" Component doesn't work when the "Casting Source" is set to "Polygon Collider 2D"
Add comment