|
 |
--------------( oo )--------------
Thousand of excuses, SeeSchloss
Sometimes shortkuts (SK) produces undesirable effects. Sorry for the SS, it
was naive, and when I see those two letters together, I don't think to the
SS.
> But still, it was not as fun as doing everything in POV ;)
Some time ago I was more active on PovRAY, but maybe less today. I find
others programming languages more complete and effective. Everything that is
geometry related (Vector override operators - Rotations - Matrix
transformation) miss me a lot. Then, why did you switched to Exclusivly
PovRAY?
Regards,
--------------( oo )--------------
guillaumeLaBelle [alias goo?] -
Architecture CAAO Website[VIF]
"SeeSchloss" <adr### [at] seeschloss org> wrote in message
news:pan### [at] seeschlossorg...
>
> > Hi SS,
> >
> > I was working with CA's longtime ago on POVray. I had the same problems
> > that you mention. I started to do CA's simulation in 3D and I tried to
> > render 500x500x500 with a text file to remember the array. This
strategy
> > was uncomputable (very too long). Then, I used java directly to produce
a
> > parsable file with the strict minimum for povray. The simulation is done
> > in Java (fast) and it could be exported to POVray.
> >
> > Here's some examples;
> >
> > http://ingallian.design.uqam.ca/goo/VDO/gPov00.avi
> > http://ingallian.design.uqam.ca/goo/VDO/aC3D-Stack.mpg
> > http://ingallian.design.uqam.ca/goo/VDO/aC-XVID.avi
>
> Nice, I just thought I should try to create an include file with an
> external program, to see the improvement in parsing time. I modified a bit
> the program I made some time ago in D for standard 2D cell automata...
> parsing a 50x50x100 world in POVRay took 35s while writing a 500x500x100
> include file (289MB !) with my program took 11s (0.037s for a 50x50x10
> world and 43s for 500x500x500) :D
>
> But still, it was not as fun as doing everything in POV ;)
>
> And... well SS reminds me of not so funny things, maybe I shouldn't
> capitalise the second S...
Post a reply to this message
|
|
