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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment