Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2020.2
2021.1
2021.2
2021.2.0a4
Issue ID
1309217
Regression
No
GetDefaultShader custom dependency does not update correctly when adding a shader named Standard in the project
How to reproduce:
1. Download the "ShaderDependencyName.zip" project
2. Remove the "Library" folder
3. Open the project
4. Right-click on the "aa" asset and click "Reimport"
Actual result: The material change to the local Standard shader instead of the built-in
Expected: The local Standard shader is used when importing the project
Reproducible with - 2020.2.1f1, 2021.1.0b3, 2021.2.0a3
Could not test (errors) - 2018.4, 2019.4
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 2022.2):
Fixed in 2022.2.0a3