 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello!
I have a 486DX 66Mz with 32MB, and my rendering speed is very slow. Is
there a way to make it render faster?
-eugene
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
eugene (eug### [at] marblehead com) wrote:
> Hello!
> I have a 486DX 66Mz with 32MB, and my rendering speed is very slow. Is
> there a way to make it render faster?
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Roland Mas (bob### [at] casimirrezelenstfr) wrote:
: 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.
3. Avoid reflection and refraction in the same texture if possible, or
at least until the final rendering. If an object is both reflective and
refractive, the rendering time explodes. Alternatively use a smaller rendering
quality until final rendering.
4. If you have really complicated objects, replace them with a bounding
object until final rendering.
There are some things that are really slow, but that you have to test again
and again until you find the correct parameters, like the atmosphere, some
halo types, etc. I don't know how to speed this up, and it has caused me
a lot of problems (atmosphere looks a _lot_ different in a 64x48 sized
image than in a 800x600 sized)
--
- Warp. -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
eugene wrote:
>
> Hello!
>
> I have a 486DX 66Mz with 32MB, and my rendering speed is very slow. Is
> there a way to make it render faster?
>
> -eugene
A cheap solution that may help is to change operating systems. I assume
you're using Window 3.1 or Win95. Try installing and running under
Linux. You won't believe how fast that 486 will run once you get a
Microshaft operating system away from it. You can get a book at the
bookstore that has the full distribution of Linux on a couple of CD's
for your system, and POV-Ray is available for Linux. Also, I have made
a freeware application called POV-Motif available on the web at:
http://www.computek/net/public/wdh/pov_motif
This application give POV-Ray users a GUI front end for POV-Ray on UNIX
systems.
Regards,
--
William D. Hayden
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> You can get a book at the
> bookstore that has the full distribution of Linux on a couple of CD's
> for your system, and POV-Ray is available for Linux.
>
> William D. Hayden
Try http://www.cheapbytes.com - I picked up the Slackware 3.4 4-CD set
for about $7 plus S&H. I've been running Slackware for just under a week
and I already love it; I have yet to install POV under Linux, so I can't
verify the difference in rendering speed.
Cheers,
Chet Hosey
Professional Slacker
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
C. Hosey wrote:
> Try http://www.cheapbytes.com - I picked up the Slackware 3.4 4-CD set
>
> for about $7 plus S&H. I've been running Slackware for just under a
> week
> and I already love it; I have yet to install POV under Linux, so I
> can't
> verify the difference in rendering speed.
Another place is http://www.linuxmall.com/
They have free (+S&H, tho) CDs available, my suggestion is to get RedHat
4.2
Other options are the RedHat 4.2 Powertools 6-CD set for $30, or RedHat
5.0 full version with manual and some commercial apps for $50.
One REALLY awesome thing about POV on Unix machines - PVM. It's a
message-passing protocol that allows programs written for it to use
multiple networked machines as one machine with a huge amount of power,
and there's a patch for POV that allows you to use PVM. Of course, you
need access to a whole load of unused machines. (I'm borrowing this
from my HS... A roomful of 20 Cyrix 6x86-166 machines that are rarely
used. :) It appears that there isn't a POV-PVM port for Crash95, which
is unfortunate because I'd rather not have to install Linux and
reinstall Windoze on 20 machines. (FIPS doesn't like FAT32... FAT32
sucks.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This thread is 6 months old, probably dead, but here goes.
A few weeks ago I got Slackware Linux, primarially to make my renders
faster. So, I now triple boot. Windows NT 4.0, Dos 6.22, and Linux. I have
another hard drive on my system with Win95, so actually I can quad-boot.
I rendered one of my own scenes at 320x240 pixels as a benchmark
Linux 1:03
NT 4.0 1:05
Win95 1:10
Dos6.22 1:36
Linux is 2 seconds faster, probably because there was no display. (I still
can't get that to work.) NT was with PovWin3.02, render priority on maximum.
So was Win95. I was really surprised by how slow dos is. I remember it being
faster than WinNT. I guess not.
Linux is faster, but only by about 2%. I guess it's worth it if it means 98
hours for an animation instead of 100.
My $0.02
Chris Jeppesen
http://www.geocities.com/CapeCanaveral/Launchpad/3392/
C. Hosey wrote in message <349### [at] cobwebnet>...
>> You can get a book at the
>> bookstore that has the full distribution of Linux on a couple of CD's
>> for your system, and POV-Ray is available for Linux.
>>
>> William D. Hayden
>
>Try http://www.cheapbytes.com - I picked up the Slackware 3.4 4-CD set
>for about $7 plus S&H. I've been running Slackware for just under a week
>and I already love it; I have yet to install POV under Linux, so I can't
>verify the difference in rendering speed.
>
>Cheers,
>Chet Hosey
>
>Professional Slacker
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
news:348### [at] geocitiescom...
>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.
>
Now, 8 years after that posting, I have a new 3000mhz computer with 512 megs
of ram!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
