Shaders targeting multiple pipelines are now broken in 2019.3?

Before 2019.3, we could write a shader with several SubShader sections using the "RenderPipeline" tag so same shader can work for built-in and for other pipelines.

Example:

SubShader {
Tags { "RenderPipeline" = "" }
Pass {
// this pass only get executed in built-in
...
SubShader {
Tags { "RenderPipeline" = "LightweightPipeline" }
Pass {
// this pass only get executed in LWRP
...

Now, after updating to 2019.3, these shaders no longer work.
I wonder if there's a different syntax or if it's a breaking change.
Any advice? /cc @Tim-C @phil_lira

 

Related bug: https://issuetracker.unity3d.com/is...r-when-its-subshader-has-a-tag-renderpipeline

 

Thanks Tim.

What would be the recommended way to reference each pipeline option?

Currently we have:

No Render Pipeline tag: this could be an unlit shader that works perfectly on both built-in and URP.
"RenderPipeline" = "": this means the shader works only for built-in.
"RenderPipeline" = "UniversalPipeline" : only URP.

Is this correct?

 

Hey @Tim-C,

What's the status of the implementation of the above?
Currently, any shader with "RenderPipeline"="" is not rendered as of Unity 2019.3.2f1 in builtin.
Removing the tag, makes it work again, but then, it will also render in URP which is not what I want.

 

Thank you Tim. I appreciate your fast response and glad to see the fix coming.

I found a workround that seems to work although I prefer the fix obviously. The workaround works by moving the subshader with the RenderPipeline tag = "" below the subshader for URP. As the system seems to pick the first one compatible with the platform, this seems to do the trick.