Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a12
2019.2.0a1
Issue ID
1113522
Regression
Yes
Shader and a shader category both get ticked on the material shader selection drop down if they have the same name
How to reproduce:
1. Open the "case_1113522-ShaderSelection" project
2. Open the "Unlit" material in the inspector and open the shader selection drop down menu
Expected results: Only the Unlit shader is ticked
Actual results: Both the Unlit shader and the Unlit category are ticked
Reproducible with: 2019.1.0a12, 2019.1.0a14, 2019.2.0a1
Not reproducible with: 2017.4.18f1, 2018.3.3f1, 2019.1.0a11
---------------------------------------------------------------------------------------
Fixed in: 2019.1.0b5, 2019.2.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment