Search Issue Tracker
By Design
Votes
0
Found in
2017.3.1f1
Issue ID
1023810
Regression
No
Unity shaders can define user-defined multi-line preprocessor directives but cannot use them and throws errors
How to reproduce:
1. Open tester's project (D3D11MultilineDefine.zip)
2. Observe the Console for shader errors
Expected result: No shader errors are thrown
Actual result: Unlit/MultilineDefine.shader throws an error at line 41 where the user tries to use a multiline preprocessor directive
Reproducible with: 5.6.6f1, 2017.1.3p3, 2017.2.2p3, 2017.3.2f1, 2017.4.1f1, 2018.1.0f1, 2018.2.0b1
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