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
Comments (1)
-
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This is fixed in the Scriptable build pipeline package and is intended to replace the native asset bundle build pipeline.