I run on a 486/33mhz with 20 megs of ram and you are damn well right
when you say it teaches you patience. Hell I believe that sitting around
waiting for my scene to finish has made me a better man. 

oh yeah if you go under the RENDER menu then scroll down to RENDER
PRIORITY... choose HIGHEST. This will speed up your rendering a lot. i
saw this and realized that i was running on normal mode all this time
when i could of been running it faster. what also comes in handy is
turning the RENDER PRIORITY down and then just play around on you
computer till its done this way if frees up more ram for you to do
stuff. it also means that the scene will take longer to finish but at
least you won't be completely bored.
But hey if you get bored while its rendering play my tictactoe game you
can play against computer or opponet
For a cool game of tictactoe download it at 
http://www.visualmax.com/visualist/tictactoe.zip

----
Taylor Maguire
vis### [at] mailcitycom
http://www.visualmax.com/visualist


> Even two ones!
> 1. The easier one: buy a computer. I did it recently, and was _really_
> surprised how much difference a P200 MMX had in rendering speed compared
> to a 486DX2/66 with 24 Mb RAM.
> 2. The cheaper one: optimize your scenes. I used to do it (and still do,
> of course), and thus saved _lots_ of rendering time. Use bounding boxes
> and automatic bounding. Use simple texture until the final rendering. Same
> for the atmospheric effects.
> 
> Anyway, always remember: difficulty teaches you patience. I started raytracing
> with DKBTrace 2.12 on an Atari 520 STE (8 MHz, 512 Kb RAM). Since then I was
> constantly astonished by the evolution: POV 1, then PC with a hard disk, then
> POV 2, then a 386, then a 486DX2/66, then POV 3, then a Pentium 200 MMX...
> I still consider starting on a too powerful machine as an encouragement to
> dirty and unoptimised code. Rendering two coloured spheres at 80x50 in
> 30 minutes, that teaches patience.
> 
> B-o-b
> --

> bob### [at] casimirrezelenstfr -- Linux, POV-Ray, LaTeX

Post a reply to this message