Official way to do custom post-processing with URP?

Now HDRP officially supports custom post-processing effects - what's the plan for URP?

Are custom renderers capable of doing this? If so - are there any guides as I'm not sure where to start?

If not - what's the plan?

 

Where did you get the information that the latest 2019.3 HDRP has official custom post processing method? Afaik, there is still no official way to do that yet? Or have I missed on some news?

 

https://docs.unity3d.com/Packages/c....high-definition@7.1/changelog/CHANGELOG.html

"Added Custom Post Processes with 3 injection points: Before Transparent, Before Post Process and After Post Process"

I did a quick test here to confirm it was working: https://github.com/IxxyXR/HDRP-Custom-Post-Processing-Test

 

Unity can you please clarify the official steps to do custom post effects? What on earth is going on?

 

just saw this,

"Custom post processes are back in #HDRP 7.1.1 + #Unity3d 2019.3!!! Integrated with the volume system. One must create script and shader templates and list the custom post processes inside the HDRP default settings."

https://twitter.com/the_f_key/status/1181489697278844928



*oops, missed that this was URP thread..

 

It will come to URP too

 

How do you know it will come to URP, and when?. Is this on a roadmap anywhere? I really need custom post processing on mobile VR, and at the moment I can't find a way to do that in Unity.

 

You should periodically check the branches and commits on the scriptable render pipeline GitHub if you’re in a rush. Could pop up there any day. Or it could be in a year. Who knows?

 

A bit confused over here too. The message seemed to point to the fact that URP is the new face LWRP and continue on it, but there seems to be an actual rewrite going on, I'm having a bunch of classes and extensions for QoL that I can't really find how to fix...
what happened to PropertySheet, ParameterOverride's, etc? Are they not available (or will-be-changed) for the time being?

 

After reading the above is it proper to say I should change my project back to standard mobile shaders and the post processing effects stack and or Blit effects if I want to do custom screen effects render passes for mobile devices?

 

For all things mobile where you have control of what to use, I would strongly suggest using Legacy Built-In pipeline... I'm stuck on it and have no leverage on deciding what to use.

Can you point us to that GitHub?
I don't fully get how URP works... can I choose LWRP and Post Processing Stack v2 on 2019.3? it's installed, but I just can't use it. The camera has changed completely and has post processing deeply embedded in it, seems to not accept Post Processing Volumes, just "Volumes" (the new ones).
There are many things with less features and/or broken, for example, Post Processing doesn't respect the alpha channel anymore no matter what, so rendering 3D with post processing and then UI with fewer ones (say, only bloom) makes it impossible to mix them together afterwards because the alpha channel will be forced to full-on even if it is told to clear to a fully transparent color.

 

@AlejUb https://github.com/Unity-Technologies/ScriptableRenderPipeline

If you're on 2019.3 you can either use URP or PostProcessing but not both. Ditch LWRP, it's not needed. URP replaces it. URP has its own version of PostProcessing but it's missing some important features. Unless you're starting a new project and aren't in any great rush for things such ambient occlusion then stick with the standard pipeline.

 

Wait, with custom render pass you can perform something very similar to old post process (in terms of results). It's just that the way to do pp is quite different than before, and it's only per command buffer.
Inside of this project: https://github.com/Unity-Technologies/UniversalRenderingExamples
you will find a Blit custom render pass, which is basically what any standard post process does.

 

I've suspected this to be the case but the lack of any official docs, comment or any examples from Unity has made it fairly unclear. The examples they do provide are quite specialist and the only comments have been "custom PP is not supported in URP" so it's not surprising that people have taken that statement at face value.

 

I totally agree! If I wasn't forced to support old pp for our project (recently converted in URP) I wouldn't have bothered. And it took me 2 days to convert a simple motion blur pp...

 

I gave up after getting builds working with the new pipelines. Nothing is stable or well documented and its more complex then it needs to be. So im back to learning the previous system cause it most resembles other systems in gl I have worked with with the Custom Buffers, but I still need to figure out its workflow still

 

Use ScriptableRenderPass for custom post processing
See this unity urp example https://github.com/Unity-Technologies/UniversalRenderingExamples.git

 

PP2 will supportg 2019.3,see here.
https://forum.unity.com/threads/post-processing-and-urp-the-plan.795456/#post-5341926

 

neat but looks like the deprecate the same year. NOT promising

 

SRP URP PPv3 HDRP PPv2
Ya dont say

 

Is custom post-processing officially supported?
I may have overlooked some information, but I would like to know the progress.

 

I have to say that it's indeed not clear, but my current understanding is that custom pp can be done with RenderFeature implementation. Don't quote me. I will try to do something in the next few days.

 

I've been able to create some custom URP post process on 2019.3 adding some render features
...but the very same code and system it's not working on unity 2020.1.6

Quite annoying I must say...

 

Still no official way?

 

It has been 'in progress' for months

 

Currently this is the most easy way:
https://github.com/yahiaetman/URPCustomPostProcessingStack

 

Looks great! But... with more than 10 projects to maintain that depend on Post Processes, only 'official' is worth to me.

 

The custom PostProcessing appeared on the roadmap, you can mark it as critical to show we need it asap.
https://portal.productboard.com/8uf...cts?utm_medium=social&utm_source=portal_share

 

Done, it's great that they finally started working on this.

 

I've never used URP, but I want to make my older custom post effects work in URP. According to what I read here that's no easy task.
Is there still no official way to have custom post effects in URP, or has this been changed?

 

bump, is there a way to make custom VolumeComponents yet?

 

Probably you could do it via scripting but as far as I know, no easy way to do it "by default".

On my side still begging for postfx shader-graph support... :/

 

This has always been possible, but was simply never documented. The volume system comes from the "Core SRP" package and is merely a way to store and blend settings. It can technically be used for more than just post effects.

A barebones component could look like:

Code (CSharp):

1. using System;
2. using UnityEngine;
3. using UnityEngine.Rendering;
4. using UnityEngine.Rendering.Universal;
5.  
6. [Serializable, VolumeComponentMenu("MySettings/Fog")]
7. public sealed class FogSettings : VolumeComponent, IPostProcessComponent
8. {  
9.     public ClampedFloatParameter globalDensity = new ClampedFloatParameter(0f,0f,1f);
10.  
11.     //Can be used to skip rendering if false
12.     public bool IsActive() => active && globalDensity.value > 0f;
13.  
14.     public bool IsTileCompatible() => false;
15. }

In any other script (such as a ScriptableRenderPass) you can retrieve the settings of a volume component as they are after all the volume blending is performed:

Code (CSharp):

1. FogSettings settings = VolumeManager.instance.stack.GetComponent<FogSettings>();
2. //Doing something with it
3. Shader.SetGlobalFloat("FogDensity", settings.globalDensity.value);

This is also how it works for any of Unity's default effects: https://github.com/Unity-Technologi...versal/Runtime/Passes/PostProcessPass.cs#L286

 

Oh man, thank you so much for this writeup. I was digging into it last night and saw the blending stuff and just could not find where they were actually doing the rendering haha. This is great, now I have a way forward. Thank you!

 

I feel stupid, but even with this very minimal example, I only get the default (un-overridden) value when I print

settings.globalDensity.value

from

Update()

(value = 0). When I write an EditorWindow script to print the value outside of Play Mode, I do see the actual value set through the stack.

Am I missing something? Is VolumeManager.instance.stack not returning the right reference during Play Mode?


EDIT: Found the cause of my issue. I'm using a stack with 2 camera's. The 2nd (top) camera did not have PostFX applied, so the stack is in a reset state when you check values in Update(). There are other points in the frame where the stack has the proper state (e.g. in OnDrawGizmos), but I have to figure out where to hook into (maybe

beginCameraRendering

) to get the state with overrides applied.

 

If you make a RenderFeature/RenderPass, the state is correct in there. It's where I'm using it.

 

Ah, yeah! That makes sense.

But what if I'm trying to use the Volume stack for more general things, like setting the Environment/Ambient light colors.. It seems weird to do that in a RenderPass since it doesn't actually 'render' anything? (Does that even work? I'd have to enqueue it before any other rendering passes so the colors apply correctly?)

 

Try setting the renderpass to render "before rendering"

 

Hey, some progress on the topic. Because an awful lot of time has passed and nothing. This is one of the highly anticipated issues - we just don't spam the topic here and wait patiently. Please don't assume that the topic is dead because I check every version when it will finally be covered.

 

With all due respect to the work of the rest of the creators, but for us programmers, the render feature is a solution. Not so for artists. Of course, we have working solutions - the problem is that the rest of the team is afraid to touch it, which makes it difficult for us to work. Regards.

 

bro wtf

 

There's been some progress on the situation so I'm just posting this for anyone who's watching the topic on custom post-processing, but didn't think to look for "full-screen shading" until recently, which led me to this parallel post.

Anyways, I managed to get something working by following some of Unity's docs on how to do post process effects (with shader graphs) in URP16, and I have posted additional information on how to use this for coded (non-visual, textual programming) workflows.

https://forum.unity.com/threads/full-screen-shaders-in-urp.1228512/#post-8898075