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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment