 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gail Shaw <gsh### [at] monotix coza> wrote:
: eval
That slows down a lot.
Put a max_gradient by hand.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3a1d250f@news.povray.org...
> Gail Shaw <gsh### [at] monotixcoza> wrote:
> : eval
>
> That slows down a lot.
> Put a max_gradient by hand.
I've been meaning to ask, how does one calculate a max_gradient? I've
been just guessing and testing. But it seems that some folk have specific
values that they use.
In other words, mine always end up as round numbers or simple divisions
(2.5, 10, 3.25) but I have seen other people who use things like 12.23937
which leads me to think that they did some sort of calculation.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bill DeWitt" <the### [at] earthlinknet> wrote in message
news:3a1d464d@news.povray.org...
....
> which leads me to think that they did some sort of calculation.
>
Dunno what anyone else does - when I'm happy with the shape of my iso I set
a ridiculously high max_gradient, use eval, and then remove eval and replace
max_gradient with the value returned by eval. I tend to add 0.1 to the eval
"just in case".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tom Melly" <tom### [at] tomandlucouk> wrote :
>
> Dunno what anyone else does - when I'm happy with the shape of my iso I
set
> a ridiculously high max_gradient, use eval, and then remove eval and
replace
> max_gradient with the value returned by eval.
Huh...? "returned"? I guess I need to pay more attention to the message
window...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bill DeWitt <the### [at] earthlinknet> wrote:
: Huh...? "returned"? I guess I need to pay more attention to the message
: window...
When you use eval, the calculated max_gradient is output to the message
window when the rendering finishes. Somewhere there.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: Re: Crackle pigment in functions
Date: 23 Nov 2000 13:50:39
Message: <3a1d66ff@news.povray.org>
|
|
|
| |
| |
|
|
BTW: If you have more Isos with "eval" in the scene - there is no output of
the max_gradient , is it?
Marc-Hendrik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Marc-Hendrik Bremer wrote:
>
> BTW: If you have more Isos with "eval" in the scene - there is no output of
> the max_gradient , is it?
>
There is (in my IsoWood demo, you get whole pages of max_gradients :-)
BTW, i had several situations when 'eval' was faster than a specified
max_gradient, don't know why though.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
Homepage: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
news:3A1D08D7.54E75832@enst.fr...
> Gail Shaw wrote:
> >
> "crackle solid" has an infinite max_gradient, and the higher the
> max_gradient, the slower the render. If you really need it to be
> "solid", you might want to specify max_gradient manually, rather than
> using eval (but of course, if you lower it too much artifacts may
> appear).
>
Thanks, renders in 3 min without eval, looks terrible though.
I'm trying for a rough crystal look and normal crackle isn't quite
what I'm looking for.
Gail
--
********************************************************************
* gsh### [at] monotixcoza * System.dat not found. *
* http://www.rucus.ru.ac.za/~gail/ * Reformat hard drive Y)es O)k *
********************************************************************
* If at first you don't succeed, call it version 1.0 *
********************************************************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gail Shaw wrote:
>
> Thanks, renders in 3 min without eval, looks terrible though.
>
The default max_gradient is 1. Try specifying it manually (around 40
should give acceptable results) to get a good balace between rendering
time and visual result.
--
* Abandon the search for truth, * mailto:ber### [at] inamecom
* Settle for a good fantasy. * http://www.enst.fr/~jberger
*********************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann wrote:
>
> There is (in my IsoWood demo, you get whole pages of max_gradients :-)
>
> BTW, i had several situations when 'eval' was faster than a specified
> max_gradient, don't know why though.
>
Either you gave a much too high value for max_gradient, or else it
varies greatly from point to point in your isosurface (I think eval
adjusts the max_gradient on a point by piont basis, whereas max_gradient
is necessarily global, therefore if there are only a couple of points
with a high gradient, eval should be faster than using this high value
for every point).
--
* Abandon the search for truth, * mailto:ber### [at] inamecom
* Settle for a good fantasy. * http://www.enst.fr/~jberger
*********************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
