Warp schrieb:
>   My guess is that specifying inside_vector makes the rendering of the
> mesh slower in some situations (probably eg. when there's media or fog
> around), which is why it's turned off by default.

I don't think so. Media would only be computed inside a mesh if the 
"hollow" keyword is also used anyway.

The only place where it should make a difference is when used with CSG 
intersection: In that case, performing proper inside tests instead of 
just returning "not inside" would be faster of course.

Anyway, the speed issue could be mitigated by allowing to explicitly 
specify "inside_vector <0,0,0>" (or, being equivalent yet more talktive, 
"inside_vector no") to disable inside tests.

Post a reply to this message