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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
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