# DX11 volume rendering

## Recommended Posts

Hi,

I have a medical volume data and I would like to learn how to write a HLSL shader to do ray-cast rendering, volume slicing etc.

Can anybody provide me some links for this kind of examples?

I use DX11.

Thanks a lot.

YL

##### Share on other sites

You can surely spend 30 minutes figuring out how to translate it, I think there are even HLSL to GLSL (and vice-versa) converters out there as they are really just exposing the underlying hardware functions.

The whole point is that you load your volume into a 3D texture and then render a cube/rectangular prism where each vertex is given its corresponding texture coordinate for the volume. Then, in a fragment/pixel shader you receive the interpolated texture coordinate for the fragments of the surface of the geometry and that serves as the origin for each raycast insofar as the math is concerned. What you need to do next is figure the vector through texture space that represents the direction the ray much march through the texture along the line that travels from the camera through the volume's geometry. In some instances this is accomplished via a complicated manner where both the front and back faces of the volume geometry are rendered to generate the starting and ending points for each fragment's ray through the texture. I just use the modelview matrix to directly calculate a perfectly acceptable ray vector, which is just the normalized vector between the viewpoint and the fragment. The math is a little tricky to visualize, but if you think about it it's just one step beyond multiplying your modelview matrix against the vertex position, and then multiply that against your modelview matrix again to orient it in worldspace.

In my vertex shader it's as simple as multiplying the modelview matrix with the vertex position to get the final render position for the vertex, and then multiply that against the modelview matrix to effectively perform an inverse matrix transform. Normalize that and you have the vector.

I made a really simple GL program that does this exactly a while ago. I'll go see if I can dig that up. Even though it's in OpenGL/GLSL I'm sure it won't be hard to port to HLSL.

##### Share on other sites

I found my old OpenGL project that I made to test out raymarching a 3D texture. It just generates the texture procedurally using sine waves. You can run it if you trust it, but all the code and shaders are there: https://dl.dropboxusercontent.com/u/62846912/FILE/bitphoria_020513.zip

##### Share on other sites

I was hired to do this in 2005 with CT data. A cheap easy way is to load the volume data into a 3D/volume texture, then draw a series of camera-aligned quads (billboards) with alpha blending and sample the volume texture from your world vertex coords. This is nice because it's very quick and easy to implement and intuitive. If you're feeling clever, you can simply raytrace the data in the shader by drawing rays and subdividing, which is a simple extension once you have the aligned quads. The math is pretty similar to any shader raytrace, parallax mapping might be a good reference for how to do that in general. Computing rays from the camera is a simple unproject operation - calculate clip space XY position for the fragment, multiply using two different Z values by inverse viewproj and you get a ray. Or you can compute the frustum corners and interpolate if you prefer that approach.

Edited by Promit

##### Share on other sites

I was hired to do this in 2005 with CT data. A cheap easy way is to load the volume data into a 3D/volume texture, then draw a series of camera-aligned quads (billboards) with alpha blending and sample the volume texture from your world vertex coords. This is nice because it's very quick and easy to implement and intuitive. If you're feeling clever, you can simply raytrace the data in the shader by drawing rays and subdividing, which is a simple extension once you have the aligned quads. The math is pretty similar to any shader raytrace, parallax mapping might be a good reference for how to do that in general. Computing rays from the camera is a simple unproject operation - calculate clip space XY position for the fragment, multiply using two different Z values by inverse viewproj and you get a ray. Or you can compute the frustum corners and interpolate if you prefer that approach.

This was something I did as well before but without any vertex/fragment shaders, just using fixed-function OpenGL. I just drew a static set of quads on the screen with an orthographic projection. They don't need to actually be floating in space. Then for each one I generated texture coordinates based on the camera's position, orientation, and FOV, for each of the quads, and just let it fill the screen with its slice of the volume 3D texture. This works a lot better if you want to actually be inside of the volume, whereas the other method that raymarches from the outer surface of the bounding volume requires that the camera is external to the volume data.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
628370
• Total Posts
2982296
• ### Similar Content

• By joeblack
Hi,
im reading about specular aliasing because of mip maps, as far as i understood it, you need to compute fetched normal lenght and detect now its changed from unit length. I’m currently using BC5 normal maps, so i reconstruct z in shader and therefore my normals are normalized. Can i still somehow use antialiasing or its not needed? Thanks.
• By 51mon
I want to change the sampling behaviour to SampleLevel(coord, ddx(coord.y).xx, ddy(coord.y).xx). I was just wondering if it's possible without explicit shader code, e.g. with some flags or so?

• Hello,
I want to improve the performance of my game (engine) and some of your helped me to make a GPU Profiler. After creating the GPU Profiler, I started to measure the time my GPU needs per frame. I refined my GPU time measurements to find my bottleneck.
Searching the bottleneck
Rendering a small scene in an Idle state takes around 15.38 ms per frame. 13.54 ms (88.04%) are spent while rendering the scene, 1.57 ms (10.22%) are spent during the SwapChain.Present call (no VSync!) and the rest is spent on other tasks like rendering the UI. I further investigated the scene rendering, since it takes über 88% of my GPU frame rendering time.
When rendering my scene, most of the time (80.97%) is spent rendering my models. The rest is spent to render the background/skybox, updating animation data, updating pixel shader constant buffer, etc. It wasn't really suprising that most of the time is spent for my models, so I further refined my measurements to find the actual bottleneck.
In my example scene, I have five animated NPCs. When rendering these NPCs, most actions are almost for free. Setting the proper shaders in the input layout (0.11%), updating vertex shader constant buffers (0.32%), setting textures (0.24%) and setting vertex and index buffers (0.28%). However, the rest of the GPU time (99.05% !!) is spent in two function calls: DrawIndexed and DrawIndexedInstance.
I searched this forum and the web for other articles and threads about these functions, but I haven't found a lot of useful information. I use SharpDX and .NET Framework 4.5 to develop my game (engine). The developer of SharpDX said, that "The method DrawIndexed in SharpDX is a direct call to DirectX" (Source). DirectX 11 is widely used and SharpDX is "only" a wrapper for DirectX functions, I assume the problem is in my code.
How I render my scene
When rendering my scene, I render one model after another. Each model has one or more parts and one or more positions. For example, a human model has parts like head, hands, legs, torso, etc. and may be placed in different locations (on the couch, on a street, ...). For static elements like furniture, houses, etc. I use instancing, because the positions never change at run-time. Dynamic models like humans and monster don't use instancing, because positions change over time.
When rendering a model, I use this work-flow:
Set vertex and pixel shaders, if they need to be updated (e.g. PBR shaders, simple shader, depth info shaders, ...) Set animation data as constant buffer in the vertex shader, if the model is animated Set generic vertex shader constant buffer (world matrix, etc.) Render all parts of the model. For each part: Set diffuse, normal, specular and emissive texture shader views Set vertex buffer Set index buffer Call DrawIndexedInstanced for instanced models and DrawIndexed models What's the problem
After my GPU profiling, I know that over 99% of the rendering time for a single model is spent in the DrawIndexedInstanced and DrawIndexed function calls. But why do they take so long? Do I have to try to optimize my vertex or pixel shaders? I do not use other types of shaders at the moment. "Le Comte du Merde-fou" suggested in this post to merge regions of vertices to larger vertex buffers to reduce the number of Draw calls. While this makes sense to me, it does not explain why rendering my five (!) animated models takes that much GPU time. To make sure I don't analyse something I wrong, I made sure to not use the D3D11_CREATE_DEVICE_DEBUG flag and to run as Release version in Visual Studio as suggested by Hodgman in this forum thread.
My engine does its job. Multi-texturing, animation, soft shadowing, instancing, etc. are all implemented, but I need to reduce the GPU load for performance reasons. Each frame takes less than 3ms CPU time by the way. So the problem is on the GPU side, I believe.

• I was wondering if someone could explain this to me
I'm working on using the windows WIC apis to load in textures for DirectX 11. I see that sometimes the WIC Pixel Formats do not directly match a DXGI Format that is used in DirectX. I see that in cases like this the original WIC Pixel Format is converted into a WIC Pixel Format that does directly match a DXGI Format. And doing this conversion is easy, but I do not understand the reason behind 2 of the WIC Pixel Formats that are converted based on Microsoft's guide
I was wondering if someone could tell me why Microsoft's guide on this topic says that GUID_WICPixelFormat40bppCMYKAlpha should be converted into GUID_WICPixelFormat64bppRGBA and why GUID_WICPixelFormat80bppCMYKAlpha should be converted into GUID_WICPixelFormat64bppRGBA
In one case I would think that:
GUID_WICPixelFormat40bppCMYKAlpha would convert to GUID_WICPixelFormat32bppRGBA and that GUID_WICPixelFormat80bppCMYKAlpha would convert to GUID_WICPixelFormat64bppRGBA, because the black channel (k) values would get readded / "swallowed" into into the CMY channels
In the second case I would think that:
GUID_WICPixelFormat40bppCMYKAlpha would convert to GUID_WICPixelFormat64bppRGBA and that GUID_WICPixelFormat80bppCMYKAlpha would convert to GUID_WICPixelFormat128bppRGBA, because the black channel (k) bits would get redistributed amongst the remaining 4 channels (CYMA) and those "new bits" added to those channels would fit in the GUID_WICPixelFormat64bppRGBA and GUID_WICPixelFormat128bppRGBA formats. But also seeing as there is no GUID_WICPixelFormat128bppRGBA format this case is kind of null and void
I basically do not understand why Microsoft says GUID_WICPixelFormat40bppCMYKAlpha and GUID_WICPixelFormat80bppCMYKAlpha should convert to GUID_WICPixelFormat64bppRGBA in the end

• Hi, New here.
I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc....
I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn?
How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want?
Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn.
So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started.
Thanks,
Dejay Hextrix

• 10
• 9
• 13
• 24
• 11