• 11
• 9
• 10
• 9
• 10
• ### Similar Content

• By stale
I'm continuing to learn more about terrain rendering, and so far I've managed to load in a heightmap and render it as a tessellated wireframe (following Frank Luna's DX11 book). However, I'm getting some really weird behavior where a large section of the wireframe is being rendered with a yellow color, even though my pixel shader is hard coded to output white.

The parts of the mesh that are discolored changes as well, as pictured below (mesh is being clipped by far plane).

Here is my pixel shader. As mentioned, I simply hard code it to output white:
float PS(DOUT pin) : SV_Target { return float4(1.0f, 1.0f, 1.0f, 1.0f); } I'm completely lost on what could be causing this, so any help in the right direction would be greatly appreciated. If I can help by providing more information please let me know.

• Hello,
i try to implement voxel cone tracing in my game engine.
At first step i try to emplement the easiest "poor mans" method
a.  my test scene "Sponza Atrium" is voxelized completetly in a static voxel grid 128^3 ( structured buffer contains albedo)
b. i dont care about "conservative rasterization" and dont use any sparse voxel access structure
c. every voxel does have the same color for every side ( top, bottom, front .. )
d.  one directional light injects light to the voxels ( another stuctured buffer )
I will try to say what i think is correct ( please correct me )
GI lighting a given vertecie  in a ideal method
A.  we would shoot many ( e.g. 1000 ) rays in the half hemisphere which is oriented according to the normal of that vertecie
B.  we would take into account every occluder ( which is very much work load) and sample the color from the hit point.
C. according to the angle between ray and the vertecie normal we would weigth ( cosin ) the color and sum up all samples and devide by the count of rays
Voxel GI lighting
In priciple we want to do the same thing with our voxel structure.
Even if we would know where the correct hit points of the vertecie are we would have the task to calculate the weighted sum of many voxels.
Saving time for weighted summing up of colors of each voxel
To save the time for weighted summing up of colors of each voxel we build bricks or clusters.
Every 8 neigbour voxels make a "cluster voxel" of level 1, ( this is done recursively for many levels ).
The color of a side of a "cluster voxel" is the average of the colors of the four containing voxels sides with the same orientation.

After having done this we can sample the far away parts just by sampling the coresponding "cluster voxel with the coresponding level" and get the summed up color.
Actually this process is done be mip mapping a texture that contains the colors of the voxels which places the color of the neighbouring voxels also near by in the texture.
Cone tracing, howto ??
Here my understanding is confus ?? How is the voxel structure efficiently traced.
I simply cannot understand how the occlusion problem is fastly solved so that we know which single voxel or "cluster voxel" of which level we have to sample.
Supposed,  i am in a dark room that is filled with many boxes of different kind of sizes an i have a pocket lamp e.g. with a pyramid formed light cone
- i would see some single voxels near or far
- i would also see many different kind of boxes "clustered voxels" of different sizes which are partly occluded
How do i make a weighted sum of this ligting area ??
e.g. if i want to sample a "clustered voxel level 4" i have to take into account how much per cent of the area of this "clustered voxel" is occluded.
Please be patient with me, i really try to understand but maybe i need some more explanation than others
best regards evelyn

• Hi guys, when I do picking followed by ray-plane intersection the results are all wrong. I am pretty sure my ray-plane intersection is correct so I'll just show the picking part. Please take a look:

// get projection_matrix DirectX::XMFLOAT4X4 mat; DirectX::XMStoreFloat4x4(&mat, projection_matrix); float2 v; v.x = (((2.0f * (float)mouse_x) / (float)screen_width) - 1.0f) / mat._11; v.y = -(((2.0f * (float)mouse_y) / (float)screen_height) - 1.0f) / mat._22; // get inverse of view_matrix DirectX::XMMATRIX inv_view = DirectX::XMMatrixInverse(nullptr, view_matrix); DirectX::XMStoreFloat4x4(&mat, inv_view); // create ray origin (camera position) float3 ray_origin; ray_origin.x = mat._41; ray_origin.y = mat._42; ray_origin.z = mat._43; // create ray direction float3 ray_dir; ray_dir.x = v.x * mat._11 + v.y * mat._21 + mat._31; ray_dir.y = v.x * mat._12 + v.y * mat._22 + mat._32; ray_dir.z = v.x * mat._13 + v.y * mat._23 + mat._33;
That should give me a ray origin and direction in world space but when I do the ray-plane intersection the results are all wrong.
If I click on the bottom half of the screen ray_dir.z becomes negative (more so as I click lower). I don't understand how that can be, shouldn't it always be pointing down the z-axis ?
I had this working in the past but I can't find my old code

• Hi,
I finally managed to get the DX11 emulating Vulkan device working but everything is flipped vertically now because Vulkan has a different clipping space. What are the best practices out there to keep these implementation consistent? I tried using a vertically flipped viewport, and while it works on Nvidia 1050, the Vulkan debug layer is throwing error messages that this is not supported in the spec so it might not work on others. There is also the possibility to flip the clip scpace position Y coordinate before writing out with vertex shader, but that requires changing and recompiling every shader. I could also bake it into the camera projection matrices, though I want to avoid that because then I need to track down for the whole engine where I upload matrices... Any chance of an easy extension or something? If not, I will probably go with changing the vertex shaders.

• Hello,
in my game engine i want to implement my own bone weight painting tool, so to say a virtual brush painting tool for a mesh.
I have already implemented my own "dual quaternion skinning" animation system with "morphs" (=blend shapes)  and "bone driven"  "corrective morphs" (= morph is dependent from a bending or twisting bone)
But now i have no idea which is the best method to implement a brush painting system.
Just some proposals
a.  i would build a kind of additional "vertecie structure", that can help me to find the surrounding (neighbours) vertecie indexes from a given "central vertecie" index
b.  the structure should also give information about the distance from the neighbour vertecsies to the given "central vertecie" index
c.  calculate the strength of the adding color to the "central vertecie" an the neighbour vertecies by a formula with linear or quadratic distance fall off
d.  the central vertecie would be detected as that vertecie that is hit by a orthogonal projection from my cursor (=brush) in world space an the mesh
but my problem is that there could be several  vertecies that can be hit simultaniously. e.g. i want to paint the inward side of the left leg. the right leg will also be hit.
I think the given problem is quite typical an there are standard approaches that i dont know.
Any help or tutorial are welcome
P.S. I am working with SharpDX, DirectX11

# DX11 Looking for an elegant solution for texture quality/resolution setting (solved)

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

## Recommended Posts

In the alpha of my driving game I'm currently offering two texture resolution settings: (very) low, which loads textures as 64x64 (excluding any GUI textures) and normal which load them as is (resolutions varying anything from  ~8x8 to 2048x2048).

I did some vehicle interior texturing this weekend and noticed then that this new texturing looks absolutely horrid on my laptop w/ low settings.

An elegant solution in my mind would be to give D3DX11_IMAGE_LOAD_INFO a flag to tell to NOT upscale any textures, which the documentation tells it will do if I were to define width and height bigger than the texture actually is. But I havent found such a flag. This is why currently I give only 0 or 64 for the width and height for the load info.

I do have some less elegant ideas which I wouldn't prefer (otherwise I guess I wouldn't have this problem this day).

I've tried searching the subject and saw some mipmap level related solutions, but seemed kind of a hassle and the solutions I saw weren't DX11 specific, and not sort of complete enough for me to understand. To be specific, I was left with an "understanding" that I would need to add new sampler(s) to the HLSL or something weird & messy like that, also the actual loading seemed like a mess too compared to what I'm doing now..

Such mess is lacking the elegancy I'm looking for here, but if it's the only way to go then sure..

##### Share on other sites

The simplest option is to hook up your texture quality setting to the "FirstMipLevel" parameter.

As long as you textures are saved with mip levels (i.e. they are in .dds files) then that will work well. Dropping one mip level will divide the size of the texture by 4, and dropping two mip levels will make it 16 times smaller. You probably won't need to drop more than that in order to support a wide range of hardware, because dropping two mip levels will take 4GB worth of textures and cut them down to be 256MB.

Also note that most of your textures should probably be stored in BC1 or BC3 format. That will make them 4-8 times smaller than uncompressed textures, and the visual quality will be almost as good.

##### Share on other sites

You could also read the dimensions of the texture and scale that based on texture quality when loading?

D3DX11_IMAGE_INFO srcinfo;
hr = D3DX11GetImageInfoFromFile(filename, NULL, &srcinfo, NULL);



##### Share on other sites

Thanks for the suggestions, both very simple & straightforward!

But, I tried setting FirstMipLevel to 2 (and 3), but didn't notice any difference in appearance or video memory usage.. Does it work only for DDS?

I stopped using DDS files at some point because of their horrible file size (they were uncompressed though I believe) and the game has lots of textures..

D3DX11GetImageInfoFromFile seems to work fairly nice however, operation takes only 1-3ms so I think I'll go with that for now.