Cinematic Image Effects (Pre Release) package

What tree system are you using? Speedtree?

 

The gbuffer does get forward rendered opaque objects rendered into it though prior to the forward rendering pass. Right now it renders them black across all gbuffer channels for the purpose of getting proper depth, but that causes problems for post process effects that use the gbuffer normals. It would be awesome if there was a shader pass for "ForwardDeferred" to render normals, depth, and maybe some specular smoothness values to the gbuffer so that opaque forward rendered objects could still take advantage of these kinds of post process effects.

 

Yep SpeedTree. There is definitely something really bad going on with their shaders. If the sun shines through the leaves the colours are terrible. This never used to be an issue so it's been introduced in newer versions of unity.

Just FYI, Unity is responsible for these shaders, not SpeedTree.

 

well i don't have beta 16. . . .

 

We're seeing lots of issues with speedtree shaders as well.

 

Same problems in Deferred - with viewpoint against sun .

 

Alright i'll try it later, haven't tried reimporting the files

 

making that *.gif my desktop background...
scratching lines on wall and counting days for beta16 relise...

 

I know right? Tim's just flaying us alive with this stuff.

 

I guess combining the post eventually will allow you to amortize a lot of it, such as your AO example above. Maybe possible for bloom and DOF too, which could offset the cost a lot from fixing up HDR and so forth (if it's at all costly).

 

your jedi mind trick not gonna work. . . . .

 

So... does that mean we ARE (possibly) getting an uber effect out of this?? Don't want to read too much into it but if that's the case...

 

I'd be happy with just an improved SSAO, ie with complete features like min/max distance, near/far distance falloff, given enough settings you can tailor an effect better.

 

Beta 16 is live. Time to try some TAA!!!

 

Tried both but it does nothing
Please check attached package - thank you!

 

Does it works ?

 

Of all the times for this thread to go a bit quiet, I didn't expect it to be just after TAA was available via motion vectors in 5.4b16!

I tried it but I am not best suited to giving initial feedback because I've had the luxury of completely avoiding all forms of anti-aliasing until now, I had the luxury of waiting till TAA was available. But this makes me ill equipped to rate the solution in its current state or compare it to others.

 

I've been skimming through Nvidia's PostWorks and it seems like a working plugin for TXAA is now possible. Although the new AA is way more practical, so its probably not be worth the effort. Unity's TAA seems to work pretty well but I haven't found a good scene to properly test it out yet.

 

There seems to be an error if SMAA (TAA branch) is enabled before running the scene. Quick workaround, add:

Code (CSharp):

1. if (source == null) return;

in OnRenderImage() of SMAA.cs.

Testing it on a simple scene with a spinning cube, the temporal aliasing finally gets rid of the crawling pixels along sharp edges. On the flipside, depending on the Fuzz Size the vertices of the cube will jitter. You have to tweak a bit to find the balance between anti-aliased edges and fuzzy vertices. But it looks promising, temporal aliasing is clearly part of the secret sauce that make Unreal and Crytek look so smoothly and cinematic. Now I'm going to try how it looks with a more complex scene, especially specular highlights.

 

In the Corridor Demo, SMAA with Temporal enabled unfortunately still has a lot of aliasing. The Temporal Anti Aliasling script on the other hand fares much better, but it also adds more blur (with the default settings, haven't tweaked yet).

 

Is someone getting spammed by these?

Kernel index (-1) out of range.

I'm using 5.3.4p4

 

Here´s the screenshot:



On both scenes I imported the TreeSoftOcclusionLeaves.shader from the shaderspackage changed its name to "NatureEdited/Tree Soft Occlusion Leaves" and changed the lines 18 and 102 to "Queue" = "AlphaTest" as you described.

 

I'm not so sure if that even can look better with image effect DOF. Does anyone have a technically identical usecase where it looks like the photoshop mockup?

In my opinion you are using way too much DOF here, try turning it down a lot and see if the artifacts are still noticable at all. Do you have an actual usecase that you could show, something from a game you are working on maybe?

 

My example scene from above is just a very quick setup to show the problem.
Of course there are technical usecases (e.g Tiltshift, artistic styles....):

Despite this, if Unitys posteffect provides these DOF-ranges (which is very cool and useful) it should work together with the provided shaders, no?

 

Done

Yes, I knew about this, hopefully there´s a chance to fix the problem.

 

Im loving the new bloom effect. Quick question, what exactly does the "high quality" flag do?

Also, is this new bloom suitable for high end mobile devices?

 

Actually I tried the bloom effect on an LG G4 and it creates big white squares wherever it would normally put a bloom effect. Is this a known issue? Is there a particular camera setting or other setting that need to be set to enable this?

 

Hi

I am just wondering whether it is possible to attach the TonemappingColorGrading script to multiple cameras, because I am getting some very strange results.

I have attached one to a Camera that uses a render texture which appears to work fine.

However I have then attached it to another camera that is using a layer mask set to say "Counters". However when I change the settings on this one it seems to affect other cameras within the scene (that render other layers e.g. "background") that do not have this script attached to them.

So is it possible to have multiple instances of this script attached to different cameras, each with different settings?

thanks

Nalin

 

Happens when using linear color space and deferred rendering. Terrain highlights make it look like plastic, grass and trees break. It's hardly a new bug too. IIRC the first time I heard of it was during the closed beta for 5.0 and was about how the standard shader's roughness range just doesn't extend far enough for terrains.

One question:
I'm using the cinematic effects (BitBucket version) and they also show in the scene view. However, this makes working on UIs impossible since everything glows. Is there a way of turning that off without having to disable all the scripts?

 

You can toggle the rendering for them in the scene view from the "skybox/lens flare" drop down, where you can disable only the image effects but leaving the rest on.

 

On GDC they said that some of those effects are working on mobile. Bloom, tonemapping and DoF in particular. What's the performance of those new effects?

 

Bloom doesnt seem to work on mobile. When i enable it on my lg g4, it shows big white squares everywhere.

 

Does anyone else have issues with Screen Space Reflections and Unity Grass? Reflective objects seem to be rendering on top of the grass. Not sure how to fix this. I guess I could try a 2 Camera setup, but that sounds like a stupid workaround.

 

Sure it is not the AO ?

 

Yeah, I tried that. It looks like it. But it is not.

 

Hello,
I was wondering if Unity would consider to maintain some comments in the standard assets scripts which explain any updates made to the scripts. This would apply to camera effects scripts, character controller scripts, etc.
The problem is when the standard assets are update, there is really no way to easily determine if something changed, other than to analyze and compare the scripts. If each file had some change log, it would be much easier to determine what changed. In the past I had to do a file compare of the DOF script to see what changed, because our scripts which communicate with the DOF script were no longer worked. It was then determined that the DOF script had changed and operated differently.
This would apply to the shader files too.
Thanks

 

Can't you use camera depth in order to filter the background layer in the foremost camera?

Like:

float rawDepth = SAMPLE_DEPTH_TEXTURE(_CameraDepthTexture, newUV);
if (rawDepth < 1.0) { rawDepth = 0; }
return color1 * (1.0 - rawDepth) + color2 * rawDepth;

This is what I did for this artwork since I rendered the background mountains and sky with a different camera and didn't want it to be affected by the tonemapper.