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
- Crash on FindNearestVertex when objectsToSearch array contains a null transform
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
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.