On Wed, 03 Nov 1999 11:52:29 -0600, Lothar Esser wrote:
>Should I simply ignore this warning or is there something I can do about
>it.

You can specify -UR on the command line to turn off unnecessary bounds 
removal but it's a bug that POV tries to remove it in the first place,
and it might be considered a bug that it doesn't entirely succeed.
I've crossposted this message to .bugreports, with followups back to
..general.

POV will remove the bounds on all objects except unions, intersections,
merges, polys, and texts.  Obviously quadrics and quartics should be in
this list, too, unless they were among the handful of quadrics that 
POV can bound automatically (ellipsoids and axis-aligned cones, cylinders, 
paraboloids, hyperboloids, etc.)

The reason it still renders faster even after the bounding volume is 
removed is that the bounding box of the bounding volume gets assigned
to another variable in the quadric object [1] before the bounding 
volume gets nuked [2].  This bounding volume remains because the 
"computed" volume is "larger."  Thus, just destroying the bounding 
object doesn't entirely remove the effects of the bounded_by statement.

[1] POV computes bbox at the end of Parse_Object_Mods
[2] in Link_To_Frame, called by Parse_Frame after the object is completely 
    parsed
-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message