Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.2.0a3
2018.2.0a8
Issue ID
1023982
Regression
Yes
[LWRP] Multiple Shader and missing directive errors occur on launch
Multiple Shader and missing directive errors occur on launching lightweight template as render-pipelines.lightweight and shadergraph package is not updated
Steps to Repo:
1. Launch unity with the lightweight template
2. Observe there are multiple shader and missing directive errors
3. Go to file > player settings > other settings
4. checkmark allow unsafe code property
5. Window > package manager
6. Update lightweight template
7. Observe console for multiple shader errors
8. Restart the editor or clear errors
9. observe that the shader errors are disappeared and new errors appear
9. Update the shader graph package
Expected Result:
1. The lightweight template should launch without any errors
2. Proper warnings and messages should be given to the user
3. The template should be ready to use
Occurring with:
2018.2.0a8, 2018.2.0a3
Working with:
2018.1.0b13, 2018.1.0b5
Note that templates are available 2018.1.0b5 and 2018.2.0a3 onwards
Environment:
Windows 10, Mac 10.13
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
Add comment