Official New Post-processing Stack (Pre-Release)

Looks like a good read. since I'm aiming for that quality

 

Looks like I better make friends with those widgets. It's not hard to do, just time consuming. I did see the curves, which is similar to photoshop

And can't wait to see the fog. I have faraway assets in some of my levels and fog adds some extra IT to my game

 

This is with TAA on, I appreciate GIF isn't the best quality but it get's the point across. You can even tell by the cuboid there's jaggies and even in editor the grass / tree's is pretty much pure noise. I must admit I've never seen a TAA solution that had any issues with things like cubes.

Screen with TAA switched on:




Here's one with TAA switched off:




Here's my own test implementation:





You can't tell that much in screenshots, but I'll post some anyway after this post. BTW, I'm not saying the implementation should be blurry in any way, although I am saying it should smooth out jaggies efficiently or it's not worth the cost of having it..

 

Edit: Screenies don't really say a lot but I'll post them any way:

1) TAA is on
2) Custom AA
3) TAA off

I'm using Unity 5.5b09, it's a radeon 390X card and it seems to work fine on cubes etc.. It's just foliage, I'm looking through the code.. My solution is err a little blurry / slow.! So hopefully can get this fixed.

 

What would be helpful is a cube with TAA on and off, nothing else. Then we can determine if you're bugged or not. Because Unity's TAA removes jaggies here, so I'm thinking.... maybe you have something preventing it from happening, or maybe not 5.5 or something

Seems weird, cubes are antialiased this end...

Edit: my test:

 

I'm liking the ground. Terrain?

 

Yep, just a test scene using standard Unity terrain.. I'll admit it, I used Scion and Amplify colour on that scene. The AO is Unity's, Enlighten's realtime GI works pretty well with Unity terrain as well IMO..

@hippocoder @Chman

It's something to do with the render queue, I've had a mess around with it and it's working. In fact it's probably one of the best AA solutions I've seen (apart from ghosting which I'm looking in to). But generally, good work..

A decent AA solution in terms of graphics has been probably one of the most sorely needed features.

Also if you're on an AMD card, I'd recommend upgrading drivers.

Thanks for the support.!

 

Looking good

 

Hey, I just got the new build of the post effects stack... I love how easy it is to create the look I want. Does anyone know why the default spectralLUT is turning the camera black?

Fixed it. I just set the images to advanced, and set them to linear

 

I have yet to try the new stack, but will you be adding SMAA to it? It's what I'm currently using from the older cinematic effect package, because the TAA in the older package was jittering like crazy when in motion. Otherwise this looks really cool! =)

 

Hi everyone today i will showing you some tests i have done for the wararm game https://www.wararm.eu/home with the new image effects stack.
Hope you enjoy
With TAA

With SMAA

Volumetric lights, TAA

No volumetric lights, SMAA

 

I love this tool man... And as for TXAA, I think Project Champion will be making use of it once I get a working build going.


Sorry about the washed out feel... forgot to tune it. Using Neutral in both shots as I have more control over the look. Filmic ACES looks very similar with less tweaks.

 

@Chman latest pull give me these error when trying to activate eye adaptation
Unity 5.4.1p4

Code (csharp):

1.  
2. Kernel 'KEyeHistogram' not found
3.  
4. UnityException: FindKernel failed
5. UnityEngine.PostProcessing.EyeAdaptationComponent.Prepare (UnityEngine.RenderTexture source, UnityEngine.Material uberMaterial) (at Assets/PostProcessing/Runtime/Components/EyeAdaptationComponent.cs:106)
6. UnityEngine.PostProcessing.PostProcessingBehaviour.OnRenderImage (UnityEngine.RenderTexture source, UnityEngine.RenderTexture destination) (at Assets/PostProcessing/Runtime/PostProcessingBehaviour.cs:216)
7.  

 

Hi,

I tried the new post-processing stack and I like the results! Film-grain together with chromatic aberration, TAA, ambient occlusion and a little bit of vignetting make for a really smooth look.

I tried bloom too, but was unable to get the kind of result I was aiming for. I had two objects in the scene with different emissive materials on them. I set the emission factor for the first object to 2, and for the other object I set it to 10. Then I tried playing with the bloom threshold value to see when it would "pick up" those emissive objects, but there was no difference between them. The other wasn't brighter either. So it seems Unity clamps emissive values between 0.0 and 1.0. Would it be possible to allow values beyond this range? Like an HDR bloom. So increasing the emission factor for a material would increasingly make it brighter and cause a bigger bloom.

I can post screens later.

Cheers!

 

Still error after reimporting. even the histogram are gone.
Edit :
it fixed by remove the whole PostProcessing folder.
kinda weird though i've been remove and reimport the folder couple times and randomly it working :/
Oh wait, i was in webGL before and then switching platform to PC.

 

The new post process stack seems to be causing a massive "GFX.WaitForPresent" performance drop only in builds, but not in editor play mode (even when window is maximized, so I don't think this is a resolution thing). Anyone else have this? GPU profiling doesn't seem to work. I'm on Windows 10, DX11, GTX960

EDIT: Ok, I managed to profile GPU now. It seems the main culprit is SRR. The GPU seems to take around 9 more miliseconds per frame when SSR is turned on. This is for a very simple scene (https://i.gyazo.com/f9705e344fa5d2a6e6b8d61041949b10.png) using the SSR's default settings with "High" reflection quality. Is this normal?

 

Awesome
Any ideas why it would run much faster in-editor than in builds? It has an extremely low performance impact in-editor, and no noticeable difference in visuals compared to builds

 

Umm.. okay my bad. Thanks!

 

Really like these post fx, only irk I have is the bloom, kinda a love hate.
I love because at times it looks really nice and better then most blooms out there.
At other times it looks really low res for whatever reason, like it has been upscaled from a much lower resolution and just looks pretty ugly, particularly on a smaller radius.

 

Great job on the new stack! Couldn't wait to use this ever since the first release of the new effects!

But I'm wondering, could anyone give me some hints on changing values at run time? I'm including UnityEngine.Post etc and tried referencing the post process behavior, but I always get 'Cannot modify value of ColorGradingModel.settings because it is not a variable'. I know I'm missing something really simple.

Any hints?

 

I'm gonna say this was a false alarm. I was on 5.5b10 too, but it seems like my scene had a missing reference to its lightmap data for some reason. It wasn't even supposed to have a lightmap in the first place. The problem disappeared when I cleared the link to the missing reference

The performance difference between in-editor and builds is gone now. But it's great to know you guys are still working on performance improvements

 

Could you add Horizontal/Vertical only Motion Blur toggle?
It could be useful in FPS games. Its looking weird now when motion blur is also on Vertical axis in FPS mode.

 

@Chman can you please confirm the issue I'm seeing where SSR doesn't work with baked lighting? It seems that lightmaps prevent it from working.

 

Is it possible to add single effects directly to the camera?

 

Chman can't you add some enhancements to the AO post processing stack, I want to use it but its a little barebones for AO, things like distance cutoff/falloff from camera.

 

Seconding MattMurphy's request for some hints on how to change these variables during runtime!

Thanks for this great asset, looks really really sharp!

 

Is there any way for particles to be affected by the motion blur effect?

 

I think that's supposed to be done (faked) through stretched particles, right?

I always assumed that's what the options for camera and velocity scale were for....

 

That might be a workaround for sprites but not for mesh particles. With motion blur support they could look like this:

 

I have no Git hub account, so just wanted to tell you that I also have the issue reported here https://github.com/Unity-Technologies/PostProcessing/issues/13

User cameronoltmann described the issue pretty well.
He is using deferred/linear, I'm using Forward/Linear in 5.5.0b10 but the problem is the same.

Anyway keep up the good work

 

Thanks Unity to release this !!!

 

This is with default sharpening as set by Unity. Sharpening shouldn't actually add black lines. Lowering from default removes them. Is this just a thing?

 

Currently particles are affected by camera motion blur but that's it. I asked Keijiro Takahashi about this and he told me the problem is that particle rendering doesn't actually support motion vectors. He referred me to this, which more clearly specifies that Graphics.DrawMesh (along with the other Graphics.Draw* methods I presume) doesn't support motion vectors.

 

Could you tell us why non moving parts are affected by motion blur? Only wheels are rotating here :

How we can prevent this?
We are on Unity 5.4.2

 

Is there any chance the wheels are opaque and the body itself is a transparent? The motion vectors aren't collected for transparent materials if I remember correctly, so they will be 'see through' as far as motion vectors are concerned. Seems a bit weird to have the car body be transparent though.

Disclaimer: Haven't actually used the motion blur yet, just followed the progress here

 

To clarify. forward shaders don't send motion vectors. They don't have to be transparent.

 

What happened to Dither? It's in the Cinematic effects but not in the Stack. Maybe I'm overlooking it?

 

I'm a big fan of very fast and okay-ish. Please keep, nothing to see here, move along...

As if this stuff is slower, it doesn't get used at all so... and in any case it'll be textured so nobody will notice it much

 

Shaders are not transparent. Same is happening with STANDARD Unity 5.x shader. Check out this shot (right rear wheel)
You can see that in some parts motion vectors are covered by fender, some parts not (same mesh, same material) :


Also you need to know that tires are skinned mesh renderers.

 

Seems like the image composition for motion blur not respecting depth of some kind...

 

You've ticked the 'generate motion vector' option in the mesh renderer component (I think it's on there, haven't used it yet)?