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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment