Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.2f1
2023.2.0a22
Issue ID
UUM-42209
Regression
No
VFX Graph particles flicker when "Indirect Draw" is disabled and "Set Alive" is used
Reproduction steps:
1. Open the attached project "VfxGraphGraphicsBufferTest_02"
2. Open the "Test" scene
3. Observe the Game view (may need to be focused)
Expected result: all particles are consistently rendered
Actual result: the particles are flickering
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.2f1, 2023.2.0a22
Reproducible on: macOS 13.4.1 (Intel), macOS 13.4 (M1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The problematic graph was using VertexID to index a custom compute buffer, but the VFX graph issues instanced draw calls (by design), so the same VertexID is repeated multiple times.
To fix it, one could transfer the particleID attribute to the Shader Graph through an exposed property, and index the compute buffer based on it.
Resolution Note (2023.2.X):
The problematic graph was using VertexID to index a custom compute buffer, but the VFX graph issues instanced draw calls (by design), so the same VertexID is repeated multiple times.
To fix it, one could transfer the particleID attribute to the Shader Graph through an exposed property, and index the compute buffer based on it.