<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Thanks, Aashish, for confirming it and
providing a workaround. Hope my post + other related posts would
bump it up a bit in the priority list. <br>
<br>
Best,<br>
Weiguang<br>
<br>
On 29/10/2015 12:14 PM, Aashish Chaudhary wrote:<br>
</div>
<blockquote
cite="mid:CAEw35Z8dO35AH6dKF1ii3hT3FAiuOvwDjzWO=9nRE_oBbPxzSw@mail.gmail.com"
type="cite">
<div dir="ltr"><span style="font-size:16px">Hi Weiguang, </span><br>
<div><span style="font-size:16px"><br>
</span></div>
<div><span style="font-size:16px">Yes, a true multi volume
rendering is not supported in current GPU mappers. This is a
interesting task and we talked about implementing it but
didn't hit high in our priority list. I think there could be
some interesting questions / answer related to this on
blending and mixing. </span><span style="font-size:16px">One
thing you could do (if possible) is that you can combine two
volumes into one with two components (assuming that each has
one) if you need something soon. Also, I believe the </span><span
style="font-size:16px">texture mapping mapper works because
it crates these polygonal slices but I would imaging that
even it would not do the right thing completely (it may look
right though) in all circumstances since its not going to
sort slices between two volumes. </span></div>
<div><span style="font-size:16px"><br>
</span></div>
<div><span style="font-size:16px">- Aashish </span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 29, 2015 at 11:59 AM,
Weiguang guan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:guanw@rhpcs.mcmaster.ca" target="_blank">guanw@rhpcs.mcmaster.ca</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">There were
a few posts in the past about this topic. The conclusion
seemed to be that VTK didn't support multi-volume rendering
in terms of proper visibility sorting/blending. I'm not sure
it is still true.<br>
<br>
I've done a test where two partially overlapped volumes are
used. I've found that only the texture mapping mapper can
render them correctly. All the other mappers (GPU based or
ray casting) always have one volume occlude the other one no
matter what direction the camera is viewing.<br>
<br>
Is vtkImageOcclusionSpectrum designed for handling multiple
volume rendering? Any comments will be appreciated. Thanks.<br>
<br>
Best,<br>
Weiguang<br>
_______________________________________________<br>
Powered by <a moz-do-not-send="true"
href="http://www.kitware.com" rel="noreferrer"
target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a
moz-do-not-send="true"
href="http://www.kitware.com/opensource/opensource.html"
rel="noreferrer" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the VTK FAQ at: <a
moz-do-not-send="true"
href="http://www.vtk.org/Wiki/VTK_FAQ" rel="noreferrer"
target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
<br>
Search the list archives at: <a moz-do-not-send="true"
href="http://markmail.org/search/?q=vtkusers"
rel="noreferrer" target="_blank">http://markmail.org/search/?q=vtkusers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a moz-do-not-send="true"
href="http://public.kitware.com/mailman/listinfo/vtkusers"
rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/vtkusers</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr"><font face="trebuchet ms, sans-serif"><i>|
Aashish Chaudhary <br>
| Technical Leader <br>
| Kitware Inc. <br>
</i></font>
<div><i><font face="trebuchet ms, sans-serif">| </font><a
moz-do-not-send="true"
href="http://www.kitware.com/company/team/chaudhary.html"
target="_blank">http://www.kitware.com/company/team/chaudhary.html</a></i></div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>