» Fri May 27, 2011 2:09 pm Screen Space Ambient Occlusion (SSAO) is a rendering technique for efficiently approximating the well-known computer graphics ambient occlusion effect in real time. It was used for the first time in a video game in the 2007 PC game Crysis made by Crytek.
The algorithm is executed purely on the computer's GPU and implemented as a pixel shader, anolyzing the scene depth buffer which is stored in a texture. For every pixel on the screen, the pixel shader samples the depth values around the current pixel and tries to compute the amount of occlusion from each of the sampled points. In its simplest implementation, the occlusion factor depends only on the depth difference between sampled point and current point.
Without additional smart solutions, such a brute force method would require about 200 texture reads per pixel for good visual quality. This is not acceptable for real-time rendering on modern graphics hardware. In order to get high quality results with far fewer reads, sampling is performed using a randomly-rotated kernel. The kernel orientation is repeated every N screen pixels in order to have only high-frequency noise in the final picture. In the end this high frequency noise is greatly removed by a NxN post-process blurring step taking into account depth discontinuities (using methods such as comparing adjacent normals and depths). Such a solution allows a reduction in the number of depth samples per pixel to about 16 or less while maintaining a high quality result, and allows the use of SSAO in real-time applications like computer games.
Compared to other ambient occlusion solutions, SSAO has following advantages:
* Independent from scene complexity.
* No data pre-processing needed, no loading time and no memory allocations in system memory.
* Works with dynamic scenes.
* Works in the same consistent way for every pixel on the screen.
* No CPU usage ? it is executed completely on the GPU.
* May be easily integrated into any modern graphics pipeline.
Of course, it has its disadvantages, as well:
* Rather local and in many cases view-dependent, as it is dependent on adjacent texel depths which may be generated by any geometry whatsoever.
* Hard to correctly smooth/blur out the noise without interfering with depth discontinuities, such as object edges (the occlusion should not "bleed" onto objects).
The algorithm is executed purely on the computer's GPU and implemented as a pixel shader, anolyzing the scene depth buffer which is stored in a texture. For every pixel on the screen, the pixel shader samples the depth values around the current pixel and tries to compute the amount of occlusion from each of the sampled points. In its simplest implementation, the occlusion factor depends only on the depth difference between sampled point and current point.
Without additional smart solutions, such a brute force method would require about 200 texture reads per pixel for good visual quality. This is not acceptable for real-time rendering on modern graphics hardware. In order to get high quality results with far fewer reads, sampling is performed using a randomly-rotated kernel. The kernel orientation is repeated every N screen pixels in order to have only high-frequency noise in the final picture. In the end this high frequency noise is greatly removed by a NxN post-process blurring step taking into account depth discontinuities (using methods such as comparing adjacent normals and depths). Such a solution allows a reduction in the number of depth samples per pixel to about 16 or less while maintaining a high quality result, and allows the use of SSAO in real-time applications like computer games.
Compared to other ambient occlusion solutions, SSAO has following advantages:
* Independent from scene complexity.
* No data pre-processing needed, no loading time and no memory allocations in system memory.
* Works with dynamic scenes.
* Works in the same consistent way for every pixel on the screen.
* No CPU usage ? it is executed completely on the GPU.
* May be easily integrated into any modern graphics pipeline.
Of course, it has its disadvantages, as well:
* Rather local and in many cases view-dependent, as it is dependent on adjacent texel depths which may be generated by any geometry whatsoever.
* Hard to correctly smooth/blur out the noise without interfering with depth discontinuities, such as object edges (the occlusion should not "bleed" onto objects).
It's one of those things that make's the game look a whole lot better, while also taking up a fair amount of resources.
EDIT: Before and after pics from this very same thread courtesy of Hawklyfox: http://img502.imageshack.us/img502/1992/screenshot21g.jpg / http://img46.imageshack.us/img46/3802/screenshot20p.jpg --- http://img38.imageshack.us/img38/5817/screenshot23e.jpg / http://img502.imageshack.us/img502/5694/screenshot22d.jpg
Ravin
