Search Issue Tracker
Fixed
Fixed in 2022.3.38f1, 2023.2.X
Votes
3
Found in
2022.3.24f1
2023.2.18f1
Issue ID
UUM-71300
Regression
Yes
VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
Reproduction steps:
1. Open the attached “IL2CPP_Crash.zip” Project
2. Open the “VFXScene” scene (Assets > VFXGraphBug)
3. Enter the Play mode
4. Select the “Test” GameObject in the Hierarchy
5. In the Inspector toggle the “Play BB Sequentially” property at least a few times
Expected result: Two instances of the same effect are visible
Actual result: One of the effects stops playing immediately, leaving only one effect visible
Reproducible with: 2022.2.0b4, 2022.3.24f1, 2023.2.18f1, 2023.3.0a19
Not reproducible with: 2021.3.37f1, 2022.2.0b3, 6000.0.0b14
Fixed in: 2023.3.0b1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- In between toggling the “Play BB Sequentially” property, make sure to wait for the effects to be inactive before toggling it again, for the best reproduction results. The issue also usually reproduces only after the toggle has been toggled twice
- The gizmo of the stopped effect is still shown after the effect has stopped being rendered
- Upgrading from 2021.3 (or from any working version) to any other version (except for beta and some alfa versions), makes the issue not reproducible on versions where it reproduced when upgrading from 2022.3.24f1
Comments (1)
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
wjamesfl
May 18, 2024 14:44
Experiencing this issue on 2022.3.13f1 as well. I had to disable instancing on the effect to get around this issue. I also noticed, if you disable and re-enable the GameObject of first effect that stopped rendering in play mode, it starts rendering again and both effects render properly.
This appears to be related to instancing. With instancing disabled on the VFX Graph, this does not happen for me.