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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment