 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body text="#000000" bgcolor="#FFFFFF" link="#0000EE" vlink="#551A8B" alink="#FF0000">
Hi everyone. I'm using an old 486/100mhz to do raytracing, and when
rendering a scene at 640x400 with antialiasing depth 2 the fastest
I can seem to get it to go is 18 pps. (I'm using the WIN95 version)
I have all other programs shut down. Render priority on highest, GUI priority
on lowest, and the render window closed....are there any more ways to speed
up render time? Besides the obvious "turn down AA" or "buy a new
computer you cheapo". Any suggestions?
<br>
Kyle
</body>
</html>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Kyle wrote:
> Hi everyone. I'm using an old 486/100mhz to do raytracing, and when rendering a
scene at
> 640x400 with antialiasing depth 2 the fastest I can seem to get it to go is 18 pps.
(I'm
> using the WIN95 version) I have all other programs shut down. Render priority on
highest,
> GUI priority on lowest, and the render window closed....are there any more ways to
speed up
> render time? Besides the obvious "turn down AA" or "buy a new computer you cheapo".
Any
> suggestions?
> Kyle
Don't use refection in your finish statement.
Don't use any objects that require csg operations.
Don't use any high order polynominal objects.
Don't use filter or transmit in your pigments.
Don't use media or fog.
Don't use while loops.
Don't have more than a couple of objects in your scene.
Don't use specular or phong highlights.
Don't use high diffuse values.
Don't use layered testures and pigments.
Don't use area lights.
Don't have radiosity turned on.
Basicaly render solid colored spheres sitting on a solid
colored plane with only one light source.
Or buy a faster computer you CHEAPO !!!
--
Ken Tyler
tyl### [at] pacbell net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<body text="#000000" bgcolor="#FFFFFF" link="#0000EE" vlink="#551A8B" alink="#FF0000">
<p>Ken wrote:
<blockquote TYPE=CITE>Don't use refection in your finish statement.
<br>Don't use any objects that require csg operations.
<br>Don't use any high order polynominal objects.
<br>Don't use filter or transmit in your pigments.
<br>Don't use media or fog.
<br>Don't use while loops.
<br>Don't have more than a couple of objects in your scene.
<br>Don't use specular or phong highlights.
<br>Don't use high diffuse values.
<br>Don't use layered testures and pigments.
<br>Don't use area lights.
<br>Don't have radiosity turned on.
<p>Basicaly render solid colored spheres sitting on a solid
<br>colored plane with only one light source.
<p>Or buy a faster computer you CHEAPO !!!
<p>--
<br>Ken Tyler
<p>tyl### [at] pacbellnet</blockquote>
Unfortunately I'm guilty of just about all of that. :-(
</body>
</html>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken wrote:
> Kyle wrote:
>
> > Hi everyone. I'm using an old 486/100mhz to do raytracing, and when rendering a
scene at
> > 640x400 with antialiasing depth 2 the fastest I can seem to get it to go is 18
pps. (I'm
> > using the WIN95 version) I have all other programs shut down. Render priority on
highest,
> > GUI priority on lowest, and the render window closed....are there any more ways to
speed up
> > render time? Besides the obvious "turn down AA" or "buy a new computer you
cheapo". Any
> > suggestions?
> > Kyle
>
> >>>Don't use refection in your finish statement.
> Don't use any objects that require csg operations.
> Don't use any high order polynominal objects.
> Don't use filter or transmit in your pigments.
> Don't use media or fog.
> Don't use while loops.
> Don't have more than a couple of objects in your scene.
> Don't use specular or phong highlights.
> Don't use high diffuse values.
> >>>Don't use layered testures and pigments.
> Don't use area lights.
> Don't have radiosity turned on.
>
> Basicaly render solid colored spheres sitting on a solid
> colored plane with only one light source.
>
> Or buy a faster computer you CHEAPO !!!
>
> --
> Ken Tyler
>
> tyl### [at] pacbellnet
Isn't that strange ? When I post to news groups I always somehow
let a typo or two creep in but my pov scripts, with only an occassional
exception, perform without error.
--
Ken Tyler
tyl### [at] pacbellnet
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Comments to you Ken.
>
> Don't use refection in your finish statement.
*point* *grin*
> Don't use any objects that require csg operations.
The more so, use union instead of merge where possible, it's faster, can be done in
testing..
Difference is slowwwww...
> Don't use any high order polynominal objects.
If I don't understand them, I don't use them ???
> Don't use filter or transmit in your pigments.
Agree..
> Don't use media or fog.
Absolutely not...
> Don't use while loops.
Do this, but if you want to speed it up before final render, do an output to a file.
wether using the #debug or #fwrite is up to you, but it will reduce parsing a lot.
Same for #if and #switch
> Don't have more than a couple of objects in your scene.
When working, use a #if(fast=true) opbject { small_easy_thing_to_render } #else object
{
huge_memory_hog_that_looks_good_or_needs_work } #end
> Don't use layered testures and pigments.
See comment about #if for advanced objects
> Don't use area lights.
theese are huge...
> Don't have radiosity turned on.
Never...
>
> Basicaly render solid colored spheres sitting on a solid
> colored plane with only one light source.
yeah... or without the light with ambient 1 .....
> Or buy a faster computer you CHEAPO !!!
hmm.... well.... Get a quad alpha system or something.... *grin*
More..
If you have a scene that needs to swap(paging-file), make sure you defragment your
swap
file...
in win95/98 :
1 Defrag the hdd with the swap file on.
2 remove all startup programs from windows.
3 go to control panel->system->performance->virtual memory
3.5 disable virtual memory.
4 reboot to DOS
4.5 remove any .swp files in C:\windows or c:\
5 reboot to windows
6 defrag your hdd again
7 set the virtual memory to "own settings" - Min=40Mb(more if you think you'll need
it)-
-Max=300 (depends on free space)-
8 reboot
9 Restore all you startup programs
10 reboot.
This will make the swap file less defragmented, and will make it a bit faster if you
have
a scene that requires swapping... It's generally a good idea to defrag your hdd once a
week or something like that if you add/remove a lot o files.
//Spider
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
This piece of advice may be of dubious value but...
Overclock your machine. Until very recently I also had 486/100. I OC-d it to
120 MHz; it was still a piss-ant, but somewhat faster. Also, try to optimize
all your BIOS settings...
Anyway, this will only get you so far (and it _might_ muck up your machine,
if you don't know what you're doing)
So basically, just get a new machine! I now have a cheapo PII Celeron
333=>419MHz; POV is more than 10 X faster. Am I happy?
Margus
Kyle wrote in message <36A23F0B.8A9469FB@geocities.com>...
Hi everyone. I'm using an old 486/100mhz to do raytracing, and when
rendering a scene at 640x400 with antialiasing depth 2 the fastest I can
seem to get it to go is 18 pps. (I'm using the WIN95 version) I have all
other programs shut down. Render priority on highest, GUI priority on
lowest, and the render window closed....are there any more ways to speed up
render time? Besides the obvious "turn down AA" or "buy a new computer you
cheapo". Any suggestions?
Kyle
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hrmmmmmmmmmmmm. I might be wrong, but why are you using the Win95
version on a 486? It might be easier for basic development, but when it
comes time to render whip out that old boot disk and render it with the
dos compile. It will should be faster, because you won't have Win95
hogging resources for itself.
--
KillFile http://www.keldin.com
"If you want to live forever, Love a child"
There are many things in this world that
get more attention than they should, this
is not one of them
http://www.missingkids.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Besides the obvious "turn down AA" or
> "buy a new computer you cheapo". Any suggestions?
> Kyle
Get the DOS version of Povray; It runs _about_ 10% faster
than the Win95 one, even in a W95 dos box. If you boot
straight dos, you will get more availiable memory, too...
Fabien.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
A DOS version of 3.0 POV-Ray (unofficial) called POV-Pro, so no 3.1
capablities.
It's a render-speed-increased-compile. Just lacks a lot of the
"official" look. From what I remember from using it some myself, it can
be much faster. Believe the author stated "up to 40 or 50%" faster. But
I recall 25% (or is it 125%, percentages always confuse me) being the
average.
My URL to it seems to be broken now though, browser errors if attempt is
made to use it.
You could email me and ask for POV-Pro, put that in the subject line,
I'll send it over, I seem to have misplaced the original archive of it
though. All I found here is the povpro.exe itself (714K), no readme,
nothing.
It's basically a plain old DOS POV-Ray though. Works in the same way, no
editor, help, nothing though. Use the official version for that.
Kyle wrote:
>
> Hi everyone. I'm using an old 486/100mhz to do raytracing, and when
> rendering a scene at 640x400 with antialiasing depth 2 the fastest I
> can seem to get it to go is 18 pps. (I'm using the WIN95 version) I
> have all other programs shut down. Render priority on highest, GUI
> priority on lowest, and the render window closed....are there any more
> ways to speed up render time? Besides the obvious "turn down AA" or
> "buy a new computer you cheapo". Any suggestions?
> Kyle
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/POVring.htm
=Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 7 set the virtual memory to "own settings" - Min=40Mb(more if you think you'll
need it)-
> -Max=300 (depends on free space)-
Actually, I've been told that setting your swap file to twice your
memory (unless you have 16 megs, then 3 times) with Min = 2 x Memory and
Max 2 x Memory. This creates a permanent swap file which works faster,
and should be large enough.
Steve
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
