 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The pps display to the bottom right starts
averaging at the beginning of parsing, not the
beginning of actually putting pixels in the output
file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Matt Giwer wrote:
>
> The pps display to the bottom right starts
> averaging at the beginning of parsing, not the
> beginning of actually putting pixels in the output
> file.
Well, this is only fair; the effective rate of picture generation is
reduced by the time taken to parse.
--
ICQ: 46085459
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 14 Dec 1999 17:06:00 -0800, Matt Giwer <jul### [at] ij net> wrote:
> The pps display to the bottom right starts
>averaging at the beginning of parsing, not the
>beginning of actually putting pixels in the output
>file.
Yep. I never trust it, esp. for long renders. I can estimate the time
with about 5% accuracy, and that's enough for me.
Peter Popov
pet### [at] usanet
ICQ: 15002700
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
John VanSickle wrote:
> Well, this is only fair; the effective rate of picture generation is
> reduced by the time taken to parse.
Fair ... to me only misleading.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Matt Giwer wrote in message <3856E978.C47E5AA3@ij.net>...
> The pps display to the bottom right starts
>averaging at the beginning of parsing, not the
>beginning of actually putting pixels in the output
>file.
That's why my personal version of POV-Ray displays the number of pixels
rendered in the last second there, instead of displaying a running average.
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wouldn't displaying the number of pixels in the last line be more
meaningful?
One way or another: I would like to be able to guess how long it will take
the rendering to finish.
BTW: I fail to find the place from where I can download the POV sources...
--
Regards,
Sander
Mark Wagner <mar### [at] gtenet> schreef in berichtnieuws
38572bd4@news.povray.org...
>
> That's why my personal version of POV-Ray displays the number of pixels
> rendered in the last second there, instead of displaying a running
average.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sander wrote:
> BTW: I fail to find the place from where I can download the POV sources...
The source files are available in the FTP site under their respective
platforms. For example the source for the windows version is available
as povwin_s.zip in the windows directory.
ftp://ftp.povray.org/pub/povray/Official/
--
Wishing you Seasons Greetings, A Merry Christmas, and A Happy New Year !
Ken Tyler - 1200+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sander wrote:
>
> Wouldn't displaying the number of pixels in the last line be more
> meaningful?
> One way or another: I would like to be able to guess how long it will
> take
> the rendering to finish.
I was hoping the next version of POV-Ray would give some info on that.
Meanwhile I made a simple program for myself that gives a rough
estimate. It works for me (with render-times that are often >day)
although very in accurate. I think it could be refined a bit. Anyways,
if you're interested look for ETA at my POV-page
(http://www.xs4all.nl/~remcodek/pov.html). Sorry, Windows9x only.
> BTW: I fail to find the place from where I can download the POV
> sources...
> --
> Regards,
> Sander
>
Remco
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
John VanSickle wrote:
> Matt Giwer wrote:
> >
> > The pps display to the bottom right starts
> > averaging at the beginning of parsing, not the
> > beginning of actually putting pixels in the output
> > file.
>
> Well, this is only fair; the effective rate of picture generation is
> reduced by the time taken to parse.
The reason it bothered me was in the garden scene over
binary.images. Just pieces of the scene were taking hours and got much
longer when two parts were rendered at the same time.
So I put all the pieces together for nearly a half hour parse time
and it shows me 1 PPS when it starts. I shrugged an "oh well" and let it
run. Then I realized it was rendering much faster than that. It climbed
up to 10 PPS and then back down to 8 PPS when it got to the slow
objects.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
