Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.4f1
2019.1.0a1
2019.2.0a1
Issue ID
1124610
Regression
No
Default Shader can be changed when assigning to Material.shader from code
Reproduction steps:
1. Open the "SampleScene" in the attached "DefaultMaterialShaderBug.zip" project
2. Make sure that the "Sprites-Default" material with "Sprites/Default" Shader is present on the "New Sprite" GameObject"
3. Enter Play Mode
4. Observe the Shader field on the "New Sprite" material
Expected Behavior: The Shader field is not changed as it is a Default shader
Actual Behavior: The Shader field is changed
Reproducible with: 2017.4.20f1, 2018.3.5f1, 2019.1.0b3, 2019.2.0a4
Note: The Default Material is grayed out and can not be changed via the editor
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note:
Fixing this functionality would create a big overload on the editor. That would introduce new performance issues.
The Shader on a Default Material is not saved and it resets after reloading the project.