In article <3654B0CB.BFF188F2@flash.net>, Dan Connelly wrote:
>This is a good idea.  The simplest generalization would be
>for a vector to have its components logically or'ed when used
>in a boolean context.... I don't know how distributed through 
>the code is the logical evaluation of parameters, but I suspect
>this could be done in a compact fashion (wherever the error is generated,
>a conversion could be done instead).

The problem with this is, you want to or them for != and and them
for =.  You have to actually do the conversion a bit further down
the parse tree, but I've already figured out how it is to be done.

Post a reply to this message

On 19 Nov 1998 23:24:11 -0500, root <root@parkrrrr.> wrote:

[snip]

In case anyone cares, that was me.  Clearly I need to fix my 
.slrnrc on the root account. :)

Post a reply to this message

I see... The bounding object feature would still offer more ease of use in all
kinds of collision detection applications; but since this can also be done in
POV script without any significant disadvantage, I won't whine if it isn't
implemented in the source.
Btw. I think there might be some advantages to using light ray bounding, for
example with light attenuation and radiosity... Not sure, though.

Margus

Ron Parker wrote:
> 
> The way POV works is to first find all intersections, then find the closest
> one (except in certain cases like isosurfaces and some other objects.)  The
> existing code doesn't have a concept of bounding a ray, because there is no
> use for such a thing in tracing light rays.  What you're asking for can't be
> done any more efficiently in C than it can in POV script, except for certain
> objects that could be optimized with much labor.

Post a reply to this message