 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <411f6ukkqp1uplrl14b1sn582vk372o0hb@4ax.com>,
W?odzimierz ABX Skiba <abx### [at] babilon org> wrote:
> Yes, I know, but then speed optimization with boundary will not work.
Just use separate macros...the blur pattern functionality would be very
useful, but having specialized macros optimized for specific patterns is
still possible.
> > BTW, why use "(1/C)*(...)" instead of just "(...)/C"?
> Becouse C is index for loop and after loop it has value 0.
"(...)/Count" will still work. I don't think that max() call is
necessary, but you could also just save the value of C before the loop
in another variable.
> Afaik 1/C is optimized to one float at parse time so it not the problem for
> parser.
It just makes it less obvious that you are dividing the sum by the
number of samples.
Hmm, something that would probably slow it down too much to be useful,
as well as being more difficult to implement, but it would be
interesting if it was modified to take samples in a sphere instead of a
cube...
--
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3C66D808.B664D528@hotmail.com>,
Tor Olav Kristensen <tor### [at] hotmailcom> wrote:
> Christopher James Huff wrote:
> >
> >...
> > BTW, why use "(1/C)*(...)" instead of just "(...)/C"? And
> > "max(int(Count)1)" should be "max(int(Count), 1)".
>
> Have you tried to do that Christopher ?
As ABX pointed out, the value of C is modified by the loop, you would
have to save it in another variable or drop the error testing that
rejects values for count < 1.
--
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christopher James Huff wrote:
>
> In article <3C66D808.B664D528@hotmail.com>,
> Tor Olav Kristensen <tor### [at] hotmailcom> wrote:
>
> > Christopher James Huff wrote:
> > >
> > >...
> > > BTW, why use "(1/C)*(...)" instead of just "(...)/C"? And
> > > "max(int(Count)1)" should be "max(int(Count), 1)".
> >
> > Have you tried to do that Christopher ?
>
> As ABX pointed out, the value of C is modified by the loop, you would
> have to save it in another variable or drop the error testing that
> rejects values for count < 1.
Yes, of course. Sorry.
I didn't notice that it also was the counting variable.
Tor Olav
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
