Unity 3 Pro - SSAO issue

Unity Engine
1

Hello!

I recently updated to Unity 3 Pro. Before doing so, I had my camera with an SSAO effect attached to it and it worked fine. After the update, it seems that the ambient occlusion shadow has an offset issue, where the shadow is not attached to the object’s intersecting geometry anymore, but floating somewhere in space. Anyone has this similar issue and know how to fix it?

Many thanks!

Nick.

2

Try importing the new 3.0 Image Effects package and using the updated SSAO from there.

3

I did so, and it seemed to work… but now when I apply the script on my camera, I get the script as ‘deactivated’ in my Inspector window (this means, it will be there, but the tick option is off, and every time I click on it, nothing happens and permanently stays off).

This appears to be an issue between the conversion of the Pro filters from version 2 to version 3… any more thoughts would be greatly appreciated!

Thanks!

4

I just found this in the Reference Manual:

“All image effects automatically disable themselves when they can not run on an end-users graphics card.”

Should I be worried that the script deactivates itself, thinking that it cannot run on my mac? (when it used to work before in version 2)

5

I have the same problem that you have Buff. The ticker does not stay on. If I deactivate the “Camera” script in the Inspector Window, it does though. I have a Geforce M GTS 8800 and I have seen AO work fine in the Bootcamp Demo and other scenes by users on this very machine. So I doubt that the issue is with my hardware.
Anybody here knows what causes this?
Steps to repeat: Load 3rd person demo scene. Select Camera, Apply SSAO script.
I am using the demo of Unity Pro. So it should work, right? Or does the Demo have the same limitations as Unity Free?

6

So, I got it to work with a new scene, but not with any of the example scenes…
Very strange…

7

I can confirm this error. Using Unity3.1.0f4 here.

It is not possible to enable the SSAOEffect component in the camera. I added some debugging outputs to the script and it seems, that the SSAOShader is responsible for this because it returns “m_SSAOShader.isSupported==false”. I’m quite sure my card supports SSAO because I had it running in Unity2.6.

So here’s my fix:

  • Delete the SSAOShader.shader from C:\Users<path_to_unity_project>\Assets\Pro Standard Assets\Image Based\SSAOShader.shader
  • Import the “Image Effects (Pro Only).package”

Now the SSAOShader.shader file will be at another location:
C:\Users<path_to_unity_project>\Assets\Standard Assets\Image Effects (Pro Only)_Sources\Shaders\SSAOShader.shader

This fixes the bug and the SSAO effect on the camera works again.
So to recap:
It seems that the SSAOShader.shader has changed location and Unity3 does not recognize this until you delete the old shader file and import the “Image Effects (Pro Only)” package again.

8

Either that or the other shader was a 2.x shader that was upgraded which for postfx does not work normally