<span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Hi Utkarsh,</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Half-progress. So, I can display a variable-transparency volume rendering (in this case of a head MRI, set so that the 0s around the head are transparent). I can then add a .vtk surface, and I can sorta see "both" datasets when opacity on the surface is set to 1.00 ... the grayscale volume peeks through at various points of the overlying (colorized) surface. I'd like to be able to see more of the underlying volume, so I reduce the opacity value for the surface. However, for any opacity value < 1.00, paraview renders only the /back/ side of the surface (the part of the surface on the other side of the head from the camera viewpoint) ... the foreground portion disappears completely. After playing around with translations, I'd guess that for opacity<1.00 the volume is entirely rendered last, overwriting what should be foreground surface pixels. Does that make any sense? Perhaps I need to show a picture ...</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">-best</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Gary</span></div><div><br></div><br>Gray,<br><br>Currently ParaView supports changing the opacity in colormaps only for<br>
volume rendering. When rending slice or points as surface or anything<br>other than volume, opacity will be fixed to single value that can be<br>set on the Display tab.<br><br>Utkarsh<br><br>On Mon, Jun 20, 2011 at 4:30 PM, Gary Strangman<br>
<<a href="mailto:gary.strangman@gmail.com" style="color: rgb(0, 0, 204); ">gary.strangman@gmail.com</a>> wrote:<br>> Hi again all,<br>> I solved my linked-colormap problem when rendering multiple volumes (thanks<br>
> Utkarsh, using separate variable names worked great!). My next issue is<br>> this: can someone explain when colormap transparency is enabled? In some of<br>> my data views, the opacity option is grayed out (for example, in slice<br>
> renderings, and also in points data). I kinda understand the points case,<br>> but I was surprised by slice renderings. I suspect there is an underlying<br>> principle I'm missing here ...<br>> -best<br>
> Gary</span>