<br><br><div><span class="gmail_quote">On 5/7/07, <b class="gmail_sendername">Berk Geveci</b> <<a href="mailto:berk.geveci@kitware.com">berk.geveci@kitware.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> i am running paraview3 beta (cvs checkout today, 2007.05.07)<br>> with openmpi, and i am having some trouble getting the surface<br>> color widget to show up. it seems i have to first tell paraview to<br>> color by normals, then switch back to color by scalars, which
<br>> then brings up the color selection button. strange behavior.<br><br>This is a known bug. Someone reported it previously. I believe someone<br>in the team either fixed it or will fix it.</blockquote><div><br>ok... i'll take your word for it. :) i have now looked through all the
<br>
paraview3 bugs on the bug tracker and i didn't see it, so if you want<br>
me to report it, let me know. </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> i've also found that when some transparency is set, the integrity
<br>> of the isosurface is poor... that is, there are some raster lines in<br>> and other artifacts in the surface. anyone experienced the same<br>> on their build of paraview3? i am running on linux64 (suse 10.0
)<br>> with the latest build of the drivers for my graphics card. i have<br>> composite rendering turned off, and am running in server/client<br>> mode on a single (4-process) machine.<br><br>A screenshot would be helpful in tracing this.
</blockquote><div><br>ok, will do tomorrow when at the work machine where this happens.<br>basically, the image is corrupted in the sense that there are lines and<br>other artifacts that make it look like the transparency has not been
<br>appropriately assigned to all faces of the mesh. might be an mpi or<br>graphics card issue if this has not been seen by other users...<br><br>bryan<br></div></div>