SSAO Pro - High Quality Screen-Space Ambient Occlusion

Hey there -- I'm getting an unexpected "Unsupported shader (SSAO)." message from line 161 of the SSAOPro file. This is in the default demo scene that comes with SSAO Pro, as well as in my own scenes.

I'm running DX9 on purpose (compatibility with the most people), on windows 10, unity 64bit editor, 5.3.2f1, deferred rendering, GTX 980M card. I really have a hard time believing my card doesn't support this, so I'm presuming that either this is a bug or something strange in my project settings is interfering with even the demo scene.

I'm able to use Amplify Color, Scion, FXAA, and PRISM all with no trouble with these project settings, so I'm really not quite sure what this would be. (I'm not running all those things at the same time, of course!)

 

That is... super duper odd. Basically here is what I think happened:
1. I import this from the asset store.
2. It does its thing, and then I move it to a CameraEffects subfolder for the sake of organization.
3. It tries to compile, but it was getting "Could not find SSAOPro.cginc" errors on import (thanks for the tip on where to find that).

Here's where it gets really strange. Not reading your post carefully (my bad), I just casually tried to hit recompile on the shader again. Didn't work. So I figure that it must be a path thing (grumble grumble). So I copy the SSAO Pro folder back to the root folder. Try to compile the shader again in that same fashion. Does not work.

So I read your instructions more carefully, then right-click and hit reimport. Boom, works like a charm. I figure that I may as well try moving it back into the CameraEffects subfolder and see if it wigs out again. It moves just fine. Suspicious, I reimport it again, this time at the new location that presumably was a problem before. No issues are encountered.

That leaves me... baffled. Your solution is simple and worked immediately, but I'm not really clear what I did that caused the issue in the first place. Clearly the path doesn't matter (thank you!), so I guess unity just had "one of those moments." I know it's nothing to do with your code at all, but I just find it to be a curiosity. I was kind of hoping I'd have a clear "do this and it breaks until your right-click and hit reimport" case that you could add to your faq. I suppose the case is just "if it wigs out for whatever reason."

Anyway, thanks again -- I'm a happy guy now.

 

What I have gathered from this and other circumstances is ... sometimes you have to re-import something to get it to work right, especially if it is a shader.

 

Rather like steam with the "please verify your file cache." It's once in a blue moon that actually matters, but man after 6 years of players occasionally bringing me a strange issue and that being like 1 in 100 the case, it still gets me.

 

Myself and a couple of others seeing crashes in Windows builds with 5.4. Details in this thread:

http://forum.unity3d.com/threads/5-4-beta-bug-crash-inside-cleanupdrawmeshrawfromnodequeue.396515/

 

Hello, we are using SSAO Pro on our project and we are happy with it's quality.
We have set up graphics setting script. And in high graphics SSAO pro component is enabled. In other settings it's disabled. Hovewer after Enabling SSAO Pro and disabling it, Draw call affect sits there and game runs slower. I don't want to restart scene after setting graphics. Is there a better way to disable SSAO Pro? After enabling and then disabling component, camera component gets this notification: "Info: renders Depth&DepthNormals textures"

 

@Chman I'm using deferred rendering path.

 

I can´t read the whole thread, is there already a comparison to the new Unity-Cinematic-Beta AmbientOcclusion?

At a first glance it was kind of convincing to me.....

 

So the bug still present for the Unity 4 users
You copy the bad practices of UT. Welcome in board.

 

Thanks and sorry.

 

Hi Chman,

I have an issue with SSAO Pro and Unity 5.4b16.
If SSAO Pro is active, I'm not able to see "Global Illumination" Pass (UV Chart, irradiance, etc...) in the Scene viewport. Everything is rendered black.
If I disable SSAO Pro, everything works fine.

Are you able to reproduce?

 

Hi Chman,

Disabling Image Effect in Scene View, now I'm able to check GI pass

Thanks for trick! You think could be fixed in next release? Imaged Effect preview is very useful.

Thanks,

 

Hi Chman,

Any progress in regards to the ability to exclude objects on a particular layer? I love the effect of the SSAO, but it makes my characters look like they need a bath - and since I'm developing VR, I don't think adding cameras is a good idea...

Thanks,

Joe

 

Ran into the "problem" with depth/depthNormals still being enabled when disabling SSAOPro as well
Could setting the depthTextureMode in OnPreRender and resetting it in OnPostRender be a way to handle it without interfering with other effects?

Code (CSharp):

1.     void OnPreRender()
2.     {
3.         depthTextureMode = m_Camera.depthTextureMode;
4.  
5.         // Depth & normal maps
6.         m_Camera.depthTextureMode |= DepthTextureMode.Depth;
7.         m_Camera.depthTextureMode |= DepthTextureMode.DepthNormals;
8.     }
9.  
10.     void OnPostRender()
11.     {
12.         m_Camera.depthTextureMode = depthTextureMode;
13.     }

 

Hi there, I just bouught the package and I have a problem. I use multyple cameras to draw different things in each layers. If I add the SSAO to the one above all (the one with higher Depth), which I use only for effects (Culling Mask: Nothing) it does nothing. And if I add the script to the camera that renders most of the world, it stops showing the particle systems (yeah weird) and also does nothing with the script.

The only way I made it work is apllying it to the one above all and turning on all the Renders (Culling Mask: Everything), but that is not what I'm looking for.

Am I missing something?

Thanks,

By the way, the support email at the Asset Store goes to a blank page.

 

It's a little off topic, but could you share with me how you set up the single camera setup with UFPS? I am struggeling to get the SSAO Pro to work with multiple cams in UFPS. Thanks so much!

EDIT: Nevermind, found it already. UFPS does have a retraction tutorial, which explains it: https://docs.google.com/document/d/...3KzMfsPUGBI/pub?embedded=true#id.ufpg3gltyrcq
SSAO Pro works like a charm now!

 

Quick question: Is there any way to prevent transparent grass planes (which hold a texture with an alpha mask) from having the AO effect? Would love to use SSAO Pro but my grass starts to have those dark fillings now:

 

@Chman yes it is a custom grass shader based on shader forge. And idea of how to solve this?

 

Hi,

Does anybody know why SSAO or any other kind of AO image effect causes horrible white edges (almost like REALLY bad aliasing?) It's particularly noticeable in this case as it's black window frames on black glass.

 

Has anyone tried this asset in VR with single pass stereo? Unity's own ssao solutions don't work reliably.

 

@Chman,
Sorry for my delay. I did some more testing and the problem with the shadow affecting the whole geometry/plane for grass/trees also happens with the SpeedTree models provided in Unity when using forward rendering (see attached images). However when I switch to deferred or legacy deferred the shadows on SpeedTree are gone but are still visible on the grass as described in my former post.
Do you have an email, so I can send you the shader which is used for the grass?
Thanks so much!

PS: Since Speedtree has some issues with highlights in deferred rendering I am aiming to use forward rendering.

 

Hi can you help me please, i can not turn SSAO on and got this warning message in unity

Unsupported shader (SSAO).
UnityEngine.Debug:LogWarning(Object)
SSAOPro:OnEnable() (at Assets/_Complete Tools/SSAO Pro/Scripts/SSAOPro.cs:148)
UnityEditor.DockArea:OnGUI()

 

In this thread there are some custom fixes to use speedtree on deferred rendering (and ssao pro too) without much notable issues.
Hope this helps.

 

I'm getting a lot of artifacts and wavy lines if I do not set my near clip plane to 0.3 or higher, is this a bug?

 

Hi. I bought it yesterday, but didn't use it yet, because deactivation of SSAO component button(in main camera) & console warning message.
"Unsupported shader (SSAO). UnityEngine.Debug:LogWarning(Object)"
What should I do? Please any idea what it could be..

 

I have this issue when using SSAO PRO:


For various reasons, I need to create a shader with exclude_path:deferred. But when doing this, and also using tessellation, these artifacts are displayed.

Code (CSharp):

1. Shader "Custom/SSAOTEST" {
2.     Properties {
3.         _Color ("Color", Color) = (1,1,1,1)
4.         _MainTex ("Albedo (RGB)", 2D) = "white" {}
5.         _Glossiness ("Smoothness", Range(0,1)) = 0.5
6.         _Metallic ("Metallic", Range(0,1)) = 0.0
7.         _Smoothness ("Tess smoothness", Range(0,1)) = 0.0
8.     }
9.     SubShader {
10.         Tags { "RenderType"="Opaque" "Queue"="Geometry" }
11.         LOD 200
12.        
13.         CGPROGRAM
14.         // Physically based Standard lighting model, and enable shadows on all light types
15.         #pragma surface surf Standard fullforwardshadows addshadow tessellate:tessEdge tessphong:_Smoothness exclude_path:deferred vertex:vert
16.  
17.         // Use shader model 3.0 target, to get nicer looking lighting
18.         #pragma target 3.0
19.        
20.         struct appdata
21.         {
22.             float4 vertex : POSITION;
23.             float4 tangent : TANGENT;
24.             float3 normal : NORMAL;
25.             float4 color : COLOR;
26.             float2 texcoord : TEXCOORD0;
27.             float2 texcoord1 : TEXCOORD1;
28.             float2 texcoord2 : TEXCOORD2;
29.             float2 texcoord3 : TEXCOORD3;
30.         };
31.  
32.         sampler2D _MainTex;
33.  
34.         struct Input {
35.             float2 uv_MainTex;
36.         };
37.  
38.         half _Glossiness;
39.         half _Smoothness;
40.         half _Metallic;
41.         fixed4 _Color;
42.        
43.         void vert(inout appdata vertex)
44.         {
45.            
46.         }
47.        
48.         float4 tessEdge (appdata v0, appdata v1, appdata v2)
49.         {
50.             return 4;
51.         }
52.  
53.         void surf (Input IN, inout SurfaceOutputStandard o) {
54.             // Albedo comes from a texture tinted by color
55.             fixed4 c = tex2D (_MainTex, IN.uv_MainTex) * _Color;
56.             o.Albedo = c.rgb;
57.             // clip(-1);
58.             // Metallic and smoothness come from slider variables
59.             o.Metallic = _Metallic;
60.             o.Smoothness = _Glossiness;
61.             o.Alpha = c.a;
62.         }
63.         ENDCG
64.     }
65.     FallBack "Diffuse"
66. }
67.  

This does not happen in forward rendering, only deferred.

Is there a way to fix this?

 

Yeah, I thought as much. Unity's own SSAO effect suffers from the same issue. For now I'm resorting to rendering the object 2 times with different materials. That seems to fix it.

The reason I need to exclude the deferred pass is because I'm basically hacking the output of a surface shader to alter the way it behaves, and this does not work in deferred, only forward. So that's why I'm excluding that path to basically force forward render for this shader.

 

I get this issue when using SSAO Pro with custom lighting:



Without SSAO Pro:

Code (CSharp):

1. Shader "Custom/ClipTest" {
2.    
3.     Properties {
4.         _Color ("Color", Color) = (1,1,1,1)
5.         _MainTex ("Albedo (RGB)", 2D) = "white" {}
6.         _Cutoff("Cutoff", Range(0,1)) = 0.0
7.     }
8.     SubShader {
9.         Tags { "RenderType"="AlphaTest" "Queue"="AlphaTest" }
10.         LOD 200
11.        
12.         CGPROGRAM
13.         #pragma surface surf SimpleLambert addshadow alphatest:_Cutoff
14.  
15.         half4 LightingSimpleLambert (SurfaceOutput s, half3 lightDir, half atten) {
16.             half NdotL = dot (s.Normal, lightDir);
17.             half4 c;
18.             c.rgb = s.Albedo * _LightColor0.rgb * (NdotL * atten);
19.             c.a = s.Alpha;
20.             return c;
21.         }
22.        
23.         float4 _Color;
24.  
25.         struct Input {
26.             float2 uv_MainTex;
27.         };
28.        
29.         sampler2D _MainTex;
30.        
31.         void surf (Input IN, inout SurfaceOutput o) {
32.             fixed4 c = tex2D (_MainTex, IN.uv_MainTex);
33.             o.Albedo = _Color;
34.             o.Alpha = c.a;
35.         }
36.         ENDCG
37.     }
38.     FallBack "Diffuse"
39. }

Is there a way to fix this?

 

Amazing, such a simple mistake. Thanks a bunch!

 

I've noticed that performance drops significantly when objects are close to the camera with SSAO on. What is the reason for this?

 

Bug Report.

In Win 10 x64 standalone (both DX11 and 12, deferred), while testing Unity 5.4.0p4, with SSAO Pro 1.6.x enabled we're getting random flashing lines and triangles. They don't occur when SSAO Pro is disabled. Sometimes they are tinted red. Running on an NVidia GTX 780Ti.