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

Recommended Posts

Back again with a new problem, I'm having issues rendering a shadow map and then using it in another shader.

I create a 256x256 texture here with R32_Float as the format:

            Texture2D shadowBuffer = new Texture2D(device, new Texture2DDescription()
{
ArraySize = 1,
CpuAccessFlags = CpuAccessFlags.None,
Format = Format.R32_Float,
Height = 256,
Width = 256,
MipLevels = 1,
OptionFlags = ResourceOptionFlags.None,
SampleDescription = new SampleDescription(1, 0),
Usage = ResourceUsage.Default
});
{
Format = Format.R32_Float,
Dimension = RenderTargetViewDimension.Texture2D,
MipSlice = 0,
});
{
Format = Format.R32_Float,
MostDetailedMip = 0,
MipLevels = 1,
});

I then render depth values to this texture and use it in another shader.  My problem is that when the values are sampled from the texture, they are clamped to 0-1.

Any help is appreciated.

EDIT: It has occured to me that the problem may lie in light matrices.  I create a orthographic projection and view matrix to act as a view from the sun:

        private static void SetUpSun()
{
SunProj = Matrix.OrthoLH(512, 512, 256, 1024);
}

{
Vector3 SunPos = new Vector3((float)Math.Sin(wt / 1f) * -512, (float)Math.Cos(wt / 1f) * -512, 0) + Camera.Position;
SunView = Matrix.LookAtLH(SunPos, Camera.Position, Vector3.UnitY);
}
Edited by Matthew Meeks

Share on other sites

Typically the depth values stored in the shadow map are in range 0..1.

I don't understand from your post what is the actual problem.

Best regards!

Share on other sites

Yeah sorry wrote that with a migraine and tried to do it as fast as possible, it didn't work.  I've changed some things around and got closer to what I wanted, getting values in-between 0 and 1, except now the farther objects are 0 and the closer are 1.  My understanding is that farther objects return depths closer to 1.

In the vs:

float4 worldPosition = mul(Output.position, World);
float4 viewPosition = mul(worldPosition, View);
Output.position = mul(viewPosition, Projection);

In the ps:

return input.position.z / input.position.w;

Really simple yet I still can't figure out why.

And just in case the problem lies in the matrices:

View:

View = Matrix.LookAtLH(Position, cameraFinalTarget, up);

Projection:

Projection = Matrix.PerspectiveFovLH((float)Math.PI / 4, (float)Width / (float)Height, 0.01f, 800f);

Thanks for the help and apologies for the vagueness of the original post.

Edited by Matthew Meeks

Share on other sites

Yeah the z-values should be in between 0..1 where 0 is closer and 1 is further.

Why are you dividing your z-value by w? Isn't the division by w done automatically?

If you are doing basic shadow mapping, you may even disable your pixel shader if you are outputting to a depth-stencil buffer.

Best regards!

Share on other sites

I have tried both with and without dividing by w with the same result.  I had placed the division of w to ensure that w was always one as it should have been.  I am not outputting to a depth-stencil buffer but rather a Texture2D render target.  Not sure if this is the preferred method but i choose this because I eventually want to do more with the shadow map (different levels of light from the same source for semitransparent objects).

EDIT: I will try binding a depth buffer and attempt that way.

Thanks for the help!

Edited by Matthew Meeks

Share on other sites

Nevermind passed the wrong description.

Edited by Matthew Meeks

• 10
• 11
• 9
• 16
• 18
• 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