is it posiible to apply Prism rendering on the rendered volume in "volume rendering module " ?
like applying a sphere carving on the render
i thought i would be able to save the rendering in prism in volume property like into rendering module and use multi volume ray casting .
SlicerPrismRendering is not really integrated with the Volume Rendering module, it’s more of an alternative way to define the rendering setup.
I’ve found that Volume rendering module and PRISM works quite nicely together on the same nodes (they both edit the same Volume Rendering and Volume Property nodes). PRISM provides a convenient GUI to specify custom shaders and their parameters, while Volume Rendering module allows editing transfer functions, lighting, and a few other parameters.
There seems to be a limitation in PRISM module GUI that prevents recognizing volume rendering nodes created by Volume Rendering module, so for now you need to create the volume rendering nodes in PRISM (by clicking the “Volume rendering” checkbox). It should be easy to fix this, if you send a bug report to the PRISM issue tracker then eventually they will take care of this (or you can give it a try yourself).
I don’t think PRISM is prepared to work with the relatively new multivolume renderer, so this may be another feature request for PRISM (or you can dive in and implement it).
i stumbled on the " volume rendering special effects" module and it does recognize node from volume rendering module . it has a wedge and sphere carving.
however the prism rendering is better and has more functionality .
ill try to submit the issue on GitHub
well , thats a downer . i don’t think it makes sense to be in slicer and not be able to interact with the core volume rendering module
This is not the case. Just for now (until the PRISM module GUI is fixed), you need to create the volume rendering nodes in PRISM. You can then use Volume Rendering module to edit those settings.
This module is an earlier version of PRISM. PRISM should work the same way, there is just that small bug in its GUI it that it expects a vtkMRMLShaderPropertyNode to be associated with the volume rendering node and the Volume Rendering module does not create such a node; but PRISM could easily create it instead of just throwing an error message.
i failed to see that before , i just tried it now and it works . however . i still would love to do to the other way around . use volume rendering module then prism . will be waiting for the fix
is there any volume rendering extension / module offering more possibilities ?
just wondering since im getting such amazing results learning using these two modules
Yes, there are many possibilities and the programming infrastructure is very powerful. it’s taken many years of development by uniquely talented people to turn these into the usable GUIs that exist today, but much more is possible if someone is able to invest the time and effort. This could be accomplished through sponsorship, if someone wants to pay to have it developed, or through mentorship, if a student or volunteer wants to dive in.
