|
![](/i/fill.gif) |
In article <3d5e7cf4$1@news.povray.org>,
"Andrew Cocker" <mai### [at] mariner9 net> wrote:
> I created a 3d grid of blob components using nested #while loops. The
> radius of each blob component relates to the greyscale value of a
> bozo pigment occupying the same points in space, which I sampled by
> using eval_pigment().
Reminds me of some macros I made once to create a blob from any object.
I used the eval_pattern() patch to evaluate an object pattern, for 3.5 I
would use a the inside() function or allow any user-defined function to
be used.
> I wasn't prepared for parse time to evaluate 8000 components. Any
> reason for it taking so long? (approx 1 minute.. not forever, I know,
> but I just assumed it would be a really quick operation)
Parsing is slow. The POV-Ray parser just wasn't designed to do this sort
of stuff quickly, that's why it is often easier to do things in an
external program, especially for complex particle systems or tree
generators. You're lucky it was so short...I've had hour long parses
before.
--
Christopher James Huff <cja### [at] earthlink net>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tag povray org
http://tag.povray.org/
Post a reply to this message
|
![](/i/fill.gif) |