Missing a shader_feature when I BuildAssetBundles.

I always missing a shader_feature when I build assetbundle.

My shader and material are located in different assetbundles, and I use BuildPipeline.BuildAssetBundles to build them all. But each time I launch up by asset bundle, the shader sees wrong.

I dig into the FrameDebugger and find the shader_feature macro is not on, so I change the shader_feature into multi_compile, then everything is OK. It so odd, and I don't want to alway include the feature but want the Unity strip for me. And this keyword is existed in the material in another bundle, I check them existed in debug mode of inspector of that material.

Then I change to create a material, use that feature, and bundle it into the shader asset bundle, everything correct again!



I really want to know what the problem of the shader feature and AssetBundles. Is there any log I can turn on to watch how shader variable compile when I build asset bundle?



Thank you~

 

@alejandro-unity Is this problem related to this issue tracker post?: https://issuetracker.unity3d.com/is...ost-when-sharing-asset-bundles-during-runtime

I couldn't find any specific mentions of shader_feature in the what's new section, apart from specifics for the standard shader.

 

@alejandro-unity Do you have a release date for the new build pipeline?

 

@alejandro-unity I'm also looking for an update on this. We're running into this issue on 2017.3.1p1. Adding all the materials into the same bundle as our shaders includes all the textures as dependencies which doesn't work for us. We ship all the shaders in the streaming assets folder and download the textures from AWS.

Can you expand on the dummy materials option? I tried automatically generating materials per every shader in the bundle and adding all the keywords to this material but the shaders are still getting stripped.