Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2021.3.5f1
2022.2.0a17
2023.1.0a2
Issue ID
UUM-543
Regression
No
Experimental Shader Externalization is not working when copying code from one Visual Effect to the other
How to reproduce:
1. Open the user attached "VfxGraph Debug.zip" project
2. Reimport the "VFX1" Asset found in the Assets/ISS folder
3. Open the Game View
Expected result: The VFX GameObjects are the same
Actual result: The VFX1 GameObject is different from the VFX2 GameObject
Reproducible with: 10.3.2 (2020.3.0f1), 10.8.1 (2020.3.30f1), 12.1.5 (2021.2.14f1), 13.1.6 (2022.1.0b10), 14.0.0 (2022.2.0a7)
Couldn't test with: 7.7.1 (2019.4.36f1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Shader externalization cannot be fixed easily now but the use case was to be able to add pragma in generated shaders for debug symbols. Some toggles were directly added in VFX Graph to allow that directly without hvaing to patch the shaders. https://jira.unity3d.com/browse/UUM-19517
Resolution Note (2023.1.X):
Shader externalization cannot be fixed easily now but the use case was to be able to add pragma in generated shaders for debug symbols. Some toggles were directly added in VFX Graph to allow that directly without hvaing to patch the shaders. https://jira.unity3d.com/browse/UUM-19517