> Just read the manual.  Apart from that it would also be advisable to check
> what the trace function actually returns before jumping to quick
> conclusions about bugs.  If you did that you would see that all points
> returned by a successful trace (which is tested differently than you do in
> your code) are perfectly on the object surface.
> 
> I think we should introduce a new rule: everyone who falsely assumes there
> is a bug in POV-Ray has to do something unpleasant (like 10 times
> rendering the POV-Ray benchmark or so...)

Well, I was just looking to know if that was a known problem of the 
trace function, but if you tell me the trace function is not responsible 
for the bug, then it is my code and it answers my question!

Thank you!
   Xilo

-- 
Dedicated to audio/visual and interactive artwork.
Author of The Primary Colors of CSound:
http://www.geocities.com/simonlemieux/PCCS/index.html

Post a reply to this message