Feedback Wanted: Scriptable Render Pipelines

[Grimreaper358]

@Kolyasisan

Yeah, really curious about how the SRP api is going to evolve, if at all. There are still tons of stuff that are just impossible to do with the SRP api, like overriding stencil values on a per-material basis or making a custom, per-renderer light assignment, or vanilla-unity forward multipass for lights. I really doubt that the majority of the black-boxed C++ rendering stuff can even be done in C#.

There are currently two stencil bits exposed to us.

https://github.com/Unity-Technologies/Graphics/blob/master/com.unity.render-pipelines.high-definition/Runtime/RenderPipeline/HDStencilUsage.cs

Which bits are used for what
https://github.com/Unity-Technologies/Graphics/blob/master/com.unity.render-pipelines.high-definition/Runtime/RenderPipeline/HDStencilUsage.cs.hlsl

Still a lot of work making it useful. This will most likely change with the Shader API update for both SRPs

There are big changes coming, to find out more read this post by the devs

What is next for us at Unity with Scriptable Render Pipelines

From the beginning, we developed the SRP architecture to solve several goals: Provide the most optimal pathways to take advantage of the fragmented hardware landscape and reach performance on those platforms Enable deep customizability of rendering paths in user land Enable content scalability across the entire platform reach of Unity We view the Universal render pipeline as the successor to the default rendering pipeline in Unity (aka the ‘built-in pipeline’). Universal RP is designed to be…