Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
0
Found in
2018.4
2019.4
2020.1
2020.2
2021.1
2021.1.0a7
Issue ID
1297800
Regression
No
Global Shader keyword limit is reached when Fallback Shader adds local keywords to the list on Build
How to reproduce:
1. Open the user's attached "ShaderLocalKeywordBuild.zip" project
2. Open the "SampleScene" Scene
3. Go to File -> Build Settings
4. Press the "Build" button in the Build Settings
5. Observe the Console log
Expected result: No errors are thrown in the Console log
Actual result: "Maximum number (256) of shader global keywords exceeded, keyword TEST_A_3 will be ignored." error message is thrown in the Console log
Reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a9
Note:
- Commenting out the Fallback lines in the Shaders, the errors go away
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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a5
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.2f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.18f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.24f1