Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
Issue ID
396476
Regression
No
Draw calls not being reclaimed from deactivated objects
Shouldn't the draw calls with de-activated Water3 be the same as not having Water3 at all? To test this...
- Open the scene and add 3 cubes.
- Play the scene; You will see the draw calls jump between 4 (innactive
water) and 6 (active water).
- Go back to the hierarchy and deactivate both Water3 and the script attached to the main camera
- Play the scene; Only 1 draw call with innactive Water3.
- During play, activate the script on the camera. The draw calls will jump to 4 during the "innactive" GO state.
- You may activate/deactivate whatever, you will never get back the 1 draw call the cubes should be rendering without Water3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment