Set edgePostProcess render after other postprocess

Questions
1

I need help!
Thanks!
Step 1 Create a DefaultRenderingPipeline, at line 47
Step 2 Create an edge Postprocessing, at line 188
In the third step, I tried to create another blur post-processing and set the edge post-processing to be unaffected by the model post-processing. at line 192

2

I am not sure the DefaultRenderingPipeline allows you to choose the execution order of your effects.

However, you can use a custom PostProcessRenderPipeline that will give you full control of the execution order of the post-processes.

2 Likes
3

@Cedric
The effect of modifying the post-processing parameter and setTimeout modifying the post-processing parameter is surprisingly different.
I followed your approach and got a bug.
I need to modify the post-processing parameters from time to time.
PG:

marginal notes line 194,202 remove the timeout to see the effect

4

I’m not sure I’ll be a great help here.
ping @Evgeni_Popov

5

This is because your custom post-process does not end up in the same place in the camera’s post-process array:

  • when you set depth of field without a delay, your post-process is at the end of the post-process chain, and therefore applies last
  • when you set depth-of-field with a delay, the post-processes in the default rendering pipeline are recreated at this point and added to the end of the camera’s post-process list, i.e. after your post-process.

If you want your post-process to always come after the post-processes of the default rendering pipeline, each time you update the latter, you must first detach your custom pipeline from the cameras, update the default rendering pipeline and reattach your:

2 Likes