• Advertisement
Sign in to follow this  

DX11 volume rendering

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

If you intended to correct an error in the post then please contact us.

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 this post


Link to post
Share on other sites
Advertisement

This page talks about it in terms of OpenGL. http://prideout.net/blog/?p=64

 

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 this post


Link to post
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 this post


Link to post
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.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By isu diss
      I'm trying to duplicate vertices using std::map to be used in a vertex buffer. I don't get the correct index buffer(myInds) or vertex buffer(myVerts). I can get the index array from FBX but it differs from what I get in the following std::map code. Any help is much appreciated.
      struct FBXVTX { XMFLOAT3 Position; XMFLOAT2 TextureCoord; XMFLOAT3 Normal; }; std::map< FBXVTX, int > myVertsMap; std::vector<FBXVTX> myVerts; std::vector<int> myInds; HRESULT FBXLoader::Open(HWND hWnd, char* Filename, bool UsePositionOnly) { HRESULT hr = S_OK; if (FBXM) { FBXIOS = FbxIOSettings::Create(FBXM, IOSROOT); FBXM->SetIOSettings(FBXIOS); FBXI = FbxImporter::Create(FBXM, ""); if (!(FBXI->Initialize(Filename, -1, FBXIOS))) { hr = E_FAIL; MessageBox(hWnd, (wchar_t*)FBXI->GetStatus().GetErrorString(), TEXT("ALM"), MB_OK); } FBXS = FbxScene::Create(FBXM, "REALMS"); if (!FBXS) { hr = E_FAIL; MessageBox(hWnd, TEXT("Failed to create the scene"), TEXT("ALM"), MB_OK); } if (!(FBXI->Import(FBXS))) { hr = E_FAIL; MessageBox(hWnd, TEXT("Failed to import fbx file content into the scene"), TEXT("ALM"), MB_OK); } FbxAxisSystem OurAxisSystem = FbxAxisSystem::DirectX; FbxAxisSystem SceneAxisSystem = FBXS->GetGlobalSettings().GetAxisSystem(); if(SceneAxisSystem != OurAxisSystem) { FbxAxisSystem::DirectX.ConvertScene(FBXS); } FbxSystemUnit SceneSystemUnit = FBXS->GetGlobalSettings().GetSystemUnit(); if( SceneSystemUnit.GetScaleFactor() != 1.0 ) { FbxSystemUnit::cm.ConvertScene( FBXS ); } if (FBXI) FBXI->Destroy(); FbxNode* MainNode = FBXS->GetRootNode(); int NumKids = MainNode->GetChildCount(); FbxNode* ChildNode = NULL; for (int i=0; i<NumKids; i++) { ChildNode = MainNode->GetChild(i); FbxNodeAttribute* NodeAttribute = ChildNode->GetNodeAttribute(); if (NodeAttribute->GetAttributeType() == FbxNodeAttribute::eMesh) { FbxMesh* Mesh = ChildNode->GetMesh(); if (UsePositionOnly) { NumVertices = Mesh->GetControlPointsCount();//number of vertices MyV = new XMFLOAT3[NumVertices]; for (DWORD j = 0; j < NumVertices; j++) { FbxVector4 Vertex = Mesh->GetControlPointAt(j);//Gets the control point at the specified index. MyV[j] = XMFLOAT3((float)Vertex.mData[0], (float)Vertex.mData[1], (float)Vertex.mData[2]); } NumIndices = Mesh->GetPolygonVertexCount();//number of indices MyI = (DWORD*)Mesh->GetPolygonVertices();//index array } else { FbxLayerElementArrayTemplate<FbxVector2>* uvVertices = NULL; Mesh->GetTextureUV(&uvVertices); int idx = 0; for (int i = 0; i < Mesh->GetPolygonCount(); i++)//polygon(=mostly triangle) count { for (int j = 0; j < Mesh->GetPolygonSize(i); j++)//retrieves number of vertices in a polygon { FBXVTX myVert; int p_index = 3*i+j; int t_index = Mesh->GetTextureUVIndex(i, j); FbxVector4 Vertex = Mesh->GetControlPointAt(p_index);//Gets the control point at the specified index. myVert.Position = XMFLOAT3((float)Vertex.mData[0], (float)Vertex.mData[1], (float)Vertex.mData[2]); FbxVector4 Normal; Mesh->GetPolygonVertexNormal(i, j, Normal); myVert.Normal = XMFLOAT3((float)Normal.mData[0], (float)Normal.mData[1], (float)Normal.mData[2]); FbxVector2 uv = uvVertices->GetAt(t_index); myVert.TextureCoord = XMFLOAT2((float)uv.mData[0], (float)uv.mData[1]); if ( myVertsMap.find( myVert ) != myVertsMap.end() ) myInds.push_back( myVertsMap[ myVert ]); else { myVertsMap.insert( std::pair<FBXVTX, int> (myVert, idx ) ); myVerts.push_back(myVert); myInds.push_back(idx); idx++; } } } } } } } else { hr = E_FAIL; MessageBox(hWnd, TEXT("Failed to create the FBX Manager"), TEXT("ALM"), MB_OK); } return hr; } bool operator < ( const FBXVTX &lValue, const FBXVTX &rValue) { if (lValue.Position.x != rValue.Position.x) return(lValue.Position.x < rValue.Position.x); if (lValue.Position.y != rValue.Position.y) return(lValue.Position.y < rValue.Position.y); if (lValue.Position.z != rValue.Position.z) return(lValue.Position.z < rValue.Position.z); if (lValue.TextureCoord.x != rValue.TextureCoord.x) return(lValue.TextureCoord.x < rValue.TextureCoord.x); if (lValue.TextureCoord.y != rValue.TextureCoord.y) return(lValue.TextureCoord.y < rValue.TextureCoord.y); if (lValue.Normal.x != rValue.Normal.x) return(lValue.Normal.x < rValue.Normal.x); if (lValue.Normal.y != rValue.Normal.y) return(lValue.Normal.y < rValue.Normal.y); return(lValue.Normal.z < rValue.Normal.z); }  
    • By Karol Plewa
      Hi, 
       
      I am working on a project where I'm trying to use Forward Plus Rendering on point lights. I have a simple reflective scene with many point lights moving around it. I am using effects file (.fx) to keep my shaders in one place. I am having a problem with Compute Shader code. I cannot get it to work properly and calculate the tiles and lighting properly. 
       
      Is there anyone that is wishing to help me set up my compute shader?
      Thank you in advance for any replies and interest!
    • By turanszkij
      Hi, right now building my engine in visual studio involves a shader compiling step to build hlsl 5.0 shaders. I have a separate project which only includes shader sources and the compiler is the visual studio integrated fxc compiler. I like this method because on any PC that has visual studio installed, I can just download the solution from GitHub and everything just builds without additional dependencies and using the latest version of the compiler. I also like it because the shaders are included in the solution explorer and easy to browse, and double-click to open (opening files can be really a pain in the ass in visual studio run in admin mode). Also it's nice that VS displays the build output/errors in the output window.
      But now I have the HLSL 6 compiler and want to build hlsl 6 shaders as well (and as I understand I can also compile vulkan compatible shaders with it later). Any idea how to do this nicely? I want only a single project containing shader sources, like it is now, but build them for different targets. I guess adding different building projects would be the way to go that reference the shader source project? But how would they differentiate from shader type of the sources (eg. pixel shader, compute shader,etc.)? Now the shader building project contains for each shader the shader type, how can other building projects reference that?
      Anyone with some experience in this?
    • By osiris_dev
      Hello!
      Have a problem with reflection shader for D3D11:
      1>engine_render_d3d11_system.obj : error LNK2001: unresolved external symbol IID_ID3D11ShaderReflection
      I tried to add this:
      #include <D3D11Shader.h>
      #include <D3Dcompiler.h>
      #include <D3DCompiler.inl>
      #pragma comment(lib, "D3DCompiler.lib")
      //#pragma comment(lib, "D3DCompiler_47.lib")
      As MSDN tells me but still no fortune. I think lot of people did that already, what I missing?
      I also find this article http://mattfife.com/?p=470
      where recommend to use SDK headers and libs before Wind SDK, but I am not using DirectX SDK for this project at all, should I?
    • By trojanfoe
      Hi there, this is my first post in what looks to be a very interesting forum.
      I am using DirectXTK to put together my 2D game engine but would like to use the GPU depth buffer in order to avoid sorting back-to-front on the CPU and I think I also want to use GPU instancing, so can I do that with SpriteBatch or am I looking at implementing my own sprite rendering?
      Thanks in advance!
  • Advertisement