Volumetric Ambient Occlusion Image Effect

* Version: 2017.3.0f3 personal
* No difference with single or multi pass
* Vive
* No difference with deferred or forward rendering
* I just purchased/installed VAO
* I don't know what command buffer mode is. I simply added the Volumetric Ambient Occlusions component to the Head/Camera controller.

I'll also add that there is no difference when viewing with one eye or both. I close one eye and I see the same effect.

 

Actually I found that. I turned it on and off. Tried every option in it's drop down. All the same.

 

Just a quick update. I'm still trying to figure out what's going on, but to debug I started a whole new project with nothing added except Steam VR and Volumetric Ambient Occlusions. I didn't touch a single setting or anything, just added the Steam VR camera, the AO, and some cubes to see if it was on or not. No ghosting.

So I'm pretty stumped at the moment, but it must be something I installed or some kind of graphical setting. It also may be to do with using Newton VR, as that is what I installed on my other projects but not this time (for simplicity sake). I did try disabling the Newton VR control and adding a plain Steam VR in the other project and that didn't help, but for all I know just installing Newton may have done something?

I guess I will be trying new blank projects with this and that added or not until I find the problem.

If I figure it out I'll let you know.

 

Good news! VAO is on sale for 30% OFF at:

https://www.assetstore.unity3d.com/en/#!/content/67927

 

I am very eager to try out the free demo 1.9 that supposed to have better performance! And while sale is on would be great!

 

I am sorry about the delay with the demo - I was busy finishing new asset that is in review process at the moment and I am focusing on improving VAO further (currently looking at integration with Unity 2018 Scriptable render pipeline and possibly adding an alternative "classic SSAO" implementation into VAO package)

As of the performance increase between 1.8 and 1.9 - it is real, please see attached screenshot. Measurement was done on my rather old GTX 660 GPU and Unity's Corridor scene. There is about 30% speedup with same (default) settings. Also notice less draw calls (which contributes to performance improvement).

 

I am hoping to try out this asset before deciding which SSAO Unity asset to buy... but I keep getting this error:

InvalidOperationException: Nullable object must have a value.
System.Nullable`1[System.Int32].get_Value () (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System/Nullable.cs:108)
Wilberforce.VAO.Demo.VAOEffect.GetUnityVersion ()
Wilberforce.VAO.Demo.VAOEffect.Start ()

I am using Unity 2018.1 the newest release version. It says 2018 is supported. I figured it might have been because it was part of a project with a lot of other assets, but I tried making a new project, important the demo asset, and still I just get this error. It does convert scripts when importing it, but I expect that should not be a problem if 2018 is supported?

 

Hi,

this code is only part of a Demo package (which was released before Unity 2018 and it fails to recognize it), full version works without problems in Unity 2018. I am working on a new demo that I hope to release soon.

 

That is good to know

 

Pre-release DEMO version of new Volumetric Ambient Occlusion version (1.10) is available -
new version 1.10 will be in the asset store soon. Demo contains all the features but final version will be more optimized for faster build times and possibly contain some bugfixes.

Get the demo here

 

New version (v1.10) has been just released - it features new controls (thickness, borders AO), detail slider, new algorithm option (raycast inspired by Alchemy AO Paper), option to reconstruct normals from depth buffer and bugfixes. Performance has also been improved on some platforms.

Raycast algorithm can be more suitable or have more performance for some scenes than VAO and you can choose whatever works better.

Detail slider - when using large radius you can bring back some fine detail with this control.

Thickness control - enables you to control how far back occlusion reaches from objects

Borders AO - suppresses occlusion on edges of the screen to prevent flickering

Normals reconstruction from depth buffer - in case the normals of your objects are wrong or unavailable, you can reconstruct normals from depth buffer to get correct SSAO

VAO is also now on sale for 50% off !

 

Hello,

does VAO run any faster than post processing v2 AO? Or is it just about visuals?

 

Hi. It is some time since I did last performance comparison with post processing stack but at that time the VAO was faster. However, Post processing stack AO is (was?) set to 2x downsampling out of the box giving faster speed but much lower quality. VAO also supports downsampling (2x/4x) so for testing it should be set to same value. I am away on holiday now so can't test it at this moment but there is a free demo you can try to see if VAO suits your needs:

https://projectwilberforce.github.io/vaodemo/

Performance is also dependent on your scene, how large radius you set and whether you use deferred or forward rendering path.

 

50% off Sale will be ending soon! Get VAO now for reduced price at http://u3d.as/xzs

 

New version (v2.0) has been just released - algorithm has been updated to use temporal accumulation and filtering for much better visual quality and performance

VAO is also now on sale for 60% off !

Asset Store Link: http://u3d.as/xzs

 

Looks interesting, I might buy.

 

Does this work on the high definition render pipeline?

 

Hello,
I need to use AO in my VR project. So I wanted to ask, is this asset efficient enough to use In a VR project? Will it cause any hiccups? (I'm really tight on performance)

 

Hi,

yes it does. Feel free to try out our demo before you buy:

https://projectwilberforce.github.io/vaodemo/

 

Hi,

I bought VAO too for a VR job that I have to finish for a client. I have also ghosting issues on my oculus rift.
Did you find out what caused this problem?

 

Can't find info about compatibility with LWRP/HDRP does VAO support these rendering pipelines?

 

Bought this and it seems to work fine with VR (Oculus Rift S) on Unity 2019.1 inside the Editor, on both the screen and in the headset.

However it doesn't show up on PC/Standalone builds, with or without the headset. I've put some debug-logging in to double-check that the component is definitely still on the camera and enabled, but it's just not showing any AO like it does in the Unity Editor.

Anyone else having this issue?

 

I keep getting an error:

"A multisampled texture being bound to a non-multisampled sampler. Disabling in order to avoid undefined behavior. Please use Texture2DMS in the shader."

The effect works fine though. Unity 2019.3.3, Deferred Rendering.

 

Hi, does this work with URP our of the box?

 

Is this compatible with HDRP ?