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
Comments (1)
-
shubhamswaraj2021
Aug 19, 2020 13:35
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
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.