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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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.