Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.6.0b3
Issue ID
867627
Regression
Yes
[Regression] Incorrect terrain Inspector warning after assigning material with Nature/Terrain/Standard shader to terrain
Steps to repro:
1. Open attached owncloud project and 't1' scene;
2. Select Terrain gameobject in the Hierarchy;
3. Go to Terrain Settings tab in Terrain Inspector;
4. Observe 'Custom material' field.
Actual result:
Terrain shader warning is thrown even though assigned 'New Material' material has Nature/Terrain/Standard shader. See attached actual.png screenshot.
Regression introduced in Unity 5.6.
Expected result:
Terrain shader warning should not be thrown for custom material having any of Nature/Terrain shaders. See attached expected.png screenshot.
Notes:
- The bug is reproducible with baked terrain lightmaps under PVR backend; not reproducible under Enlighten baking backend;
- Reproducible in 5.6.0b3;
- Not reproducible in 5.5.0p1, 5.4.3f1;
- Reproducible on both OSX 10.12.1 and Windows 10;
- Reproducible only with Nature/Terrain/Standard shader; Not reproducible with Nature/Terrain/Specular and Nature/Terrain/Diffuse shaders;
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
Add comment