Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.3.X
Votes
0
Found in
6000.0.61f1
6000.2.8f1
6000.3.0b8
Issue ID
UUM-125367
Regression
No
VFX is displayed incorrectly in the first frame when played after saving the VFX Graph
How to reproduce:
1. Open the attached project "VFXGraphError"
2. Open the "VFX" scene
3. Select the "GanzSeModularHeroKit" GameObject
4. On the Visual Effect Overlay click "Play" and observe the results
5. Open the attached to GameObject VFX Graph "CharacterDeath" next to the Scene view
6. Press Ctlr + S/Command + S to save the VFX graph
7. Observe the played VFX Graph in the Scene view
Expected results: The first frame of the Visual Effect is the same in both cases
Actual results: The first frame is different and wrong when Visual Effect is played after the saving
Reproducible with: 6000.0.61f1, 6000.2.8f1, 6000.3.0b8
Not reproducible with: 6000.4.0a3
Reproducible on: macOS Sequoia 15.6 (M1)
Not reproducible on: No other environment tested
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (6000.3.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.