Search Issue Tracker
Fixed
Fixed in 2022.3.65f1, 6000.0.55f1, 6000.1.14f1, 6000.2.0b11, 6000.3.0a1
Votes
0
Found in
6000.2.0a7
Issue ID
UUM-99917
Regression
No
VFX are not reinit immediatly when changing properties in asset inspector
Steps to reproduce:
- Create a new VFX asset and instantiate in scene
- Select the VFX asset in project browser
- Change the instancing mode and culling flags in inspector
Actual results:
VFX instances are not always reinitialized correctly. And require manual user action to tick the editor update
Expected results:
VFX instances are always correctly reinitialized
Reproducible with versions: 6002.0a7
Not reproducible with versions: not tested
Can’t test with versions:
Tested on (OS): windows editor
Notes:
- This is most likely and issue with culling state and VFX reinit. The auto editor update is not triggered for some reason
- Notice that if you create another VFX asset + instance in scene, redoing the repro steps won't show the issue anymore because this instance will force the editor update
- Marked as not a regression but could be one
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:
Forward-ports for this version need to be handled at a later time.
Resolution Note (fix version 6000.3.0a1):
Editor: Fix VFX not repainted when changing some asset properties