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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment