POV-Ray : Newsgroups : povray.general : min_ and max_extent of an intersection object : Re: min_ and max_extent of an intersection object Server Time
15 Jul 2024 13:40:56 EDT (-0400)
  Re: min_ and max_extent of an intersection object  
From: Thomas de Groot
Date: 27 Jun 2020 02:37:02
Message: <5ef6e90e@news.povray.org>
Op 26/06/2020 om 09:10 schreef jr:
> hi,
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> I should have known of course, and instead of swearing by Eagle the
>> Bald, sacrificing nameless things to the Clipka idol and invoking the
> (when making sacrifices, substituting the virgins with their grandmothers does
> not help!  :-))

I just discovered that indeed! ;-)

>> good spirit of Saint William of the Pokorny (in that order) for a couple
>> of days, I should have opened the Grimoire and read:
>> "Note: This is not perfect, in some cases (such as CSG intersections and
>> differences or isosurfaces) the bounding box does not represent the
>> actual dimensions of the object."
>> The hell it doesn't!
>> So, I am left with the good old trial-and-error finding of the right
>> dimensions/locations of intersection objects. Not a big deal afaiac ;-)
>> Still, I have been wondering if there would be other, smart, ways to do
>> the same? ...
> perhaps the 'Bounder' will work with "intersection objects"?

And so I forgot about that tool! :-/

However, it does not work either for the case in question. The results 
are different from the classical way but still wrong.

I attach a little test scene together with version 3 of Bounder where I 
only changed two #local statements to #declare.


Post a reply to this message

Download 'bounder.inc.txt' (9 KB) Download 'intersection_test.pov.txt' (5 KB)

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.