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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
Add comment