Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a1
2019.2.0a11
2019.3.0a1
Issue ID
1143087
Regression
Yes
Canvas: Removing normal from the Additional Shader Channel drop down causes rendering issues
Canvas does not display correctly when Normal is removed from the Additional Shader Channel in the canvas.
Steps to reproduce
- Open the main menu scene.
- Select MainMenu in the Hierarchy.
- In the inspector, under Cavas, find *Additional Shader Channel* drop down.
- Remove Normal from the drop down menu.
Notice issue >> The Canvas is rendered incorrectly.
Broken: 2019.2.0a11, 2019.2.0a1, 2019.2.0a2
Working: 2019.1.0b6, 2019.1.0b10
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.3):
GFX buffers implementation changed. The buffer stride size was no longer being respected so need to recreate the buffer if the stride changes.