Skip to main content
GameDev.net gamedev.net
🔒 Locked

Normal Interpolation issues on my generated terrain

DX11
Started by Corefanatic Jan 22, 2013 at 11:10 PM 8 replies 3.5k views
Original Post
Corefanatic
Corefanatic

Hi all,
I am having a weird problem with normals on my generated terrain. I am not sure whether is it is shader or mesh issue, but here is how it looks:




Dx11FW%202013-01-22%2022-51-45-78.png

As you can see, I get this pattern along the edges of the triangles. This reminds me of per vertex shading however I am aiming for per pixel shading.

Here are my vertex and pixel shaders:

VS:


cbuffer cbToProjection
{
	float4x4 matToProj;
}

struct VS_IN
{
	float4 Position : POSITION;
	float3 Normal: NORMAL;
};

struct VS_OUT
{
	float4 Position : SV_POSITION;
	float3 NormalWS: TEXCOORD1;
};

VS_OUT main(VS_IN IN)
{
	VS_OUT OUT;
	OUT.Position = mul(IN.Position,matToProj);
	OUT.NormalWS = normalize(IN.Normal);
	return OUT;
}

PS:


struct PS_IN
{
	float4 Position : SV_POSITION;
	float3 NormalWS: TEXCOORD1;
};

float4 main(PS_IN IN): SV_TARGET0 {
	float3 normal = normalize(IN.NormalWS);
	float3 toLight = normalize(float3(1,3,-2));
	float NDotL = saturate(dot(toLight,normal));
	float4 color = float4(1.0f,1.0f,1.0f,1.0f);	
	color.rgb *= NDotL;
	return color;
}

so what am I doing wrong?

Jason Z
Jason Z

From your shader code, it looks like you are doing this correctly (although you could remove the normalize call on the normal vector in the VS since you renormalize in the PS after rasterization). My guess is that your terrain is defining three vertices for each triangle face, rather than one vertex at each grid point. You can verify this by checking the number of vertices you are passing in with your draw call, or you can also check this with PIX/Graphics Debugger to see how many primitives are generated from how many input vertices.

Jason Zink :: DirectX MVP   Direct3D 11 engine on CodePlex: Hieroglyph 3 Direct3D Books: 
Corefanatic
Corefanatic
From your shader code, it looks like you are doing this correctly (although you could remove the normalize call on the normal vector in the VS since you renormalize in the PS after rasterization). My guess is that your terrain is defining three vertices for each triangle face, rather than one vertex at each grid point. You can verify this by checking the number of vertices you are passing in with your draw call, or you can also check this with PIX/Graphics Debugger to see how many primitives are generated from how many input vertices.

So, I moved the rendering into indexed rendering, so there is only one normal per vertex and still get same result.

nfactorial
nfactorial

Have you tried with different light directions? The dark areas simply look like they are dark because they are facing away from the parallel light you have hard-coded in your shader (ie. the dark sections are always on the -z axis in your image).

It may also be worth outputing the normal to the frame buffer so you can visually see any issues with the interpolation.

eg: change your color computation (in the pixel shader to) to:

color = normal * 0.5f + 0.5f;

return color;

You can also change your light vector so that it's always directly above the terrain (float3 toLight = float3( 0.0f, 1.0f, 0.0f );) which should give you a more even lighting across the terrain, again helping to see any issue with the normals. With the off-center light angle, it makes it difficult to say what is wrong really sorry :) But, certainly, your shader code looks fine. If it isn't the light direction confusing you, then it maybe the normals themselves.

My first guess is just that the light is at an angle really ;)

n!

nfactorial
nfactorial

It could also be that I'm misunderstanding what you're complaining about.

Sometimes people build their terrain such that the vertices look like:

pW3fUDy.jpg

Whereas you can avoid some artifacts on terrain lighting if you structure your vertices like:

ZO7pxKa.jpg

n!

Jason Z
Jason Z
From your shader code, it looks like you are doing this correctly (although you could remove the normalize call on the normal vector in the VS since you renormalize in the PS after rasterization). My guess is that your terrain is defining three vertices for each triangle face, rather than one vertex at each grid point. You can verify this by checking the number of vertices you are passing in with your draw call, or you can also check this with PIX/Graphics Debugger to see how many primitives are generated from how many input vertices.

So, I moved the rendering into indexed rendering, so there is only one normal per vertex and still get same result.

That may or may not mean that there is exactly one vertex normal being used at each grid point. How many vertices are in your vertex buffer, how many indices in your index buffer, and how many primitives are you drawing? Compare that with your grid size and make sure that you only have N+1 x N+1 vertices for a grid of size N x N.

Jason Zink :: DirectX MVP   Direct3D 11 engine on CodePlex: Hieroglyph 3 Direct3D Books: 
Corefanatic
Corefanatic

Have you tried with different light directions? The dark areas simply look like they are dark because they are facing away from the parallel light you have hard-coded in your shader (ie. the dark sections are always on the -z axis in your image).

It may also be worth outputing the normal to the frame buffer so you can visually see any issues with the interpolation.

eg: change your color computation (in the pixel shader to) to:

color = normal * 0.5f + 0.5f;

return color;

You can also change your light vector so that it's always directly above the terrain (float3 toLight = float3( 0.0f, 1.0f, 0.0f );) which should give you a more even lighting across the terrain, again helping to see any issue with the normals. With the off-center light angle, it makes it difficult to say what is wrong really sorry smile.png But, certainly, your shader code looks fine. If it isn't the light direction confusing you, then it maybe the normals themselves.

My first guess is just that the light is at an angle really ;)

n!

Setting the light to 0,1,0 doesn't help, the problem persists. Rendering the normals into the frame buffer shows the same problem.

It could also be that I'm misunderstanding what you're complaining about.

Sometimes people build their terrain such that the vertices look like:

pW3fUDy.jpg

Whereas you can avoid some artifacts on terrain lighting if you structure your vertices like:

ZO7pxKa.jpg

n!

I am building the mesh the way shown in the first picture, will try the other way that thanks.


From your shader code, it looks like you are doing this correctly (although you could remove the normalize call on the normal vector in the VS since you renormalize in the PS after rasterization). My guess is that your terrain is defining three vertices for each triangle face, rather than one vertex at each grid point. You can verify this by checking the number of vertices you are passing in with your draw call, or you can also check this with PIX/Graphics Debugger to see how many primitives are generated from how many input vertices.

So, I moved the rendering into indexed rendering, so there is only one normal per vertex and still get same result.

That may or may not mean that there is exactly one vertex normal being used at each grid point. How many vertices are in your vertex buffer, how many indices in your index buffer, and how many primitives are you drawing? Compare that with your grid size and make sure that you only have N+1 x N+1 vertices for a grid of size N x N.

For a 16x16 grid, there are 256 vertices, index buffer holds 1350 indices

Corefanatic
Corefanatic

It could also be that I'm misunderstanding what you're complaining about.

Sometimes people build their terrain such that the vertices look like:

pW3fUDy.jpg

Whereas you can avoid some artifacts on terrain lighting if you structure your vertices like:

ZO7pxKa.jpg

n!

So, I tried building the mesh as in the second image, unfortunately the problems did not go away.

16x16 mesh:

Dx11FW%202013-01-24%2022-50-58-53.png

normals:

Dx11FW%202013-01-24%2023-01-47-90.png

nfactorial
nfactorial
Hey, thanks for the images. The lighting in the first one shows your problem much clearer for me.It looks like your normals are incorrect. For terrain normals I take the height sample x,y and compute the normal for that sample with:

float h0 = GetSample( x + 0, y - 1 );
float h1 = GetSample( x - 1, y + 0 );
float h2 = GetSample( x + 1, y + 0 );
float h3 = GetSample( x + 0, y + 1 );

Vector3 normal;

normal.x = h1 - h2;
normal.y = separation; // separation = distance between samples (I use 1.0f).
normal.z = h0 - h3;

normal.Normalize();

return normal;

If that doesn't help, perhaps posting your normal calculation code?

n!
Vexal
Vexal

Hey, thanks for the images. The lighting in the first one shows your problem much clearer for me.It looks like your normals are incorrect. For terrain normals I take the height sample x,y and compute the normal for that sample with:

float h0 = GetSample( x + 0, y - 1 );
float h1 = GetSample( x - 1, y + 0 );
float h2 = GetSample( x + 1, y + 0 );
float h3 = GetSample( x + 0, y + 1 );

Vector3 normal;

normal.x = h1 - h2;
normal.y = separation; // separation = distance between samples (I use 1.0f).
normal.z = h0 - h3;

normal.Normalize();

return normal;

If that doesn't help, perhaps posting your normal calculation code?

n!

Are you using y-up for your normals, but z-up for your sample locations in this response?

EDIT: Also, I think your y value for the normal should be 2 * the separation. According to this post, at least http://www.gamedev.net/topic/163625-fast-way-to-calculate-heightmap-normals/

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.