Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3.0a8
2019.3.0f3
2020.1
Issue ID
1209147
Regression
Yes
Local Shader Keywords are not used in Editor when loaded from AssetBundles
How to reproduce:
1. Open "SampleScene" from "LocalKeyword_1_6.zip"
2. Set "Play Mode Script" to "Use Existing Build" in Window>Asset Management>Addressables>Groups
3. Build Player Content
4. Start Play mode
5. Observe the colors of cubes
Expected result: Both cubes are red
Actual result: Right cube is white
Reproducible with: 2019.3.0a8, 2019.3.1f1, 2020.1.0a22
Not reproducible with: 2019.2.21f1, 2019.3.0a7
Could not test with: 2017.4 and 2018.4 - local keywords not supported
Notes:
1. Works correctly in standalone build
2. All keywords remain defined in material but not used when checked using Frame Debugger
3. Affects both shader_feature_local and multi_compile_local, even with "Skip unused shader_features" disabled
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
- [Android] The warning "Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak" is displayed when ShaderVariantCollection.WarmUp is called
- RectangleContainsScreenPoint returns false for some points even when the points are in the rectangle
- [iOS] Stacked camera does not render when using post effects
- TextField cannot be edited in an extended Editor window when double-clicking it
- [VisionOS] visionos build do not add plugin or frameworks
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a4
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.4f1
Resolution Note (fix version 2019.3):
Fixed in 2019.3.8f1