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
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a3