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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a2