Tim Nikias wrote:

> So in order to quicken things up, you might want to break
> the CSG into smaller parts.

Note that, although faster with opaque objects, this might (and probably 
will) not only to be actually slower when using transparent objects (due to 
the need for more intersection tests and, with reflection, deeper 
recursion), but also produce some artifacts such as the infamous coincident 
surfaces problem. Using merge may help somewhat, but I don't think it gets 
rid of all the artifacts. Also, using such a composite object as a media 
container may be artifact-prone.

Post a reply to this message