What I'm up to?

I would like to render some CT/MRI data. The data is represented as a 3d array with float values. (Or a sequence of 2d images)

My scheme

As the blender manual describes, procedual textures have their 3D structure. With the trick in the stack exchange QA ( Controlling volume density), this 3D structure can be visualised.

Thus, all I need to do is to convert the 3d array to a 3D texture. Please help me achieve this either by node or scripting(preferred).



The picture below shows that the single image version is rather simple.


The following is the .blend file for the above screen shot. (Although, you might not have the image texture with it.)

The tasks above can be achieved in Blender Internal (see comments). I am now eager to know a Cycles/EEVEE solution

  • $\begingroup$ If you are happy with single image, why not to load all scans as image sequence and render that way? Just rename images in specific app to get names like scan_001, scan_002 and so on. $\endgroup$ – Serge L May 18 '18 at 11:18
  • $\begingroup$ @SergeL Thanks for the reply. One of the advantage of rendering them with one cube is that I can keep the geometry-size small. Although your proposal may be one of the possible solutions, I don't want to see a cube on a cube on a cube ... on a cube, until it piles up to 1000. $\endgroup$ – Allosteric May 18 '18 at 12:31
  • $\begingroup$ found this. docs.blender.org/manual/en/dev/render/blender_render/textures/… (I think I can solve this myself but still open for any kind of answer/advice) $\endgroup$ – Allosteric May 18 '18 at 12:59
  • $\begingroup$ The link above is well explained in the following video. youtube.com/watch?v=7PSPiUrrXsg. However, this is not a promising solution since this uses Blender Internal Renderer. Any Cycles/EEVEE solution is more preferable. $\endgroup$ – Allosteric May 18 '18 at 13:30

This is currently not available for the Cycles/EEVEE. However, one of the GSoC 2018 challenge aims to implement this. https://wiki.blender.org/index.php/User:Geraldine/GSoC_2018/Proposal

I will update this post once it is available.

  • $\begingroup$ Any updates yet? $\endgroup$ – Leander Mar 23 '19 at 15:16
  • $\begingroup$ Not quite. The branch for this is at developer.blender.org/diffusion/B/history/… but I cannot judge how this project went or how this would influence the blender source. Speaking of OpenVDB, the Sculpt team seems to be interested in using OpenVDB for re-meshing but that's yet another area so ... $\endgroup$ – Allosteric Mar 24 '19 at 9:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.