Search Issue Tracker
Fixed in 2022.3.7f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a23
Votes
0
Found in
2022.3.3f1
2023.1.1f1
2023.2.0a20
Issue ID
UUM-41136
Regression
No
[VFX] Failure to cull VFX commands when no renderer in the CullResults
Camera command culling fails when no VFX are visible in the camera frustum.
How to reproduce :
- Create a scene with one default VFX, two cameras, and no lights
- Move one of the cameras such that the VFX bounds are completely outside the camera frustum.
- Enter Play Mode
- Open the profiler, start profiling.
- Find the VFX.ProcessCamera marker
- Observe that both cameras emit BatchUpdate and SortBuffer commands. (FillIndirectRenderArgs is ok)
Expected result : Only the camera where the VFX is visible should emit the BatchUpdate and SortBuffer commands.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment