Question Post Processing with Builtin, question...

Sorry for asking this here. Couldn't find a section for Post Processing.

If this is the wrong spot, please feel free to move:

Layers are mentioned for the Volume... for post processing. The docs read confusingly, for me:

https://docs.unity3d.com/Packages/com.unity.postprocessing@3.2/manual/Quick-start.html

Are the layers used for the Volume a hit detection thing (like how physics treats layer interactions by masking), or are the layers those (and only those) that the Post Processing is applied to AND the means by which volume detection is being done?

And what is the purpose of the volumes? Is this a depth thing... like "do post processing to the depth of the volume and not deeper, nor shallower" somewhat akin to the manner that clipping planes operate?

 

Thank you!!

Not only is it tricky to find... it's a ghost town...

Someone asked a similar question in September. No answer.

 

Whilst it's more specific, the bottom line is that this user is suffering the same conceptual problem I'm having, which is what are "layers" in the context of post processing?

https://forum.unity.com/threads/post-processing-affects-all-layers.1337822/

 

If I had any doubt that Unity would Unificate™ the post processing practices and paradigms, these just blew that away. And the docs leave me with me with more questions than answers, true to form... for Unity.

I'm worse in person. Far worse.

Why do both vCams (CMCams) and Volumes co-exist with Post Processing Profiles*? Which one trumps the other? Why?

I had to go look up, somewhere else, what a Post Processing Profile is because these docs don't self explain, nor link to what this is. It's the single most important aspect of Post Processing in Unity, and is not capitalised in the docs you linked to, when it's first introduced. and it's never ever more than "introduced" in these docs.

Post Processing Profiles continue the absolutely impeccable naming conventions of Unity.

They are the stacks of effects that any Volume* causes to occur through any camera** active within its bounds***.

*region in which Post Processing occurs

**doesn't have to be a camera that triggers this... can be any game object within the bounds. Probably just for kicks.

***regions can overlap, and strengths of influence can be by distance FROM a region... too. Just for more kicks, I suppose.

 

I was a little worried that there'd be some energy lost on the SRP thought experiment, so I tried to made it clear, in the title of this thread, this about Builtin.

I understand Unity still heavily promotes using SRP... I don't know why. Nobody that's tried them knows why.

And don't know anyone sane using SRP renderers.

 

Argh... testing reveals there is (seemingly) cumulative interplay between the Volume Profile settings and CM Post Processing Profiles.

IOW: Profiles on Volumes are not overridden by Profiles on vCams, they're compounded. Or summed.