Search Issue Tracker
By Design
Votes
10
Found in
2019.2.0a8
2019.3
2019.3.0b8
2020.1
Issue ID
1193781
Regression
Yes
Custom shader doesn't override built-in terrain shader
How to reproduce:
1. Open the attached '1193781-shader-override-issue.zip' project
2. Open 'SampleScene' Scene
3. Inspect 'Standard-FirstPass' shader
4. Notice that shader's name is Shader "Nature/Terrain/Standard"
5. Notice that 'Default-Terrain-Standard' shader is assigned to 'Terrain-standard' GameObject
Expected result: Built-in shader is overridden and 'Terrain-standard' GameObject is red
Actual result: Built-in shader is not overridden and 'Terrain-standard' GameObject is grey
Reproducible with: 2019.2.0a8, 2019.2.11f1, 2019.3.0f3, 2020.1.0a16
Not reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.2.0a7
Note: Video and project of reproduction are attached in Edit
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
- Visual C# Compiler cannot find source files because it is looking at old file locations
- Ghost empty folders are left behind when after calling Refresh, Directory.Move is called
- [OSX] The Scene icon in the Unity Editor's title bar can be dragged and dropped out of the project
- [Metal][Editor] Memory grows continuously until Editor crashes when importing 100k materials
- Investigate why .meta files are sometimes not parsed right
Resolution Note (fix version ):
Nowadays terrain references shader via standard asset referencing so there won't be any more same-name shader overriding mechanism. If user wants to override the terrain shader, he should be able to just create a new material, referencing the new shader and assign the material to the terrain.