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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
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.