In article <chr### [at] netplexaussieorg>, 
chr### [at] maccom says...

> correctly, it does something close (and practically equivalent) though: 
> if the bounding box intersection is further than the best (nearest) 
> intersection, the object is ignored.

Thats better than no such optimisation at all, but chances are that some 
computation intensive object (isosurface landscape for example) in the 
background will get unnecessary checked for intersections...

with my "algorithm" it is guarantied that this won't happen if its 
bounding box is behind any other (opaque) object.

Lutz-Peter

Post a reply to this message