Terrain in BattleField 3: A modern, complete, scalable system

-

Multiple raster resources used




Scalability
- arbitrary view distance
- arbitrary lod
- arbitrary velocity

Main observation

Quadtree node payload
- with / without ---?
- used as LODs

payload with LOD
- cost independently on size
- scalable

without LOD  - not scalable





Terrain decoration payloads
 - list of instance transforms ( grass, tree,,)
- according - scattering, shader splatted
- quite unique
- near-root high view distance

Realtime ed in FrostEd


Workflow issue
- compression and runtime editing
- bypass pipeline
- update scheme for procedural content need
- Frostbite terrains too large for some popular tools


Efficient on CPU



Efficient on GPU

GPU optmization: procedural virtual texturing
 - shader splatting ---  rendering slowly
- splatting not scaable in view distance: can't afford mutipass

By splatting into a texture!!!

Virtual texture key values

texture format
- RGBA8
-Indices into virtual texture tile atlas

MegaTexture/TeraTexture
- how reach 1Mx1M
    - indirection texture go 4k x 4k

Clipmap indirection
- resolved on CPU for each draw call

Tile compositing
 benf: small diet footprint, low latency, dynamic update, efficient workflow

Virtual texture issues
- blurriness
-runtime compression quality
-gpu tile cost offset
-limit hw filtering
-compositing latency
-limit at around 32 samples per meter
- two shader splatting: diff, normal,specular, smoothness

Data streaming
- typical tile size: 133x133x2

tile by tile streaming
- for slower gameplay

Tile bundle streaming
Hybrid streaming

Resident set size: powerful blurriness

Blurriness
- mip bias applied to terrain raster streaming
-pipeline trick --- no data is lost, cut tile size in half, addd on leaf level


BF3 blurriness
- cheap raster DX1

physics issue


Reducing disk seeks
- latency
   - co-locate nearby tiles

Improvement throughput
 - data tile are compressed by pipeline
 - incomplete quadtree

Hide latency
  - CLOD
 - global priority

Global priority
-

Procedural mesh generation
-mesh generated from hightailed
-straight-forward tessellation
-patches of 16x16 tris
-proj size roughly size
-blockly creastline

PC
- hightfield sampled in vertex shader


PS3
 - vertex shader fetch texture is too slow
     -  so...?


Mesh stitching
 - modify index, vertex unchange






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