"Chris Huff" wrote:
> > > BTW I don't know why MP clamps negative values to zero.
> >
> > Neither do I and I would *really* like someone to explain it to me...
>
> Perhaps because it was intended to simulate transparency and
> was only designed to work in the range of 0-1?
> As far as I can tell, MegaPOV does it the way it is supposed
> to work.

If it is supposed to be used in the range of 0 to 1 only, then using values
outside this range should generate an error or at least a warning.

However, there is no reason to confine the valid values to be from 0 to 1.
Being able to use values outside this range will be *very* useful - not for
realism, but for many other things.

Anyway, values outside the 0 to 1 range *can* be used; the question is why
it works in such a strange way. Is there an actual senseful reason behind,
or was it coded this way for no particular reason?

I would find it very annoying if I am prevented from effectively using a
powerful feature for "no particular reason". I'm not saying that there isn't
a good reason for the way it works, but it really bothers me not to know
what it is, or if there is one at all.

That's why I would *reeeaally* like to be told *why* *it* *works* *as* *it*
*does*!
(Both for official POV-Ray and for MegaPOV).

Oh well, I guess that if you want to have something changed, you gotta do it
yourself.
And if you can't - sigh...

Rune
--
\ Include files, tutorials, 3D images, raytracing jokes,
/ The POV Desktop Theme, and The POV-Ray Logo Contest can
\ all be found at http://rsj.mobilixnet.dk (updated October 9)
/ Also visit http://www.povrayusers.org

Post a reply to this message