Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2020.3.21f1
2021.2
2022.1
Issue ID
1377675
Regression
No
No warnings are thrown when using multiple Shaders with duplicate internal names
How to reproduce:
1. Open the attached project (DuplicateShaderTest.zip)
2. In the Project window, under Assets, select the Material "Material"
3. In the Inspector window, observe the Shader selection drop-down menu
Expected result: the Editor prevents or warns against using duplicate internal Shader names
Actual result: the Material has two Shaders of the same internal name assigned, and no errors or warnings about duplication are thrown to the Console
Reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.2.5f1, 2022.1.0b1
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.2.X):
This is significantly more complicated than first anticipated due to legacy assumptions.
This has been moved to an internal tracker for future consideration.