clipka <ano### [at] anonymousorg> wrote:
> Am 29.08.2015 um 23:15 schrieb Jérôme M. Berger:
>
> >> #declare the_tiling =
> >> union{
> >>     #for(i, 0, 99)
> >>         #for(j, 0, 99)
> >>             intersection{
> >>                 object{
> >>                 one_piece
> >>                 translate <i*0.4, j*0.4, 0>
> >>                 }
> >>                 cylinder{
> >>                 <20,20,0>,<20,20,1>,19
> >>                 }
> > Try to add these lines here:
> >     bounded_by { box { min_extent (one_piece)+<i*0.4, j*0.4, 0>,
> >                        max_extent (one_piece)+<i*0.4, j*0.4, 0> } }
> >>                 cutaway_textures
> >>             }
> >>         #end
> >>     #end
> >> }
>
> Why fix a perfectly good and fast-rendering scene? It's the other
> variant that takes ages to render.
>
> Besides, the intersection code /already/ makes sure that the bounding
> box isn't larger than what you suggest to specify manually; the bounding
> box for the intersection of a given set of objects defaults to the
> intersection of their bounding boxes.
>

Em...Clipka, I trust your profession on the POV-Ray's internal detail. But, for
this problem, why I add Jérôme M. Berger's adding code, its rendering time
decreases to 2 seconds?
I knew that POV-Ray makes a global bounding hierarchy for the first(global)
level .... But from the rendering time what I tried just now it seems that
POV-Ray didn't make boundings for my objects.

Post a reply to this message