• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
codejockey

DX11
Terrain Blend With Pixel Shader

5 posts in this topic

Ok, I'm going to be quite generous with this post as I have seen this terrain blending question being asked repeatedly over and over and over.
I found a good tutorial ([url="http://www.innovativegames.net/blog/blog/2009/05/29/xna-game-engine-tutorial-12-introduction-to-hlsl-and-improved-terrain/"]http://www.innovativ...proved-terrain/[/url]) and I'm going to describe to you folks how to do it.
It uses a pixel shader to do the texture blending.
Only concern I have with it is that it is increadibly slow unless you have multiple channels for your video card. (check out bindless textures on the NVidia video cards [url="http://www.geforce.com/Active/en_US/en_US/pdf/GeForce-GTX-680-Whitepaper-FINAL.pdf"]http://www.geforce.c...paper-FINAL.pdf[/url])
However with the cards that run DX11 these days you'll have to tell me if its quicker because I get around 8 FPS.
With that in mind here's what I have completed that works.
First off your terrain model has to define its UV's to be from 0 to 1.
This is accomplished by dividing the number of vertexes across by 1 and number of vertexes down by 1.
My terrain is 128x128. So we get 0.0078125 and if we loop across starting at 0 when whe arrive at the 128th vertex we'll be at 1.
We can take advantage of this in the pixel shader. Here's how:

Set up a float value for how many times you want the texture to tile across the terrain.

float uvScale01 = 1.0;

in your program you'll have a handle set to this variable:

htexture01MaskScale = shader->effect->GetParameterByName(NULL, "uvScale01");

and you can set the variable from your program:

r = shader->effect->SetFloat(htexture01MaskScale, 1.0f);

This is a mask in mine so I have it stretched across the whole terrain for the blending but if it were a texture you could make the scale something like 32 and it would tile across the whole terrain 32 times.
I'll show you how in a little bit.
Here is the sampler definition for the mask and a texture is just the same.
texture texture01;
sampler2D texture01Sampler = sampler_state
{
texture = texture01;
};
Vertex shader definition:
struct VertexShaderInput
{
float4 pos : POSITION;
float3 norm : NORMAL;
float4 diffuse : COLOR;
float4 specular : COLOR1;
float2 uv1 : TEXCOORD;
float Depth : TEXCOORD1;
float3 vpos : TEXCOORD2;
};
Pixel shader definition:
struct VertexShaderOutput
{
float4 pos : POSITION;
float3 norm : NORMAL;
float4 diffuse : COLOR;
float4 specular : COLOR1;
float2 uv1 : TEXCOORD;
float Depth : TEXCOORD1;
float3 vpos : TEXCOORD2;
};
Not going to go into much detail here but this is how you pass the pixel from the primitive as it relates to the FVF to the pixel shader.
Grabbing the elements to pass to the PS:
VertexShaderOutput VertexShaderFunction(VertexShaderInput input)
{
VertexShaderOutput output;
// directional lighting
lightDir = normalize(lightDir);
output.pos = mul(input.pos, WorldViewProj);
output.vpos = input.pos;
// lighting
output.norm = normalize(mul(input.norm, World));
float d = dot(output.norm, lightDir);
d = clamp(d, ambient, 1.0);
output.diffuse = lightMaterial * d;
output.diffuse.a = 1.0;
output.specular = specularMaterial * d;
output.specular.a = 1.0;
// texture
output.uv1 = input.uv1;
// fog
output.Depth = output.pos.z;
return output;
}
Notice there are normals (vertex normal) and depth and things like that for more than just blending.
Now for the actual blend:
float4 PixelShaderFunction(VertexShaderOutput input) : COLOR0
{
float4 final = {0, 0, 0, 0};
float4 lightMap;
float4 maskMap;
float b1;
float b2;
float4 ts;
// =================================================================================
// Base Terrain Layer 1

final = tex2D(texture16Sampler, input.uv1 * uvScale16);
// =================================================================================
// Terrain Layer 1

maskMap = tex2D(texture01Sampler, input.uv1 * uvScale01);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture02Sampler, input.uv1 * uvScale02);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Terrain Layer 2

maskMap = tex2D(texture03Sampler, input.uv1 * uvScale03);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture04Sampler, input.uv1 * uvScale04);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Terrain Layer 3

maskMap = tex2D(texture05Sampler, input.uv1 * uvScale05);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture06Sampler, input.uv1 * uvScale06);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Terrain Layer 4

maskMap = tex2D(texture07Sampler, input.uv1 * uvScale07);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture08Sampler, input.uv1 * uvScale08);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Terrain Layer 5

maskMap = tex2D(texture09Sampler, input.uv1 * uvScale09);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture10Sampler, input.uv1 * uvScale10);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Terrain Layer 6

maskMap = tex2D(texture11Sampler, input.uv1 * uvScale11);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture12Sampler, input.uv1 * uvScale12);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Terrain Layer 7

maskMap = tex2D(texture13Sampler, input.uv1 * uvScale13);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture14Sampler, input.uv1 * uvScale14);
final = (final * b1) + (ts * b2);
}
// =================================================================================
// Lightmap
// no scaling needed here as it goes across the whole terrain

lightMap = tex2D(texture15Sampler, input.uv1);
final *= lightMap;
// =================================================================================
// Fog
#include "fog.fxh"
// =================================================================================
// Return Color
final.a = 1.0;
return final;
}
technique terrainBlend
{
pass
{
#include "samplerStates.fxh"
VertexShader = compile vs_3_0 VertexShaderFunction();
PixelShader = compile ps_3_0 PixelShaderFunction();
}
}
Yup 7 layers of textures and a lightmap to boot. Ok looks a little daunting at first but here is what it is doing.
final is the returned pixel color and texture16 (0-15 samplers) is scaled (tiled) across the terrrain at scale16 times.
This is the base texture for the whole terrain.
final = tex2D(texture16Sampler, input.uv1 * uvScale16);
Then blend texture02Sampler with a bitmap mask or whatever mask you have defined. The mask just needs to be 24 bit and I use bmp's for the mask even though I uploaded a jpg. IE just doesn't want to display a bmp.
// =================================================================================
// Terrain Layer 1

maskMap = tex2D(texture01Sampler, input.uv1 * uvScale01);
if (maskMap.r > 0.0)
{
b1 = 1.0 - maskMap.r;
b2 = 1.0 - b1;
ts = tex2D(texture02Sampler, input.uv1 * uvScale02);
final = (final * b1) + (ts * b2);
}

Here's the code to get the shader script executed:
r = shader->effect->Begin(&shader->passes, NULL);
for (UINT x=0;x<shader->passes;x++)
{
r = shader->effect->BeginPass(x);
r = graphics->device->DrawIndexedPrimitive(D3DPT_TRIANGLELIST, 0, 0, nbrVert, 0, count);

r = shader->effect->EndPass();
}
r = shader->effect->End();
I used an indexed list of vertexes but you can use drawprimitive if you like. Not sure what you application is.

And thats all there is to it. It looks real nice when you get the shader script working and you don't need 12x128x2 triangles to do the blend.
You can actually do it on 1 triangle so you should be able to apply this to any form of texture blending that you may need.

PS. Fog way to cool.

float fogStart = 256.0;
float fogEnd = 4096.0;
float fogDensity = 0;
float minFog = 0.0;
float maxFog = 1.0;
float3 fogColor = {0.85, 0.85, 0.85};
if (fogDensity > 0)
{
float fog = (input.Depth - fogStart) / (fogEnd - fogStart);
fog *= fogDensity;
fog = clamp(fog, minFog, maxFog);
final = lerp(final, float4(fogColor, 1.0), fog);
}

Oh and one final note, you don't have to do just textures for a terrain. You can use a normal map and do per pixel bump mapping for dynamic lighting.

final = tex2D(texture01Sampler, input.uv1);
normalMap = tex2D(texture02Sampler, input.uv1);
NdL = dot(lightDir, normalMap);
final *= NdL;

let's not forget to make the alpha channel of the pixel 1 so it does't blend with itself.

final.a = 1.0;

And a really, really good texture artist is a must for making a real nice looking terrain so you don't get the fish net looking tiling from a semi-seemless texture pack. Way to go Id Software. http://www.moddb.com/games/enemy-territory-quake-wars/addons/mega-texture-media-pack


and voila! Happy terraining! Edited by codejockey
1

Share this post


Link to post
Share on other sites
+1 for sharing [img]http://public.gamedev.net//public/style_emoticons/default/biggrin.png[/img]
[quote name='Butabee' timestamp='1351048605' post='4993328']Getting rid of the if statements should speed it up.[/quote]^this, and using lerp is a lot faster than manually writing linear interpolation math. I'd also pack all the masks together to reduce the number of texture fetches:
e.g. http://pastebin.com/KfEw0sjW Edited by Hodgman
0

Share this post


Link to post
Share on other sites
You could also do dynamic branching to avoid texture fetches for textures that have zero for their mask (right now you're always doing all 16 texture fetches).

To do this you'll need to add the [branch] attribute before each if statement, and then switch from using tex2D to tex2Dlod (and calculate the miplevel manually outside the branch ([url="http://www.gamedev.net/blog/73/entry-1692117-terrain-texturing-explained/"]see here for an example[/url])).

I gotten significant performance improvements from doing this.

Of course this would only make sense if you have large portions of your terrain where the mask is 0 for some textures. Edited by phil_t
0

Share this post


Link to post
Share on other sites
"I gotten significant performance improvements from doing this."

That one is using a sheet of seemless textures which is only ONE texture and they calulate the UV coords in the shader to arrive at the seemless texture.

I'm new/noob to pixel shaders and the math so I'm sure mine won't ever be improved until I manage to get a further education in mathmatics and video game programming at a industry professional level. Just something to help the curious. Edited by codejockey
0

Share this post


Link to post
Share on other sites
I know it's different than what you're doing, I was just using it as an example of how to calculate the mipmap level manually (so you can use tex2Dlod, which lets you put texture sampling operations inside a dynamic branch that the GPU can actually skip).
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Similar Content

    • By lonewolff
      Hi Guys,
      I am just wondering if it is possible to acquire the address of the backbuffer if an API (based on DX11) only exposes the 'device' and 'context' pointers?
      Any advice would be greatly appreciated
    • By MarcusAseth
      bool InitDirect3D::Init() { if (!D3DApp::Init()) { return false; } //Additional Initialization //Disable Alt+Enter Fullscreen Toggle shortkey IDXGIFactory* factory; CreateDXGIFactory(__uuidof(IDXGIFactory), reinterpret_cast<void**>(&factory)); factory->MakeWindowAssociation(mhWindow, DXGI_MWA_NO_WINDOW_CHANGES); factory->Release(); return true; }  
      As stated on the title and displayed on the code above, regardless of it Alt+Enter still takes effect...
      I recall something from the book during the swapChain creation, where in order to create it one has to use the same factory used to create the ID3D11Device, therefore I tested and indeed using that same factory indeed it work.
      How is that one particular factory related to my window and how come the MakeWindowAssociation won't take effect with a newly created factory?
      Also what's even the point of being able to create this Factories if they won't work,?(except from that one associated with the ID3D11Device) 
    • By ProfL
      Can anyone recommend a wrapper for Direct3D 11 that is similarly simple to use as SFML? I don't need all the image formats etc. BUT I want a simple way to open a window, allocate a texture, buffer, shader.
    • By lucky6969b
      Q1:
      Since there is no more fixed pipeline rendering in DX11, for every part of rendering in DX11, do I need to create a brand-new vertex shader and pixel shader... or at least I have to find one relevant online. If you work on skinned meshes and other effects originally worked in DX9 fixed pipeline, do I have to rework everything by now?
       
      Q2:
      For assimp, if it originally was designed for DX9, like it is coupled to a DX9 device for creating meshes and materials etc. Do I have to add in the DX11 device in the assimp, or can I just leave the assimp to remain in DX9 and after the meshes are loaded, I just convert the vertex buffers and index buffers into DX11 buffers?
      Thanks
      Jack
    • By MarcusAseth
      This header is mentioned in the book I'm reading but there is no documentation on msdn... Is it like an... outdated and abandoned header?
      If so, what's the current default/recomended library for handling errors with directX?
  • Popular Now