On 07/21/2014 09:47 PM, Bald Eagle wrote:
>
> Wicked cool.  I, embracing the technology of The Ancients, am able to render it
> in a mere 1:52. (4:27 with aa).

Suppose with ray tracing as in the movie Jaws, once you see the shark, 
you want a bigger boat. ;-)

>
> Thanks for the tip, WP!  While that gets me an amazing apple (really?  with only
> TWO pigments??),  I'm still just as ignorant about the ray ---> intersection
> output.  I also didn't see any notification in the message window about
> max_gradient.  Is it there?  Nothing leapt off the screen, grabbed me around the
> neck, and screamed, "LOOK AT ME!!!"   So I may have missed it.  :O
>

I admit to not spending much time with the intersection test values 
beyond checking them for sanity if I am getting a result which is 
completely wrong. That said, I believe what gets reported is basically a 
hierarchy of tests. How many rays hit the bounding box(es) -> how many 
of those rays hit the parametric containing sphere -> finally how many 
of those rays hit the parametric object.

As for a maximum gradient report. I re-ran Mike's example code 
commenting out the precompute option and adding a max_gradient of 0.5. 
Only a portion of the object renders, so I would expect to see a max 
gradient report - if they are reported for parametric objects - but I do 
not. Lastly looking at the source code for the parametric object, it 
doesn't look to me like any attempt is made to record and report a max 
gradient as is the case with isosurfaces.

Bill P.

Post a reply to this message