On 11 Sep 2002 07:50:32 -0400, Warp <war### [at] tagpovrayorg> wrote:
> Planes:   75 s
> Polygons: 80 s
> Mesh:     63 s

since the uvmapped box was counted as possible solution for the question in
subject where is the time for boxes :-)

ABX

Post a reply to this message

Warp wrote:
> 
> Ken <tyl### [at] pacbellnet> wrote:
> > With limitations. From some tests I just ran it appears the mesh must be
> > the top level object in the csg operation. If used a secondary object
> > in a csg it does not work as expected.
> 
>   I remember that this bug was found months ago. I wonder if anyone made
> a proper post at p.bug-reports... (if not, someone should).

I only vaugly remember this topic and don't recall if it was ever confirmed
and reported. If confirmed I would be willing to file a formal bug report.

-- 
Ken Tyler

Post a reply to this message

In article <3d7f2e08@news.povray.org>, Warp <war### [at] tagpovrayorg> 
wrote:

>   I made a test with boxes made of planes, polygons and a mesh (with
> differently colored sides) and compared their rendering speed
> (-w800 -h600 +a0.1) by randomly placing 500 of them in the scene.
> The render times were:
> 
> Planes:   75 s
> Polygons: 80 s
> Mesh:     63 s
> 
>   Seems like the mesh wins.

Hmm, not what I expected. I would have thought that finding an 
intersection against 12 planes and clipping them to triangles would be 
slower than intersecting 6 planes...maybe the mesh bounding is making 
more of a difference than I thought, or maybe intersection has more 
overhead than I thought.

Hmm, maybe a union of 6 clipped planes would be faster. Bound each plane 
individually, so POV can eliminate the faces...

-- 
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/

Post a reply to this message