Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
0
Found in
2021.2.0a16
2021.2.1f1
2022.1
Issue ID
1380745
Regression
Yes
Shader Keywords array always returns 0 length when keywords are visible in the Inspector
Reproduction steps:
1. Open the '1380745-sample' project
2. Open the 'test' Scene
3. Select the testMaterial and observe it in the Inspector in the Debug mode; note that there is a Shader Keyword 'test_keyword'
4. Observe the Console; the 'test' script prints the lengths of the Shader Keywords array
Expected result: the printed Shader Keywords array length is 1
Actual result: the printed length is always 0
Reproducible with: 2021.2.0a16, 2021.2.3f1, 2022.1.0a15
Not reproducible with: 2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.0a15
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a8
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b14
Resolution Note (fix version 2021.2):
Fixed in 2021.2.18f1