• Advertisement
Sign in to follow this  

DX11 Chunked LOD vs Tesselated Terrain

This topic is 2269 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I've written a basic DX11 terrain engine using the new tessellation stages, but it currently uses fixed sized patches. Given that my game allows the player to zoom right in or out I need to use a quad tree or similar to vary the size of the patches based on viewing distance...

Most Terrain articles that talk about quadtrees assume that you're using Chunked LOD and not Tessellation. As I looked into it more I started to realise that Chunked LOD (With morphing between the levels) is very simple and gives excellent results with zero popping.

So, what is the advantage of using tessellation over normal Chunked LOD (Including morphing)?

Making the terrain watertight with different sized patches is a pain with tessellation. Chunked LOD simply uses skirts, which whilst doesn't appear to be an elegant solution, its much simpler and gives perfect results.

I believe the main difference between the 2 techniques is the way the terrain morphs between levels. With Chunked LOD every other vertex morphs vertically at the same time as you move between levels. With Tessellation the new verticies emerge from existing veritices and then move horizontally to the final position.

Personally I would have thought that the vertical morphing of Chunked LOD would look less strange than the horizontal mophing you get from tessellation.

Thanks
Ben

Share this post


Link to post
Share on other sites
Advertisement
Chunked LOD terrain is a bit outdated.
Today's version is GeoMipMapping. I believe GeoClipMapping to be even more efficient, but GeoMipMapping is close enough for the simplicity in implementation given that you already have a chunk system.

Also, LOD is not determined by distance, but by how much space the object occupies on the screen. If you went by distance alone and the player uses a sniper rifle, hilarity will ensue.


L. Spiro

Share this post


Link to post
Share on other sites
You can either use heightmap based Chunked LoD, which is simple and fast, with some metric for LoD, or tessellate & displace your terrain on GPU given a heightmap.
And alternative is to use vector maps instead of height maps to allow for overhang and such, check Halo Reach presentation about that.

In Shogun 2, I chose Chunked LoD to replace geomipmapping.
Keep in mind you might pick up a different solution given your requirements...

Share this post


Link to post
Share on other sites
Sure I'm aware of GeoMipMapping and ClipMapping but I fail to see how they are in any way better than Chunked LOD. Chunked LOD is both simple and gives perfect transitions between detail levels.

Thanks
Ben

PS. Apologies if my response seems a bit 'short', I've only got a minute between meetings.

Share this post


Link to post
Share on other sites
[quote name='YogurtEmperor' timestamp='1320120115' post='4879130']
Chunked LOD terrain is a bit outdated.
Today's version is GeoMipMapping
[/quote]

Has hardware changed in some way that made GMM worthwhile again? I haven't really kept up with this stuff since ChunkedLOD took over from GMM as the method du jour.

That is:

GMM - 2000
ChunkedLOD - 2002
GeoClipMaps - 2004

IIRC the error metric used in the GMM paper is much rougher than that in ChunkedLOD. The LOD models GMM (and I'm guessing GeoClipMaps) generates are nowhere near as good as ChunkedLOD - this is because of the arbitrary sampling used to select vertices at each LOD, whereas ChunkedLOD actually uses the potential screen space error per vertex and selects the most important vertices, IIRC.

But there's no reason not to mix and match. How about ChunkedLOD with adaptive tessellation to refine silhouette edges?

Share this post


Link to post
Share on other sites
[quote]
Making the terrain watertight with different sized patches is a pain with tessellation.
[/quote]

I do not understand the problem? Can't you make a grid of quad patches. Tessellate each patch based on some metric (distance/screenspace coverage). Also be sure to tessellate each edge based only on edge properties so it is watertight.

Share this post


Link to post
Share on other sites
[quote name='Quat' timestamp='1320170458' post='4879313']
[quote]
Making the terrain watertight with different sized patches is a pain with tessellation.
[/quote]

I do not understand the problem? Can't you make a grid of quad patches. Tessellate each patch based on some metric (distance/screenspace coverage). Also be sure to tessellate each edge based only on edge properties so it is watertight.
[/quote]

There are 2 problems:
1. If you have an edge A -> B and tessellate it with a factor such as 4.3 and then on the neighbouring tile that edge becomes B -> A (Due to winding order) and tesselate that with a factor or 4.3 then its no longer watertight. You have to either stick with integer tesselation factors at the edges (In which case you will get popping when you change values), or you have to do tricks to the winding order to ensure the edges are always tesellated in the same order.

2. The other problem is how do you know what your neighbouring tiles size is? A single tile of size 64x64 could have, on a single side, multiple neighbours of different sized tiles, e.g. four tiles of sizes 32, 16, 8, 8.

Thanks
Ben

Edit: Although I guess you could just use Skirts, just like with Chunked LOD.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By mister345
      Hi, can somebody please tell me in clear simple steps how to debug and step through an hlsl shader file?
      I already did Debug > Start Graphics Debugging > then captured some frames from Visual Studio and
      double clicked on the frame to open it, but no idea where to go from there.
       
      I've been searching for hours and there's no information on this, not even on the Microsoft Website!
      They say "open the  Graphics Pixel History window" but there is no such window!
      Then they say, in the "Pipeline Stages choose Start Debugging"  but the Start Debugging option is nowhere to be found in the whole interface.
      Also, how do I even open the hlsl file that I want to set a break point in from inside the Graphics Debugger?
       
      All I want to do is set a break point in a specific hlsl file, step thru it, and see the data, but this is so unbelievably complicated
      and Microsoft's instructions are horrible! Somebody please, please help.
       
       
       

    • By mister345
      I finally ported Rastertek's tutorial # 42 on soft shadows and blur shading. This tutorial has a ton of really useful effects and there's no working version anywhere online.
      Unfortunately it just draws a black screen. Not sure what's causing it. I'm guessing the camera or ortho matrix transforms are wrong, light directions, or maybe texture resources not being properly initialized.  I didnt change any of the variables though, only upgraded all types and functions DirectX3DVector3 to XMFLOAT3, and used DirectXTK for texture loading. If anyone is willing to take a look at what might be causing the black screen, maybe something pops out to you, let me know, thanks.
      https://github.com/mister51213/DX11Port_SoftShadows
       
      Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.
      https://github.com/mister51213/DX11Port_ShadowMapping
       
    • By xhcao
      Is Direct3D 11 an api function like glMemoryBarrier in OpenGL? For example, if binds a texture to compute shader, compute shader writes some values to texture, then dispatchCompute, after that, read texture content to CPU side. I know, In OpenGL, we could call glMemoryBarrier before reading to assure that texture all content has been updated by compute shader.
      How to handle incoherent memory access in Direct3D 11? Thank you.
    • By _Engine_
      Atum engine is a newcomer in a row of game engines. Most game engines focus on render
      techniques in features list. The main task of Atum is to deliver the best toolset; that’s why,
      as I hope, Atum will be a good light weighted alternative to Unity for indie games. Atum already
      has fully workable editor that has an ability to play test edited scene. All system code has
      simple ideas behind them and focuses on easy to use functionality. That’s why code is minimized
      as much as possible.
      Currently the engine consists from:
      - Scene Editor with ability to play test edited scene;
      - Powerful system for binding properties into the editor;
      - Render system based on DX11 but created as multi API; so, adding support of another GAPI
        is planned;
      - Controls system based on aliases;
      - Font system based on stb_truetype.h;
      - Support of PhysX 3.0, there are samples in repo that use physics;
      - Network code which allows to create server/clinet; there is some code in repo which allows
        to create a simple network game
      I plan to use this engine in multiplayer game - so, I definitely will evolve the engine. Also
      I plan to add support for mobile devices. And of course, the main focus is to create a toolset
      that will ease games creation.
      Link to repo on source code is - https://github.com/ENgineE777/Atum
      Video of work process in track based editor can be at follow link: 
       
       

    • By mister345
      I made a spotlight that
      1. Projects 3d models onto a render target from each light POV to simulate shadows
      2. Cuts a circle out of the square of light that has been projected onto the render target
      as a result of the light frustum, then only lights up the pixels inside that circle 
      (except the shadowed parts of course), so you dont see the square edges of the projected frustum.
       
      After doing an if check to see if the dot product of light direction and light to vertex vector is greater than .95
      to get my initial cutoff, I then multiply the light intensity value inside the resulting circle by the same dot product value,
      which should range between .95 and 1.0.
       
      This should give the light inside that circle a falloff from 100% lit to 0% lit toward the edge of the circle. However,
      there is no falloff. It's just all equally lit inside the circle. Why on earth, I have no idea. If someone could take a gander
      and let me know, please help, thank you so much.
      float CalculateSpotLightIntensity(     float3 LightPos_VertexSpace,      float3 LightDirection_WS,      float3 SurfaceNormal_WS) {     //float3 lightToVertex = normalize(SurfacePosition - LightPos_VertexSpace);     float3 lightToVertex_WS = -LightPos_VertexSpace;          float dotProduct = saturate(dot(normalize(lightToVertex_WS), normalize(LightDirection_WS)));     // METALLIC EFFECT (deactivate for now)     float metalEffect = saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace)));     if(dotProduct > .95 /*&& metalEffect > .55*/)     {         return saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace)));         //return saturate(dot(SurfaceNormal_WS, normalize(LightPos_VertexSpace))) * dotProduct;         //return dotProduct;     }     else     {         return 0;     } } float4 LightPixelShader(PixelInputType input) : SV_TARGET {     float2 projectTexCoord;     float depthValue;     float lightDepthValue;     float4 textureColor;     // Set the bias value for fixing the floating point precision issues.     float bias = 0.001f;     // Set the default output color to the ambient light value for all pixels.     float4 lightColor = cb_ambientColor;     /////////////////// NORMAL MAPPING //////////////////     float4 bumpMap = shaderTextures[4].Sample(SampleType, input.tex);     // Expand the range of the normal value from (0, +1) to (-1, +1).     bumpMap = (bumpMap * 2.0f) - 1.0f;     // Change the COORDINATE BASIS of the normal into the space represented by basis vectors tangent, binormal, and normal!     float3 bumpNormal = normalize((bumpMap.x * input.tangent) + (bumpMap.y * input.binormal) + (bumpMap.z * input.normal));     //////////////// LIGHT LOOP ////////////////     for(int i = 0; i < NUM_LIGHTS; ++i)     {     // Calculate the projected texture coordinates.     projectTexCoord.x =  input.vertex_ProjLightSpace[i].x / input.vertex_ProjLightSpace[i].w / 2.0f + 0.5f;     projectTexCoord.y = -input.vertex_ProjLightSpace[i].y / input.vertex_ProjLightSpace[i].w / 2.0f + 0.5f;     if((saturate(projectTexCoord.x) == projectTexCoord.x) && (saturate(projectTexCoord.y) == projectTexCoord.y))     {         // Sample the shadow map depth value from the depth texture using the sampler at the projected texture coordinate location.         depthValue = shaderTextures[6 + i].Sample(SampleTypeClamp, projectTexCoord).r;         // Calculate the depth of the light.         lightDepthValue = input.vertex_ProjLightSpace[i].z / input.vertex_ProjLightSpace[i].w;         // Subtract the bias from the lightDepthValue.         lightDepthValue = lightDepthValue - bias;         float lightVisibility = shaderTextures[6 + i].SampleCmp(SampleTypeComp, projectTexCoord, lightDepthValue );         // Compare the depth of the shadow map value and the depth of the light to determine whether to shadow or to light this pixel.         // If the light is in front of the object then light the pixel, if not then shadow this pixel since an object (occluder) is casting a shadow on it.             if(lightDepthValue < depthValue)             {                 // Calculate the amount of light on this pixel.                 float lightIntensity = saturate(dot(bumpNormal, normalize(input.lightPos_LS[i])));                 if(lightIntensity > 0.0f)                 {                     // Determine the final diffuse color based on the diffuse color and the amount of light intensity.                     float spotLightIntensity = CalculateSpotLightIntensity(                         input.lightPos_LS[i], // NOTE - this is NOT NORMALIZED!!!                         cb_lights[i].lightDirection,                          bumpNormal/*input.normal*/);                     lightColor += cb_lights[i].diffuseColor*spotLightIntensity* .18f; // spotlight                     //lightColor += cb_lights[i].diffuseColor*lightIntensity* .2f; // square light                 }             }         }     }     // Saturate the final light color.     lightColor = saturate(lightColor);    // lightColor = saturate( CalculateNormalMapIntensity(input, lightColor, cb_lights[0].lightDirection));     // TEXTURE ANIMATION -  Sample pixel color from texture at this texture coordinate location.     input.tex.x += textureTranslation;     // BLENDING     float4 color1 = shaderTextures[0].Sample(SampleTypeWrap, input.tex);     float4 color2 = shaderTextures[1].Sample(SampleTypeWrap, input.tex);     float4 alphaValue = shaderTextures[3].Sample(SampleTypeWrap, input.tex);     textureColor = saturate((alphaValue * color1) + ((1.0f - alphaValue) * color2));     // Combine the light and texture color.     float4 finalColor = lightColor * textureColor;     /////// TRANSPARENCY /////////     //finalColor.a = 0.2f;     return finalColor; }  
      Light_vs.hlsl
      Light_ps.hlsl
  • Advertisement