Search Issue Tracker
Fixed
Fixed in 2022.3.7f1, 2023.1.9f1, 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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment