Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2023.1.0a1
Issue ID
UUM-537
Regression
No
[VFX] Unexpected behavior after call of Renderer.material
Any access to `gameObject.GetComponent<Renderer>().material` will make the VisualEffect oddly behaves.
Step to repro:
- Import Repro_Material.unitypackage (the scene uses HDRP but the repro is compatible with URP)
- Enter in PlayMode
- Observe the color of the VFX evolving
- Click on the boolean "repro_issue" in inspector of the custom monobehavior
- Observe the color stopping to evolve
Expected:
- The color continue to evolve
Tested with 2022.1b12 & 2022.2.0a8
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 material behavior is tricky with VFXRenderer, the object is mainly handled by C++
If you want to modify the actual content of a material, I advice directly modify the sharedMaterial (being aware it can be shared between several instances).
Moving the ownership to user in VFX isn't planned yet but I are considering behavior improvement.
Resolution Note (2023.1.X):
The material behavior is tricky with VFXRenderer, the object is mainly handled by C++
If you want to modify the actual content of a material, I advice directly modify the sharedMaterial (being aware it can be shared between several instances).
Moving the ownership to user in VFX isn't planned yet but I are considering behavior improvement.