Search Issue Tracker
Fixed in 7.1.1
Votes
0
Found in [Package]
6.9.1
Issue ID
1180459
Regression
Yes
[ShaderGraph] Shaders break when Editor version is upgraded
How to reproduce:
1. Open VM > Bug Attachments > '1180459-Shader-Graph-issue.zip' project in 2019.2.5f1 version
2. Reopen the attached '1180459-Shader-Graph-issue.zip' project in 2019.3.0a1 version
3. Observe the Scene View
Expected result: Shaders are properly applied to GameObjects
Actual result: Shaders are applied as pink textures to GameObjects
Reproducible with: 2019.3.0a1 (Shader Graph 5.2.3), 2019.3.0b3 (Shader Graph 7.0.1), 2020.1.0a4 (Shader Graph 7.0.1)
Not reproducible with: 2018.4.8f1 (ShaderGraph 4.1.0), 2019.2.5f1 (ShaderGraph 6.9.1)
Could not test: 2017.4 because Shader Graph is not introduced
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 (fix version 7.1.1):
This is fixed when upgrading to 7.1.1. Additional similar symptoms please re-file as new bugs.