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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.