Ambient Occlusion Fields and Decals in Infamous 2

-



Infanous2
 - deferred- shadering
  - vertex-baked AO

AO - large or small scale
Baked-great but

SSAO great but...


Hybrid approach


 - complement AO . SSAO
 - medium sscale
-  in world space: precompute AO




AO Fields
   - precomputing
      - volume texture
      - voxel is occlusion cone
      - render geometry into 32x32 cube map
      -  read back
   - Applying
            - draw bounding box, pixel shader retrieve world pos
             - blending result into G buffer AO channel using mutltuitive blending
   - Texture details
       size chosen by artist
        format: 8bit RGBA, not DXT
   - Visible Boundary
        - remap alpha values at build time
                - find max alpha value of all voxel
    - incorrect self- occlusion
            - ideally detect interior voxels and fix up



AO decal
    : planar ver. of AO field
    - use cased: thin objects embedded
   - precomputing: store as 2d texture
    - render height map of source geometry
            - parallel projection looking at/floor from front
           
    - applying
         - same as AO field.
          - rgba, depth channel
    - details
         - BB size use 0.7 epsilon instead of 0.25
         - tex size is 64-128 each axis
          - DXT5 format
    - Halos around height changes
           - sol:
     - Edges too soft
            - sol: bake wall-occlusion onto vertices

Fields/ Decals memory used

Fields/ Decals  performance

Future enhancement
    - faster precompute
    - on character
   - undersampling better



Comments

Post a Comment

Popular posts from this blog

Drawing textured cube with Vulkan on Android

-
Image
Vulkan is a modern hardware-accelerated Graphics API. Its goal is providing an high efficient way in low-level graphics and compute on modern GPUs for PC, mobile, and embedded devices. I am personally working a self training project, vulkan-android , to teach myself how to use this new APIs. The difference between OpenGL and Vulkan OpenGL: Higher level API in comparison with Vulkan, and the next generation of OpenGL 4 will be Vulkan.   Cross-platform and Cross-language (mostly still based on C/C++, but people implemented diverse versions and expose similar API binding based on OpenGL C++, WebGL is a good example).  Mainly used in 3D graphics and 2D image processing to interact with GPU in order to achieve hardware acceleration. Don't have a command buffer can be manipulated at the application side. That means we will be easily see draw calls being the performance bottleneck in a big and complex 3D scene. Vulkan: Cross-platform and low-overhead. Erase the boundary bet...
Read more

glTF loader for Android Vulkan

-
Image
This post is going to introduce how we integrate with an existing glTF loader library to make it be able to show glTF models in our Vulkan rendering framework,  vulkan-android . tinygltf In the beginning, we don't want to make our new own wheel, so choosing  tinygltf as our glTF loader. tinygltf is a C++11 based library that would help us support all possible cross-platform project easily. tinygltf setup in Android Studio In  vulkan-android  project, we put third party libraries into third_party folder. Therefore, we need to include tinygltf from third_party folder in app/CMakeLists.txt as below. set(THIRD_PARTY_DIR ../../third_party) include_directories(${THIRD_PARTY_DIR}/tinygltf) Model loading from tinygltf We are going to load a gltf ASCII or binary format model from the storage. tinygltf provides two APIs , they are LoadBinaryFromFile() and LoadASCIIFromFile() respectively based on the extension name is *.glb or *.gltf. TinyGLTF loader will return a tiny...
Read more

C++ unit testing & CI integration in GitHub (I/2)

-
Image
I am working on a side project,  Vulkan-Android , that is based on Java, JNI, C++, and Vulkan for Android platform. It also uses my C++ math library. Therefore, the requirement of my build and unit tests are around C++. First of all, I would make sure the unit tests in local are run properly. C++ unit test on Mac OS On Mac OS, I think the most convenient way to do unit testing for C++ is writing XCT in Xcode. In the beginning, we need to create a test plan in Xcode. It will helps us create a schema, then, in the test navigator, create a new Unit Test Target. Due to XCT was originally designed for Objective-C or Swift, if we wanna test our C++ code, we need a workaround by making the file extension name to be *.mm . And then, write down the unit tests as below: #import <XCTest/XCTest.h> #include "Vector3d.h" using namespace gfx_math; @interface testVector3D : XCTestCase @end @implementation testVector3D - (void)setUp { // Put setup code here. This method is cal...
Read more