Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.2
2019.2.10f1
2019.3
2020.1
Issue ID
1202968
Regression
No
"IPreprocessShaders.OnProcessShader" doesn't work with "multi_compile_local" variants
Reproduction steps:
1. Open "New Unity Project (12).zip" project
2. Build for Android
3. Look at the Console output
Expected Result: "F00000000000_ON" and "F000000000_OFF" are outputted
Actual Result: "F00000000000_ON" and "F000000000_OFF" are not outputted
Reproduced with: 2020.1.0a15, 2019.3.0f2, 2019.2.16f1, 2018.4.14f1
Could not reproduce on: 2017.4.35f1(Scripting errors)
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note:
This is by desing, function that u are using `keys[j].GetKeywordName()` is only works for global keywords.
In 2020.1 we added new functions `ShaderKeyword.GetKeywordName(Shader, ShaderKeyword)` and `ShaderKeyword.GetGlobalKeywordName(ShaderKeyword)` where `keys[j].GetKeywordName()` is deprecated. The reason we needed new functions, as local keyword names can only be resolved if shader is known in context.