Timwi <tim### [at] gmxnet> wrote:
> Thanks a lot... although it raises the question: why is that not the
> default? Why is the default something that is, apparently, broken by
> definition (because it doesn't calculate all intersections it needs to
> generate the correct result)?

It can have a significant performance advantage if the object is *not* used in
CSG (or, more specifically, differences or intersections), but directly at
scene level (or in unions).

(But then again, the user could still specify "max_trace 1" to benefit from that
speedup, so making all_intersections the default seems like a reasonable idea to
me. Maybe depending on the #version setting for backward compatibility.)

Post a reply to this message