# DX11 Lighting problem in deferred rendering

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

## Recommended Posts

Hi !

I have a lighting problem, the scene is lit and a part or it is unlit, I don't understand why. If I amplify light intensity for example, lit parts of the scene are more lit but the part which is in shadow, is better lighted. There is no shadow mapping implemented in this program, and I even not manage to guess what kind of problem it could be.

This is deferred rendering, so in the image below, the lighting is applied on a texture pixel by pixel, which is applied on a quad.

It doesn't seem to be the number of lights (just 1 present in the scene), I tried with more lights and it is the same problem.

[attachment=22703:bugged DX11.png]

##### Share on other sites

Hi theScore,

can we see how you reconstruct the position, normal, etc...? ( I think this is the fault )

in what space are they stored in? View, model, perspective?

So to help you further, it would be awesome if we could see this:

• How you store the GBUFFER
• How you use/extract from the GBUFFER
• How you calculate your lighting with the extracted values from the GBUFFER

EDIT: Try to just render the reconstructed normals, positions to see if it looks right. Or use a modern graphics debugger to check the render targets.

Cheers!

-MIGI0027

Edited by Migi0027

##### Share on other sites

Hi !

Positions and normals are stored in 2 vectors of 4 floats of 16 bit for each one.

Threre are stored in view space.

Normals are stored like this :

[attachment=22704:normals texture.png]

And positions :

[attachment=22705:positions texture.png]

##### Share on other sites

The positions look off, can we see how you store them?

##### Share on other sites

Another problem may be here (vertex shader from Gbuffer pass) :

        matrix <float, 4, 4> projView = mul(proj, view) ;
matrix <float, 4, 4> projViewWorld = mul(projView, world) ;

output.RTposition = mul( input.position, view );
output.color = input.color ;
output.RTnormal = mul( input.normal, view);

output.texCoord = input.texCoord ;

output.finalPos= mul( projViewWorld, input.position );


The world matrix is an identity matrix from CPU code, it is for that, that I only multiply positions and normals by the view matrix.

But I am doing :

positions * viewMatrix

normals * viewMatrix

And :

ProjViewWorldMatrix * positions ; //so, not in the same order...

If I change the order in the shader it doen't work (black screen)

##### Share on other sites

Structs in VS :

struct vsIn
{
half4 position : POSITION ;
half4 normal   : NORMAL ;
half4 texCoord : TEXCOORD0 ;
half4 color    : COLOR0 ;
};

struct vsOut
{
half4 finalPos :SV_POSITION ;
half4 color : COLOR0 ;
half4 RTposition : POSITION1 ;
half4 RTnormal   : NORMAL   ;
half4 texCoord : TEXCOORD0 ;

};



And structs in pixel shader :

struct psIn
{
half4 finalPos		: SV_POSITION ;
half4 color			: COLOR0 ;
half4 RTposition	: POSITION1 ;
half4 RTnormal		: NORMAL ;
half4 texCoord		: TEXCOORD0 ;

};


##### Share on other sites

How are the matrices structued? Row Major? Column Major?

Just to try, transpose the view matrix thats used on the normals and positions, and do as you did before: viewMatrix * position

Edited by Migi0027

##### Share on other sites

I use XMMatrixLookAtLH,it is in row major.

I did that and I have the same result than in my first post : (I am not sure that it is what you expected ?)

	matrix <float, 4, 4> projView = mul(proj, view) ;
matrix <float, 4, 4> projViewWorld = mul(projView, world) ;

matrix <float, 4, 4> transposedView = transpose(view);

output.RTposition = mul( transposedView, input.position );
output.color = input.color ;
output.RTnormal = mul( transposedView, input.normal);

output.texCoord = input.texCoord ;

output.finalPos= mul( projViewWorld, input.position );

return output ;


##### Share on other sites

Yeah that's what I meant. I've never used XMMatrix, though I should transition to it.

Forget the transposing. When you multiply the view matrix with the position, remember that its a point, so you'd need to write mul(view, float4(input.position.xyz, 1)); But for the normal, leave the w component 0, or instead multiply the normals by the 3x3 view matrix.

##### Share on other sites

Finally, I did that and it works :

	output.RTposition = mul( input.position, transposedView );
output.color = input.color ;
output.RTnormal = mul( input.normal, view );


And I don't understand why positions can't be multipied by a row major matrix... Do you know it ?

##### Share on other sites

Awesome!

Im afraid my knowledge of matrices is very limited, maybe someone with a better overview of the concept can help you. I wouldnt want to pass wrong information to you.

-MIGI0027

##### Share on other sites

Ok   thanks for your help, you put me on the line.

if somebody knows for the matrices !...

##### Share on other sites

Without going into theory/details: when it comes to matrices A * B != B * A. If your matrix is different (row vs column) then multiplication order is reversed, you can also reverse it by transposing all matrices.

##### Share on other sites

Ok but here I perform the multiplication in the same order, with the same matrix but transposed once and the other time not transposed, so I don't understand why it works here and with the same processing not ?

##### Share on other sites
// these two are equivalent
output.RTposition = mul( input.position, transposedView ); // transposing reverses order
output.RTposition = mul( view, input.position ); // judging by your projViewWorld matrix this is correct order

// if those lines are correct, then this one is wrong order
output.RTnormal = mul( input.normal, view );

• 10
• 11
• 9
• 16
• 19
• ### Similar Content

• I wanted to see how others are currently handling descriptor heap updates and management.
I've read a few articles and there tends to be three major strategies :
1 ) You split up descriptor heaps per shader stage ( i.e one for vertex shader , pixel , hull, etc)
2) You have one descriptor heap for an entire pipeline
3) You split up descriptor heaps for update each update frequency (i.e EResourceSet_PerInstance , EResourceSet_PerPass , EResourceSet_PerMaterial, etc)
The benefits of the first two approaches is that it makes it easier to port current code, and descriptor / resource descriptor management and updating tends to be easier to manage, but it seems to be not as efficient.
The benefits of the third approach seems to be that it's the most efficient because you only manage and update objects when they change.

• hi,
until now i use typical vertexshader approach for skinning with a Constantbuffer containing the transform matrix for the bones and an the vertexbuffer containing bone index and bone weight.
Now i have implemented realtime environment  probe cubemaping so i have to render my scene from many point of views and the time for skinning takes too long because it is recalculated for every side of the cubemap.
For Info i am working on Win7 an therefore use one Shadermodel 5.0 not 5.x that have more options, or is there a way to use 5.x in Win 7
My Graphic Card is Directx 12 compatible NVidia GTX 960
the member turanszkij has posted a good for me understandable compute shader. ( for Info: in his engine he uses an optimized version of it )
Now my questions
is it possible to feed the compute shader with my orignial vertexbuffer or do i have to copy it in several ByteAdressBuffers as implemented in the following code ?
the same question is about the constant buffer of the matrixes
my more urgent question is how do i feed my normal pipeline with the result of the compute Shader which are 2 RWByteAddressBuffers that contain position an normal
for example i could use 2 vertexbuffer bindings
1 containing only the uv coordinates
2.containing position and normal
How do i copy from the RWByteAddressBuffers to the vertexbuffer ?

(Code from turanszkij )
Here is my shader implementation for skinning a mesh in a compute shader:

• Hi, can someone please explain why this is giving an assertion EyePosition!=0 exception?

It looks like DirectX doesnt want the 2nd parameter to be a zero vector in the assertion, but I passed in a zero vector with this exact same code in another program and it ran just fine. (Here is the version of the code that worked - note XMLoadFloat3(&m_lookAt) parameter value is (0,0,0) at runtime - I debugged it - but it throws no exceptions.
and here is the repo with the alternative version of the code that is working with a value of (0,0,0) for the second parameter.

• 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

• 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.

Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.