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 block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
- The construction of a specific class breaks the binding Bool references and does not allow them to be toggled on back by hand when working in the Custom Editor window
- AssetReferenceAtlasedSprite creates a copy of the Sprite during Addressables.LoadAssetAsync<TObject> which does not release when Addressables.Release is used
- Crash on TryToRegisterMonoScriptToHashMap when importing a specific .unitypackage
Add comment