LWRP shaders cost 80MB size

This doesn't seem too unusual, we have added a few shader variants back in lately, this is the downside of having one 'Uber' shader that attempts to cover everything.

What would help us though is to get the variant count you are hitting, or even the output of the variants. You can do this by finding the shader(LightweightStandard in this case) in your project window, it'll be under packages if you search for it, then click the drop down arrow by the 'Compiled code', make sure 'Current Build Platform' and 'Skip unused shader_features' are ticked.


(Example from my project, tbf it doesn't have many materials so it have a very low variant count)
You will then see the number of variants that are needed for your game, if you click show, a file with a list of variants will be created.

 

This is interesting, are you sure the build targets/graphics APIs were the same between builds? Going based off what you are getting in the editor vs cloud build it's definitely not lining up, potentially we have a bug there where is it missing the shader stripping process.

I'll get back here about it once I've learned some more, I'll flag it up with the build team.

 

@LeGiangAnh Can you PM me a link to your cloud build project?

 

Thanks, this is an unacceptably large amount(so is 80 tbf), I will have a look at this today and see if there is something that can be done.

 

Hey All,

Just wanting to give an update on this saying that we are still looking at reducing variants where we can, I would like to know what people are experiencing with the newer packages as we have cut down the amount now in 5.2.1 which is the latest LWRP.

One thing to check is to make sure you don't have any settings enabled on the pipeline asset you are not intending to use, this will add to the combinations of shaders that need to be compiled, also double check if you need all the graphics APIs that are in the PlayerSettings.