A Vulkan implementation of real-time PBR renderer.
- Video demo available on my homepage
| Paper Mill | Factory |
|---|---|
 |
 |
| Mon Valley | Canyon |
|---|---|
 |
 |
- glTF, also called the GL Transmission Format, it is a runtime asset dilivery format for GL-based applications. It supports common functionalities of 3D applications such as geometry, texture, skin, and animation. It also allows extension, for example, I used the FRAUNHOFER_materials_pbr extension to load PBR textures.
- It aims to form a standard/common format for runtime asset dilivery/exchange. In my opinion, it has better documentation than FBX and possess some abilities that some other file formats don't (e.g. scene hierarchy, skin, animation). I believe, if it gets popular, it will be a great convenience to both application developers and artists because less effort will be required to perform application-specific conversion on file formats.
- In order to show my support, I added glTF support to Laugh Egine. It is now able to load geometry and material data from glTF files.
- Below are some screen shots of 3D models loaded from glTF files. Thanks to Sketchfab for providing these glTF assets and Gary Hsu for the glTF 2.0 test models.
| Microphone (glTF 1.0) | Helmet (glTF 1.0) |
|---|---|
 |
 |
| Boom Box (glTF 2.0) | Lantern (glTF 2.0) |
|---|---|
 |
 |
-
Shadow
- Implemented Cascaded Shadow Map (CSM) for directional lights. The lesson I learned is that having shadow is easy but making it presentable is not. Most of my time was spent in fixing shadow mapping artifacts such as perspective aliasing (multiple pixels mapped to the same shadow map texel), projection aliasing (enlongated, pointy shadow on surfaces that are almost parallel to the light direction), shadow acne, and shadow edge shimmering.
- Tighter orthographic frustum, slope based depth bias, non-uniform frustum split, and PCF are used to mitigate shadow acne and perspective/projective aliasing. To fix the shadow edge flickering problem, I followed the moving light in texel-sized increments idea from DX11 CSM sample. The reason why shadow edge shimmers is that an area of the scene (e.g. a small patch on a floor) is covered by shadow pixels of different sizes/shapes/orientations due to the fact that the orthographic cascade frustums are updated each frame in reponse to camera movement. Therefore, to combact this artifact, we need to fix the sizes and orientations of the orthographic cascade frustums and move them in texel-sized increments. So a patch in the scene is always covered by a shadow map texel of the same size/shape/orientation.
- I render the shadow map for each cascade using different subpasses without inter-dependency in the hope that they will be executed in parallel. However, according the to timeline of RenderDoc capture, it seems that the subpasses are executed sequentially. So I may switch to the geometry shader layered rendering approach in the future. Performance comparison is needed.
Test Scene Cascades Drone Cascades 
Test Scene Drone 
-
Spherical Harmonics Diffuse Lighting
- The lastest update to Laugh Engine implemented spherical harmonics diffuse lighting. It doesn't change too much in terms of speed but it does save a lot of memory and opens up an opportunity for algorithms that bake environment lighting at lots of locations in a scene (e.g. LPV - Light Propogation Volume), which I want to implement in the future.
- For each environment map, only 9 float3 SH coefficients are needed which take up 9 * 12 = 108 bytes in contrast to the 32 * 32 * 6 * 16 = 98,304 bytes storage for a 32x32 cube map which was used to store diffuse irradiance previously. Consequently, a 99.9% saving in space was achieved in my case. In practice, since diffuse irradiance is a low frequency signal, we probably don't need a 32x32 cube map. But even for a 4x4 cube map, using spherical harmonics still result in 93.0% saving in space. Such a huge saving thus justified a little extra computation cost required by SH.
- The following 6 screenshots show the diffuse irradiance recovered using precomputed SH coefficients. It is easy to see that SH successfully captures the tone of the environment (e.g. the bottom of the helmet reflects the yellow tone of desert, the top of the helmet captures the blue sky).
-
Optimized Bloom
- Two optimizations were made to my bloom implementation:
- Performing Gaussian kernel filtering at half resolution
- Taking advantage of hardware linear filtering to halve the number of texture read operations during the blur pass
- The first optimization is easy to understand. For the second one, the basic idea is that we can take advantage of hardware linear filtering feature to fetch two texels in one texture read operation, which is usually much cheaper than doing two texture reads. To do that we need to compute modified weights and texture coordinate offsets that are specific to the size/mean and sigma/stddev of the Gaussian kernel used. For more information, you can refer to this article An investigation of fast real-time GPU-based image blur algorithms.
- Following chart shows the performance difference in milliseconds per frame for different models. Benchmark was performed on a GTX 1080 graphics card.
- Two optimizations were made to my bloom implementation:
-
MSAA
- I implemented MSAA in my custom resolve shader. The basic idea is that for each type of materials, select a representative sample (if there is any), perform lighting calculation using corresponding material model only for the representatives, and finally, colors of all material types are blended together based on the percentage of samples having that type.
- Following chart shows the performance difference between MSAA and SSAA in terms of milliseconds per frame. Performance boost is more salient on models that cover a large portion of the viewport. Test was performed on a GTX 1080 graphics card.
 |
 |
|---|---|
 |
 |
 |
-
Precomputation performance
- It is not real-time but fast enough to be used for interactive editting
- The increase of execution time from 128x128 to 256x256 is very small. Probably the GPU is not saturated at that time.
Envrionment Prefiltering BRDF LUT Baking 
-
PBR vs. Blinn-Phong
- PBR using IBL only
- Blinn-Phong was tested using two point light sources
- Framebuffer resolution was 1920x1080 with no AA
- Bloom was on
- The scene with a Cerberus pistol in it was used for benchmark
- Basically no addtional cost by using PBR over Blinn-Phong but we get much better quality
- Install LunarG Vulkan SDK
- If you have Visual Studio 2015, the solution should build out of the box
- To run the program, you will need to copy the .dlls to executable path or system paths
- Builds on other platforms are not supported yet