Official New Post-processing Stack (Pre-Release)

Wow, this works, thank you very much, would be nice if developers fix this in code and no flip images necesary anymore, for example put a checkbox with the option "flip vertical".

 

Hi, I have a question about how works tonemapping correction, this effect converts sRGB colors to for example ACES film colors (Render RAW image -> sRGB -> ACES film colors -> GPU) or converts from raw linear color render data directly to ACES film colors (Render RAW image -> ACES film colors -> GPU) ?, if the first process is the used then is not a real ACES color encode and is a emulation effect? thanks.

 

have same, rename Bloom.cginc (and refs to it in Bloom.shader & Uber.shader) helped

 

This post-processing stack looks great, but so far it only works on non-VR games.
How would I go to make it work on VR, especially on the Daydream?

 

Why did you guys not included SMAA in this? TAA looks like everything is shaking, i dont know how this is better than no AA at all.

Please add SMAA

 

Still wondering about this. It also occured to me that it would make sense for all Image Effect stack components to have access to these blur textures because DoF and SSR use them at least and if you have both enabled you would be wasting resources by generating blur textures once for each effect!

 

You are incorrect, and probably have failed to set it up. Try a new project in 5.6 with the latest post fx download. Unless of course you think the adam demo is shaking non stop somehow.

Or post a bug report. Unity has already said SMAA isn't going to happen.

 

How do we access the post processing stack effects in C#? Like Using ? I am unable to use depth of field and effects like those now so I was wondering how can one use these in C#? I was looking around but was unsuccessful.

 

Thank you so much I appreciate this.

 

I guess this is only me but.. anyone else experienced the SSR not working anymore , despite being in deffered rendering and using a simple plane with a standard material set with high metalness/s ?
What am I missing ?

 

https://www.assetstore.unity3d.com/en/#!/content/7006

 

Strange that the link does not work. I made a new link.
https://www.dropbox.com/s/zdusayzvzyldojb/Postprocessing-modSSAO.unitypackage?dl=0

 

Now I'm getting a 404 error...

 

Same 404 :'-(

 

anyone else experiencing some strange jittering from the postprocessing?

 

Does it go away when you disable dithering?

 

Does anyone get strange ghosting artifacts with TAA? If I keep the TAA cam still and pass a moving object in front of it, a trail of the object stays behind until I move the camera.

 

There's a lot of warping that happens. Check this video - https://gfycat.com/DismalFoolishDuckling

 

I have done this exactly (Assigning a new Profile to the current PostProcessingBehaviour), but doing so, I got spammed with this error :
Attempting to release RenderTexture that were not gotten as a temp buffer

What I did wrong ?

 

Scene view image effect bug fixed in Patch 4

 

I have an issue with the depth of field effect in this stack, using the latest GitHub version:

The transparent elements such as the question mark particles on this shot seems to use depth information from the element behind it, and not the actual particle position.

The question marks should not be blurry on this image as they're positioned at the left character's head, yet they appear blurry because the background behind them is far away.

Is this the wanted behavior of the DOF effect? Is there a way to fix this / are you planning to fix it? Thanks!

 

Using a transparent shader for the particles? Solution sees to be to switch to a different shader or use mesh particles since transparent objects don't write to the depth buffer.

http://answers.unity3d.com/questions/1071430/depth-of-field-ignoring-particles.html

 

It has entirely to do with the shader writing to depthbuffer or not. Meshes with transparent shaders will behave the same as particles with transparent shaders, because pretty much all transparent shaders don't write to the depth buffer. You could draw over the questionmark with another invisible shader that just writes to depth, after all transparent rendering is done. That might still look weird though, I'm not sure.

 

I see. Yes, I was using a transparent shader. I've fixed the issue by using a cut-out shader. Thanks guys!

 

the jittering is caused by the ambient occlusion as it seems

 

Hm, for me the AO always worked fine, but I had some flickering issues with certain combinations of modules activated. That mostly went away with an update, except for dithering. Maybe try another version (an older one if you have the newest already).

 

Black screen on GL Es 3.1 device T720 MP2 only used Color Grading

 

yikes that is terrible, and pretty much exactly what is happening with mine too. Well I guess I'm glad I'm not alone, but not so glad that such a terrible issue still remains and makes TAA unusable aside from static scenes.

 

I ve tried it on several projects and none will build when using this stack

 

Generally speaking, just saying "it doesn't work" doesn't help anyone help you. You should provide as much information as possible, such as...
Unity version
Version of the asset
Build target (PC, UWP, Windows Phone, iOS, Android, ...)



As for me, I have just acquired an Xbox One and am really eager to begin testing games on it. But the post processing stack does not appear to be compatible with Universal Windows Platform (UWP). Unity version 5.6.0p1. Latest release version of this asset from the Asset Store. Error is as follows:
Assets\PostProcessing\Runtime\Utils\ReflectionUtils.cs(81,29): error CS1061: 'Type' does not contain a definition for 'BaseType' and no extension method 'BaseType' accepting a first argument of type 'Type' could be found (are you missing a using directive or an assembly reference?)

EDIT: The solution to my problem is easy. Simply move ReflectionUtils.cs from the Runtime/Utils/ folder to the Editor/Utils/ folder.

 

how well does this fair on mobile platform?

 

Unity 5.6 - EnlightenRunTimeManager.PostUpdate process using 95% CPU time when using post processing stack.

Not sure if this is the right place for this but today I experienced the following:

1) With the post processing stack enabled when pressing play in the editor, the Profiler shows a steady 60FPS.

2) If I make a development build of the scene with it plugged in to the profiler, FPS drops to 15 FPS. It's continuous spikes caused by the EnlightenRuntimeManage.PostUpdate process. I don't understand what this is or why it only happens in a build, rather than in the editor / play as well.

If I disable the post processing stack on my camera and rebuild, this spikes completely stop. Building without it plugged in to the profiler (dev build turned off) I can see the lag spikes, so it still happens then too.

Anyone any ideas?

 

Are you testing on a desktop PC or laptop ? it's not hardware fault ?

 

Hi,

No, it's definitely not a hardware fault. It's a relatively new (less than a year old) desktop PC and testing on a separate machine produces the same results.

The bit I don't understand is that I don't get the same results in the editor.

I have nailed it down to the screen space reflection option. This seems to be the culprit. I get that these effects are expensive but is this expected behaviour? I.e difference between editor play mode and build?

I also get this strange glitch with the bloom setting, so I'm wondering if there's something else going on in my scene that's effecting the post processing stack. See attached.

 

SSR have an impact, if you turn it off perhaps you won't have spikes ?
The game should run faster in build mode, you could check your build settings perhaps you have something not expected turned on or some value too hight somewhere.

 

Please, upload it on google drive or sendspace or something like. Or on gumroad perhaps :-D I need it so much!

 

Hey, I'm kinda new but I read the Github instructions but bloom is missing/a few things have different names, has it been renamed?

 

Since updating to Unity 5.6.1 (from the first 5.6 release) screen space reflection doesn't seem to work. When I turn it on the scene goes black as if there's no lighting. I've double-checked I'm still using deferred lighting and have rebuild the scene lighting. (The water uses its own reflection script, which is why it still works.)

 

I might be missing something obvious, but your scene doesn't seem to have any lighting at all? What exactly are you hoping to reflect?

 

In 5.6 scene with procedural skybox, when camera MSAA is enabled and direction light x-rotation is reduced to below certain angle, weird artifects shows up on the horizon.

 

There seems to be a bug in 5.5.3p3 where the generated code for the screen space reflection shader is wrong when running GLCore.

The code in the ScreenSpaceRaytrace.cginc file:

Code (CSharp):

1. if (P1.y > yMax || P1.y < 0.5)) {
2.         float yClip = (P1.y > yMax) ? yMax : 0.5;
3.         float yAlpha = (P1.y - yClip) / (P1.y - P0.y); // Denominator is not zero, since P0 != P1 (or P0 would have been clipped!)
4.         alpha = yAlpha;
5.     }

Causes the compiler to generate code that tries to access non-existing 3rd and 4th values of a bool vector with 2 values.
Changing it to the following seems to disable the optimization and remove the error:

Code (CSharp):

1. if (!(P1.y <= yMax && P1.y >= 0.5)) {
2.         float yClip = (P1.y > yMax) ? yMax : 0.5;
3.         float yAlpha = (P1.y - yClip) / (P1.y - P0.y); // Denominator is not zero, since P0 != P1 (or P0 would have been clipped!)
4.         alpha = yAlpha;
5.     }

 

It does have lighting. That image is how the scene looks when I try to use screen space reflections. Here's how it looks if I disable SSR:

 

What's the status of the flickering issue on your end? I've pulled a new version of the stack from the assetstore yesterday and the issue still seems to persist. If you haven't found a fix internally that isn't live on the assetstore yet, I might have a repro case now.

 

I can't find that code in ScreenSpaceRaytrace.cginc. The closest I have is:

if (P1.y > yMax || P1.y < yMin) {
float yClip = (P1.y > yMax) ? yMax : yMin;
float yAlpha = (P1.y - yClip) / (P1.y - P0.y); // Denominator is not zero, since P0 != P1 (or P0 would have been clipped!)
alpha = yAlpha;
}

 

I forgot, I inlined the constants in an attempt to avoid the bugged optimization, so that is the code I'm referring to.

 

I have a problem with depth of field: the intensity of effect (blur) changes with different screen resolution. So i must change aperture.

Settings are:
Focus distance: 3
Aperture: 6.5
Use camera FOV: disabled
Focal lenght: 50
Kernel size: medium

Unity 5.6.1p1

TNX for support.

 

What are the differences between V1 and V2 in Github?

 

afaik v2 are total refactor of the PostProStack with some new feature, some feature are still cannot be used. Most are ready.
But i don't recommend it to be used in the real production for now.

 

Will there be a simplified Depth of Field mode? I don't want to learn about cameras just to use it.

Focus distance, focus size, near blur, far blur, etc should work for most games.

 

You don't need to.

Play with the settings for 10 seconds and you'll get what each one does.