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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment