Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2
2019.2.9f1
2019.3
Issue ID
1191820
Regression
Yes
Keyword is discarded and error is thrown to the Console when shader keywords are replaced
How to reproduce:
1. Open the attached '1191820.zip' project
2. Open 'NewSurfaceShader.shader' shader
3. Notice that the number of keywords remains at 64
4. Replace 'x1' shader keyword to 'a1' shader keyword and save the shader
Expected result: Keywords are replaced and no error thrown to the Console
Actual result: Error is thrown to the Console that 'Maximum number (64) of shader local keywords exceeded, keyword x1 will be ignored.' and a keyword is discarded
Reproducible with: 2019.2.16f1, 2019.3.0f3
Not reproducible with: 2017.4.35f1, 2018.4.14f1, 2020.1.0a16
Notes:
- Screenshot and project of reproduction attached in Edit
- Local shader keywords are limited to 64 keywords per project while documentation states that it is limited to 64 keywords per shader. Any additional keyword is discarded.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a2