Dženan Zukić <dzenanz@gmail.com> writes:

> The mesh is the triangulated cube (side length=3D1, centered on
> 0,0,0). I a= m using slicing (as it is the only one which can render

> meshes). If I try 2D slicing or Raycasting, I get a warning about
> them not being able to render meshes.

okay, good, I was wondering if you had somehow managed to bypass that :)

Side note: if all you want is to see the boundary of the domain, just
turn on the "Global Bounding Box" from the "Render Options" widget.

Do you see this artifact without the mesh there?  It appears to happen
in the middle of the data, not the cube, so I'm curious if it's
actually related or just some other bug.

Finally... can you send me a rendering with "local bounding box" on?  I
want to see which bricks are yellow && which are green.

-tom

> On Mon, Dec 13, 2010 at 16:20, tom fogal <tfogal@sci.utah.edu> wrote:
>

> > D=C5=BEenan Zuki=C4=87 <dzenanz@gmail.com> writes:
> > > Probably on wishlist: proper (sorted) transparency, preferably as
> > > "per mesh " option. Attached screenshot shows artifacts.
> >
> > We do sort everything during rendering.  Which renderer are you
> > using?
> >
> > I don't see any mesh in there, FWIW...
> >
> > -tom