Ken <tyl### [at] pacbellnet> wrote:
:  Having answered this question on another newsgroup recently
: it reminded me how often it is asked. I know that this pretty
: much the same answer as given for the video card question but
: also expands upon it to cover other areas. I didn't see it on
: the VFAQ ( I might have missed it) so here is the response I
: gave.

  I added your response to the VFAQ and wrote also another one. My response
is far from complete; any suggestions are very welcome.
http://www.cs.tut.fi/~warp/povVFAQ.html#renderingspeed

-- 
main(i){char*_="BdsyFBThhHFBThhHFRz]NFTITQF|DJIFHQhhF";while(i=
*_++)for(;i>1;printf("%s",i-70?i&1?"[]":" ":(i=0,"\n")),i/=2);} /*- Warp. -*/

Post a reply to this message

Nieminen Mika wrote:
> 
> Ken <tyl### [at] pacbellnet> wrote:
> :  Having answered this question on another newsgroup recently
> : it reminded me how often it is asked. I know that this pretty
> : much the same answer as given for the video card question but
> : also expands upon it to cover other areas. I didn't see it on
> : the VFAQ ( I might have missed it) so here is the response I
> : gave.
> 
>   I added your response to the VFAQ and wrote also another one. My response
> is far from complete; any suggestions are very welcome.
> http://www.cs.tut.fi/~warp/povVFAQ.html#renderingspeed

Looks good to me.

-- 
Ken Tyler

tyl### [at] pacbellnet

Post a reply to this message

Hehe..
I just use speeding things where results get better/unchanged. Why ??? I belive in
optimized code...  (and I have a slow processor)

//Spider

Ken wrote:
> 
> Lance Birch wrote:
> >
> > Don't quote me on this... (I haven't used POV-Ray since I got MAX, so I
> > don't know if this still works...)
> >
> > Can you use the bounded_by statement still?  This would be one way to speed
> > up the CSGs...  or does POV-Ray do this automatically now?
> >
> > --
> > Lance.
> >
> > ---
> > For the latest MAX plug-ins, images and much more, go to:
> > The Zone - http://come.to/the.zone
> 
> Please note:
> 
> My suggestions have concentrated on the hardware end of speeding
> up the rendering process. I don't feel that tweeking the code
> as anything but a crutch. Limiting the capabilities of any
> software by not using it's features is limiting your abilities
> to use the program to it's fullest extent. For me there is no
> feature I will not use just because it takes a little longer.
> Don't let your hardware become a bottle neck. Starve the children
> and buy a faster machine. That's my motto.
> 
> --
> Ken Tyler
> 
> tyl### [at] pacbellnet

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

Use the Linux version, it's 40% faster  8-)

Post a reply to this message

Miguel Alvarez Rodriguez <nor### [at] abonadoscpluses> 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
>
>Use the Linux version, it's 40% faster  8-)

..or the DOS version!  Windows will slow down most any application!


-----------------------------
Orrin - Long Island, New York
orr### [at] orrinorg
http://www.orrin.org/carib/    (Caribbean Index)
http://www.orrin.org/syocc/    (Syosset Camera Club)
http://www.orrin.org/wphs/     (HS Reunion)
http://www.orrin.org/          (Site Index)

Post a reply to this message

Ken wrote:
> 
> Nieminen Mika wrote:
> >
> > Ken <tyl### [at] pacbellnet> wrote:
> > :  Having answered this question on another newsgroup recently
> > : it reminded me how often it is asked. I know that this pretty
> > : much the same answer as given for the video card question but
> > : also expands upon it to cover other areas. I didn't see it on
> > : the VFAQ ( I might have missed it) so here is the response I
> > : gave.
> >
> >   I added your response to the VFAQ and wrote also another one. My response
> > is far from complete; any suggestions are very welcome.
> > http://www.cs.tut.fi/~warp/povVFAQ.html#renderingspeed
> 
> Looks good to me.
> 
> --
> Ken Tyler
> 
> tyl### [at] pacbellnet

FYI here's the results of a little test I did the other day.
I made an array of spheres like this

union{ // switch this between merge and union
  #declare Z=-2;#while(Z<=2)
    #declare Y=-2;#while(Y<=2)
      #declare X=-2;#while(X<=2)
        sphere{<X,Y,Z>,0.9}
        #declare X=X+1;#end
      #declare Y=Y+1;#end
    #declare Z=Z+1;#end
    pigment{rgbt<1,1,1,.0.9>}
    bounded_by{box{-3,3}}  // toggle this line on and off
}

so I got an array of 5x5x5 spheres, set the camera so the spheres took
up about a quarter of the width of the image.  Now I rendered it using
union and with merge and also with/without bounding.

Results:
               pixels/second  
merge bound      4452
merge unbound    1528
union bound       933
union unbound    1839

So at least in this case the merge with manual bounding was by far the
fastest.

Cheers, PoD.

Post a reply to this message

On Sun, 17 Jan 1999 22:54:51 -0600, Bob Hughes <inv### [at] aolcom>
wrote:
[snip]
>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.
>
>
I've still got the original .zip file - even the samples .zip that
were on the site too. E-mail me for it/them (but expect a delay in my
reply) :)


Cheers,

Cliff Bowman
Why not pay my 3D Dr Who site a visit at
http://www.geocities.com/Area51/Dimension/7855/
PS change ".duffnet" to ".net" if replying via e-mail

Post a reply to this message

Ah ha! I found out why my URL to POVpro was not working.
I had mistakenly put "povray" as the final pathname.
Here it is, and it works:

ftp://terra.ru.com/pub/gamos/povpro/

POVpro is a DOS version of POV-Ray 3.0 optimized for speed.

Cliff Bowman wrote:
> 
> On Sun, 17 Jan 1999 22:54:51 -0600, Bob Hughes <inv### [at] aolcom>
> wrote:
> [snip]
> >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.
> >
> >
> I've still got the original .zip file - even the samples .zip that
> were on the site too. E-mail me for it/them (but expect a delay in my
> reply) :)
> 
> Cheers,
> 
> Cliff Bowman
> Why not pay my 3D Dr Who site a visit at
http://www.geocities.com/Area51/Dimension/7855/
> PS change ".duffnet" to ".net" if replying via e-mail

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/POVring.htm
=Bob

Post a reply to this message