Cinematic Image Effects (Pre Release) package

I've just received delivery of my Vive headset and immediately noted that the SSR effect is broken when rendering with the Vive. It's all warped and different per eye, so really jarring.

Oculus DK2 worked fine. Can anyone shed light on what might be breaking here?

Not using Single Pass Stereo Rendering or Graphic Jobs optimizations (as they are known to be incompatible with current camera effects)

 

How can i ignore AO for my normal maps?

 

Hello, i was just wondering... Since these are Pre-release Image Effects, am i allowed to include them in my asset-store project?
I hope that's not a stupid question!

 

Using native OpenVR along with SteamVR asset and Cinematic Effects (Beta) SSR - each eye displaying something very different.

I did a little more digging through the release notes and came across:

VR: Native OpenVR support added

• Note that native OpenVR support renders with an off-center asymmetric projection matrix. This means that any shaders which relied on fov / aspect may not work correctly.
  

If I was to switch back to using only SteamVR plugin, would this help? Any advice on how to do in 5.4 beta given it's now native through OpenVR?

 

It appears downgrading to Unity 5.3.4p1 and using SteamVR instead of OpenVR allows us to use SSR again (which is key for our project)

Can anyone shed light on why OpenVR differs to SteamVR implementation (assuming at this point that SteamVR does not use an off-center asymmertic projection matrix, or whatever is causing this to break)?

This will be a problem going forward obviously, is there anything on the roadmap to support VR with these effects (particularly the Vive).

I read that support won't make it for 5.4 and single-pass VR rendering (and understand the implications single-pass has to all camera effects), but what of support for non single-pass VR that need to make use of such effects?

 

Thanks very much for following up on this. SSR is probably the most important one for a particular application / industry of VR that we are targeting here.

Do you know if it's even possible to correct the depth buffer after an off center asymmetric projection matrix?

Just trying to set expectations at this end.

We have a prototype launching end of June, where we can continue targeting 5.3, but just want to be confident with recommendations going forward.

 

The bloom is showing black boxes on apple tv 4, probably related to this

• Clamping of HDR result, leading to broken bloom

Edit: only when high quality is off
Apple tv does not have so much power for the high quality mode ..

 

Latest SSR in 5.4 B19 if the SSR quality are set to Low i'm getting pixelated screen

 

It already can be used to debug?
https://github.com/keijiro/KinoVision

 

Alright cool, btw what happen with resolve resolution option? why it's removed? that was usefull

 

I have a question about the new SMAA implementation. We're working on a VR project where one would usually recommend MSAA for the smoothest anti-aliasing, which becomes a lot more visible in VR anyways. For a variety of reasons, the forward renderer is too limiting for our use case, so we've been experimenting with SMAA. As you can see in the comparison below, it does a job comparable to MSAA on the blue surface. The red line however is still pretty jagged, which is very visible in VR. This particular surface is self-illuminated with HDR values to produce some over-exposure in combination with the bloom filter that I've turned off for this comparison. As long as I keep the emission value low, it looks good. But especially within the HDR range, the edges become very jagged.

Any suggestions on this?

 

scene i've created with lighting setup, level design and image effects setup with the new cinematic image effects package and other.

Hope you enjoy

 

@Tim C @willgoldstone
Hi there! I was wondering if you guys had any ideas why our color grading looks drastically different when built, as opposed to when it's in the editor?
Here are two screenshots:

This is how the game looks in the editor, and on the right are the settings.


This is how the game looks once built for Mac.
Both screenshots are using the same LUT and settings, and are under similar lighting conditions. But the colors are way more saturated and blown out in the build.

Here are the import settings for the LUT:

 

You may also find that SMAA does a comparable job to MSAA on some edges in still screenshots, but in VR feel like it's still jagged. The reason is temporal aliasing is far more apparent in VR than the local pixel aliasing alone. Temporal SMAA or other temporal AA techniques can help with this, but the base SMAA can't and is the reason why MSAA is so preferred for VR.

I would personally love to see a proper HDR MSAA implementation for the forward renderer. The same work on getting an inverse tonemapper could be applied to a custom MSAA resolve pass. It's something people have been doing for nearly a decade now to support both HDR and MSAA in forward.
http://www.humus.name/index.php?page=3D&ID=77

 

Is it possible to make the ssr ignore a layer? I dont wan't my first person objects to have ssr.

 

just downloaded image effects and tested on 5.4 b21, it gives me this error...

Assets/Standard Assets/Effects/CinematicEffects(ALPHA)/TemporalAntiAliasing/TemporalAntiAliasing.cs(159,17): error CS1061: Type `UnityEngine.Camera' does not contain a definition for `nonJitteredProjectionMatrix' and no extension method `nonJitteredProjectionMatrix' of type `UnityEngine.Camera' could be found (are you missing a using directive or an assembly reference?)

EDIT: DOES IT NEED b22 in order to work properly ?

 

Looks mint Tim. I'm guessing at this point you're going to throw motion blur in and then merge them into some sort of optimised thing with as few passes as possible? Whats the next step?

 

Im guessing they aren't ready to do that yet.

 

I'm loving this new depth of field effect, it works wonderfully!
Is there a way yet to access its values through scripting? When I access the DepthOfField component in a script, it's listing the values of the old component, not of the new one.

Edit: Nevermind, I just had to use the namespace CinematicEffects rather than ImageEffects, it's all good!

 

We would like to render the weapon in one camera to not overcomplicate the setup. Is it possible to modify a shader to prevent it being affected by ssr? thanks.

 

Hi!

I'm getting started with this pack (nice stuff!), and want to make some things clear about SSR

1) I understand we don't need reflection probes anymore, right?
2) Is it already compatible with iOS? Android? If not, will it be?
3) What's the minimum requirements and steps to setup?

I can't get them to work. I'm just adding it to my main camera, deferred path, tried on iOS/Android/Desktop, and no reflections. Only when I turn on the probes, but then the probes do the job, I see no difference. I'm on Unity 5.3.5f1.

 

I'm pretty sure you will still need them or you get no offscreen reflection.

 

Hi there, yes I was using the asset store version, thanks for linking me to the BitBucket page! So I imported the newer version and got it set up, and it appears to be worse;
Here is how it looks in the editor:


And here's how it looks in the build, same lighting conditions, same LUT.


This is still with Eye Adaptation enabled, but even in the darkest situations, the game never looks like that in the editor. I tried multiple import settings and they all still make it look bad, any ideas? @Chman

 

Guys i've imported this package on my project but when i try implementing antialiasing i get this message Missing shader for image effect Main Camera (UnityStandardAssets.CinematicEffects.AntiAliasing) i've imported it normaly from the asset store , any clues?

 

Oh huh apparently we were working in gamma space, I switched it to linear space and things look different; the eye adaptation and bloom behaves differently! But I still noticed color differences even with Eye Adaptation and Tonemapping disabled; the only thing enabled is LUT, with the contribution at 1.
Here is the editor:

Here is the build:
and here is the LUT:


and for even more clarity, here are the natural colors:


the LUT was exported from the built-in "Export to PNG" button

 

Hello, sorry for maybe already discussed issue, but - it would seem useful - at least to me as a "poor consumer" - to put - somewhere to place easy to find - clear information about under which conditions is each effect supposed to work?
Such as to bitbucket "Readme" and Asset Store description?
It means - for example: AmbientOcclusion: deffered rendering only, not on mobile, not on WebGL... etc?

Beside that, of course thanks for your effort, and looking forward to see finally a great-looking AO in my nicely antialiased image...

 

Hi!

When using the Ambient Occlusion post effect on Xbox One it seems to triple the performance when standing close by and looking to a wall. The GPU cost goes from ~10ms to ~34ms just by walking up to a wall.

Here is a demonstration video in a simple scene captured from the Xbox One:

Here is a before and after of the profiler when walking up to a wall.

Before


After


Any idea why this happens?

 

It's a quirk of all AO implementations. Some fare better than others, due to samples I guess. You're much better off baking it.

 

Also should be noted a lot of older SSAO implementations didn't suffer from this because they were doing SSAO wrong by using a fixed screen space radius which caused over-occlusion on things in the distance (which was usually handled by fading out distant AO).

An alternative to reducing the sample count is the AO implementation can use a screen space radius clamp. The original Scalable Ambient Obscurance, what Unity's Screen Space Ambient Obscurance is based on, handled this by generating a mip map chain for the depth and using lower mips when the radius got larger for better cache coherency.

 

Thanks everyone for all the insight! Glad to know this is a side effect and not a bug.

 

What do you guys think about this as a replacement for AO in general?

- bake AO into textures for env and characters
- use spherical harmonic style soft shadows where dynamic object meets env

I mean this is faster and generally looks pretty much the same up to a point. We can still make it react to light. Why isn't this the first solution? AO seems to me a lazy man's solution with only a small quality gain for a loss of a lot of performance.

 

Ah yes, we actually were using the exported LUT in the game. Since my last post, we tried setting the color grading in the scene, but after making a build, we got the same result; The build looked different from the editor.

Also note that we're changing values in the component via code after the scene loads; we thought this could have something to do with the problem but HOWEVER, we tried this: We made a new blank test project, and ONLY imported the Color Grading and Tonemapping component. We built the game, and boom, the editor and the build looked exactly the same.
THEN, in the test project, we tried changing the values of the component via code, and it worked just fine, looked the same in the editor and in the built.

SO that leads me to believe that something in our big project is interfering with the Tonemapping and Color Grading component......but I have no idea as to what....Both projects are in forward rendering, gamma color space, and are using HDR, same quality settings and everything, I'm quite confused.

Are the cinematic image effects only supposed to work in Deferred rendering? We're using Forward.

 

Have mobile fixes been pushed yet? Im curious if effects work on mobile devices.. Is there a test scene Unity can send me to check on various physical devices I own. Feel mobile not been covered fully here.. Cheers

 

I think grarding works as far as I can tell, I'm not sure all of the effects will work on a mobile though, in particular SSRR might not work on most phones as it is deferred only, so depends on if the mobile supports deferred... imagine similar story for the AO.