Search Issue Tracker
Fixed
Fixed in 6000.6.0a7
Under Consideration for 6000.4.X, 6000.5.X
Votes
0
Found in
6000.0.69f1
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a1
Issue ID
UUM-138375
Regression
No
VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
How to reproduce:
1. Open the "IN-137652" project
2. Open the "TestScene" scene
3. Right-click the Game window's tab header
4. Click “Load RenderDoc”
5. Click "Capture the current view and open in RenderDoc" button in the Game window
6. Double click on the capture in RenderDoc
7. Filter for "RenderLoop.Draw"
8. Expand both children titled "VFX.ParticleSystem.RenderMeshIndirect"
9. Observe the value in "ExecuteIndirect → IndirectDrawIndexed"
Actual result: One instance shows IndirectDrawIndexed<36, 1000>, the other shows IndirectDrawIndexed<36, 118>
Expected result: Both instances show a value less than 1000
Reproducible with: 6000.0.10f1 (413673acabac), 6000.0.71f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b1, 6000.6.0a1
Could not test with: 2023.1.0a10, 6000.0.0b11 (a707ca4efec4) (Visual Effect Graph warnings and Visual Effect not rendering)
Reproducible on: Windows 10
Not reproducible on: No other environments tested
Note: Does not reproduce on HDRP
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note:
Fixed in 6000.6.0a7
Resolution Note (fix version 6000.6.0a7):
Fixed in 6000.6.0a7