Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4
2019.4
2020.2.7f1
2020.3
2021.1
2021.2
Issue ID
1324025
Regression
No
[Assetbundles] Shader keyword is lost in Build when Shader is in different AssetBundle than Material
How to reproduce:
1. Open the user's attached "Bug Test" project
2. Open the "bootstrap" Scene
3. Enter the Play Mode and inspect the circles in the Game View
4. Open the build ("Bug Test.exe") found in the "LocalBuild" folder
5. Observe the circles
Expected results: In the build on circles is red the other is green just like in the Editor
Actual results: Both circles in the build are red
Reproducible with: 2018.4.33f1, 2019.4.23f1, 2020.3.2f1, 2021.1.1f1, 2021.2.0a11
-
TJHeuvel-net
Mar 25, 2021 16:50
Note this is most likely an issue with addressables too.
One workaround is to make a ShaderVariantCollection, and include the variants that you use in there. However tracking what is used is also quite difficult, and the builtin `Save to Asset` tool doesnt work well with async shader loading.
Quite a hassle!
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
- TransformAccessArray.Add behaves differently when the argument is null and the argument is an int
- [iOS] App crashes when trying to use WebCamTexture depth data on back triple camera
- [Mobile] Only second base Camera out of two base Cameras with priority 1 and -1 is rendered in the Player
- 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
Resolution Note:
This is fixed in the Scriptable build pipeline package and is intended to replace the native asset bundle build pipeline.