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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.