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
- An image bleeds out of the borders of a Mask when the project is opened with the iOS Build Support module
- Shadows do not appear on the Material with a custom shader which uses screen space shadow map in HDRP when Ray Traced Shadows are enabled
- An emoji is not shown in the UI Builder Viewport and the Game view when it is placed in the Labels text attribute and Usage Hints is set to Dynamic Color
- The Sprite Renderers are looking for Secondary Textures from the wrong page within the Sprite Atlas when the Sprite Atlas has a large amount of textures for packing
- [URP] Invalid update of shader stripping settings
Add comment