POV-Ray : Newsgroups : povray.msdos : Trace timer problem Server Time
20 Nov 2026 09:41:22 EST (-0500)
  Trace timer problem (Message 1 to 21 of 21)  
From: Alf Peake
Subject: Trace timer problem
Date: 20 Nov 1999 05:57:44
Message: <38367ea8@news.povray.org>
I was comparing the trace times of 2 similar scenes when I came across this
problem with povray's trace timer.

Using this commandline:
\dos\povray\povray +iTIMER +w160 +h120 +p +d

with this remnant of the original scenes:
// Complete TIMER.POV file
camera{ location -100*z angle 40 look_at 0 }
light_source { <100,70,-600> color rgb 1 }
background{ rgb 0.5 }
// eof

the completed trace is displayed and statistics then show that the timer
keeps running most times until a key is pressed. Also <time for parse> is
not always shown.

It is OK at 320*200 up, or with other scenes I've tried. I've not had time
to play further.

I'm using DOS povray 3.1d, Win98SE and Celery 500.
No change booting to DOS instead of W98 DOS prompt, or using default
povray.ini


Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/


Post a reply to this message

From: Nieminen Juha
Subject: Re: Trace timer problem
Date: 21 Nov 1999 14:52:48
Message: <38384d90@news.povray.org>
Alf Peake <alf### [at] peake42freeservecouk> wrote:
: Also <time for parse> is not always shown.

  I think that when <time for parse> is 0 seconds, then it's not shown.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/


Post a reply to this message

From: Peter Popov
Subject: Re: Trace timer problem
Date: 21 Nov 1999 16:03:28
Message: <5104OGkuYU1wKXKgzw0DJ3k2pfZr@4ax.com>
On 21 Nov 1999 14:52:48 -0500, Nieminen Juha
<war### [at] punarastascstutfi> wrote:

>Alf Peake <alf### [at] peake42freeservecouk> wrote:
>: Also <time for parse> is not always shown.
>
>  I think that when <time for parse> is 0 seconds, then it's not shown.

Can you confirm this? Do you have access to a DOS box? Is it a bug and
if yes, is it documented?


Peter Popov
ICQ: 15002700


Post a reply to this message

From: Chris Colefax
Subject: Re: Trace timer problem
Date: 21 Nov 1999 18:46:08
Message: <38388440@news.povray.org>
Alf Peake <alf### [at] peake42freeservecouk> wrote:
>: Also <time for parse> is not always shown.

Nieminen Juha wrote:
>  I think that when <time for parse> is 0 seconds, then it's not shown.

Peter Popov <pet### [at] usanet> wrote:
> Can you confirm this? Do you have access to a DOS box? Is it a bug and
> if yes, is it documented?

Yes, if the scene requires very little parsing then only the render time
is shown.  In fact, if the scene requires less than a second of
rendering then this isn't shown either!   For animations, however, this
seems to be taken into account fine when calculating the average parsing
and rendering speed, and I wouldn't say I think of this as 'buggy'
behaviour myself.


Post a reply to this message

From: Peter Popov
Subject: Re: Trace timer problem
Date: 21 Nov 1999 20:00:32
Message: <Z5U4OIb1STONjeTqFIZuyfjcymQ6@4ax.com>
On Mon, 22 Nov 1999 09:54:54 +1000, "Chris Colefax"
<cco### [at] geocitiescom> wrote:

>Peter Popov <pet### [at] usanet> wrote:
>> Can you confirm this? Do you have access to a DOS box? Is it a bug and
>> if yes, is it documented?
>
>Yes, if the scene requires very little parsing then only the render time
>is shown.  In fact, if the scene requires less than a second of
>rendering then this isn't shown either!   For animations, however, this
>seems to be taken into account fine when calculating the average parsing
>and rendering speed, and I wouldn't say I think of this as 'buggy'
>behaviour myself.

Thanks, Chris. I am glad it's actually a well-thought feature rather
than a bug. It makes sense, too.


Peter Popov
ICQ: 15002700


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 22 Nov 1999 17:32:04
Message: <3839c464@news.povray.org>
Sorry if I did not make it very clear what I was getting.
I would only consider I had a problem if I needed to use the <time for
parse/trace> data (which I was doing). I have no problems with the trace
itself.
Using TIMER.POV and command line both as shown in my first post, in DOS you
get a normal render full-screen preview completed within 1 second, then pov
waits for you to hit a key. So you wait around 15 secs for this demo then
hit one. Screen clears and you get the statistics screen which I've dumped
to the attached text file. Notice the trace time? Timer only stops when you
hit the key, not when the trace stops.

Murphy's law says I can't get a dump with the missing <time for parse> :(

Later...

Just tried this on another PC with Pov v3.1d for dos - a Pentium 166
non-MMX, Win95a, booting to dos, and W95a dos prompt. Same problem exists.

Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/


  Chris Colefax <cco### [at] geocitiescom> wrote in message
news:38388440@news.povray.org...
> Alf Peake <alf### [at] peake42freeservecouk> wrote:
> >: Also <time for parse> is not always shown.
>
> Nieminen Juha wrote:
> >  I think that when <time for parse> is 0 seconds, then it's not shown.
>
> Peter Popov <pet### [at] usanet> wrote:
> > Can you confirm this? Do you have access to a DOS box? Is it a bug and
> > if yes, is it documented?
>
> Yes, if the scene requires very little parsing then only the render time
> is shown.  In fact, if the scene requires less than a second of
> rendering then this isn't shown either!   For animations, however, this
> seems to be taken into account fine when calculating the average parsing
> and rendering speed, and I wouldn't say I think of this as 'buggy'
> behaviour myself.
>
>


Post a reply to this message


Attachments:
Download 'scrndump.txt.dat' (3 KB)

From: Peter Popov
Subject: Re: Trace timer problem
Date: 22 Nov 1999 18:31:08
Message: <pdE5OBr2YbS03sX9n4nW+EMt=FzP@4ax.com>
Alf,

if indeed the timer does not stop until a key is pressed, even after
the trace is finished, then this looks like a bug. I do not have the
MS-DOS version so will you please try it on several different files /
resolutions and if you can confirm it is indeed a bug, post a bug
report. Thank you in advance.


Peter Popov
ICQ: 15002700


Post a reply to this message

From: Gerald K  Dobiasovsky
Subject: Re: Trace timer problem
Date: 22 Nov 1999 21:10:54
Message: <3839f7ae@news.povray.org>
[...after a quick, rather non-systematic test]
Happens too under MS-DOS 6.20.
Couldn't get the parse time to disappear, though.

--
Gerald
ger### [at] aonat


Post a reply to this message

From: Alan Kong
Subject: Re: Trace timer problem
Date: 23 Nov 1999 05:51:42
Message: <Y3E6OC7wKMMkJLAef8ArbixB7360@4ax.com>
On Mon, 22 Nov 1999 14:48:23 -0000, "Alf Peake"
<alf### [at] peake42freeservecouk> wrote:

>Screen clears and you get the statistics screen which I've dumped
>to the attached text file.

  Hi, Alf. You can paste those stats into the body of your message to
avoid using attachments. Much appreciated, thanks.

-- 
Alan - ako### [at] povrayorg - a k o n g <at> p o v r a y <dot> o r g
http://www.povray.org - Home of the Persistence of Vision Ray Tracer


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 24 Nov 1999 17:02:43
Message: <383c6083@news.povray.org>
Peter,

Problem seems related to camera+resolution.
I've used 160*120 as one of my regular resolutions since Pov 2.1
and feel certain I would have noticed this before if it was a regular
occurence.
I'll play with it a bit more.
Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/



Peter Popov <pet### [at] usanet> wrote in message
news:pdE5OBr2YbS03sX9n4nW+EMt=FzP@4ax.com...
> Alf,
>
> if indeed the timer does not stop until a key is pressed, even after
> the trace is finished, then this looks like a bug. I do not have the
> MS-DOS version so will you please try it on several different files /
> resolutions and if you can confirm it is indeed a bug, post a bug
> report. Thank you in advance.
>
>
> Peter Popov
> ICQ: 15002700


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 24 Nov 1999 17:02:44
Message: <383c6084@news.povray.org>
Thanks for the confirmation, Gerald.
That seems to suggest it is not my system setup :-)

Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/


Gerald K. Dobiasovsky <ger### [at] aonat> wrote in message
news:3839f7ae@news.povray.org...
> [...after a quick, rather non-systematic test]
> Happens too under MS-DOS 6.20.
> Couldn't get the parse time to disappear, though.
>
> --
> Gerald
> ger### [at] aonat
>


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 24 Nov 1999 17:02:45
Message: <383c6085@news.povray.org>
Alan,

Yes, I tried that but word-wrap made a right untidy mess of the paste and I
wasn't sure if the post would be the same.

Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/


Alan Kong <ako### [at] povrayNO-SPAMorg> wrote in message
news:Y3E6OC7wKMMkJLAef8ArbixB7360@4ax.com...
> On Mon, 22 Nov 1999 14:48:23 -0000, "Alf Peake"
> <alf### [at] peake42freeservecouk> wrote:
>
> >Screen clears and you get the statistics screen which I've dumped
> >to the attached text file.
>
>   Hi, Alf. You can paste those stats into the body of your message to
> avoid using attachments. Much appreciated, thanks.
>
> --
> Alan - ako### [at] povrayorg - a k o n g <at> p o v r a y <dot> o r g
> http://www.povray.org - Home of the Persistence of Vision Ray Tracer


Post a reply to this message

From: Gerald K  Dobiasovsky
Subject: Re: Trace timer problem
Date: 24 Nov 1999 17:30:13
Message: <383c66f5@news.povray.org>
I've never stumbled upon this bug, because I don't use the preview
display under DOS (always staring at the statistics output instead ;)).

--
Gerald
ger### [at] aonat


Post a reply to this message

From: Chris Colefax
Subject: Re: Trace timer problem
Date: 24 Nov 1999 17:40:40
Message: <383c6968@news.povray.org>
Peter Popov <pet### [at] usanet> wrote:
> if indeed the timer does not stop until a key is pressed, even after
> the trace is finished, then this looks like a bug. I do not have the
> MS-DOS version so will you please try it on several different files /
> resolutions and if you can confirm it is indeed a bug, post a bug
> report. Thank you in advance.

A little rummage around in the source reveals it is indeed a bug, but
not specific at all to the MS-DOS version.  The mentioned non-display of
parse and/or trace time when either is less than 1 second should occur
on all platforms (try rendering light_source {0, 0} with a width and
height of 1 if you're looking for a suitably quick scene to confirm
this).

The bug occurs in the main program loop, where the timer is not stopped
until the tracing function is finished.  But the tracing function(s)
includes the display of the image while it is being rendered, and at the
end includes the waiting for a keypress to exit (ie. the bug doesn't
occur if you use -D to not display the image, and the bug doesn't occur
in POV-Ray for Windows because it doesn't support the +P pausing
option).

As bugs go I would have to say it seems more like an oversight, and its
effects are fairly limited.  Nevertheless, if Alf would like to post a
bug report about this I'm sure you (Peter) can enlighten him on the
correct procedure...


Post a reply to this message

From: Ken
Subject: Re: Trace timer problem
Date: 24 Nov 1999 18:05:09
Message: <383C6ECA.B56CD5CC@pacbell.net>
Alf Peake wrote:
> 
> Alan,
> 
> Yes, I tried that but word-wrap made a right untidy mess of the paste and I
> wasn't sure if the post would be the same.
> 
> Alf

I used to have that problem too but now I just set my line length to about
100 characters and never have the problem anymore.

-- 
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

From: Peter Popov
Subject: Re: Trace timer problem
Date: 24 Nov 1999 20:52:45
Message: <BZY8OECPVONTwzTC9QwvXrsUzVvm@4ax.com>
On Wed, 24 Nov 1999 14:15:15 -0000, "Alf Peake"
<alf### [at] peake42freeservecouk> wrote:

>Peter,
>
>Problem seems related to camera+resolution.
>I've used 160*120 as one of my regular resolutions since Pov 2.1
>and feel certain I would have noticed this before if it was a regular
>occurence.
>I'll play with it a bit more.
>Alf

I tried it with a 4x3 image and it rendered in a flash. I let it wait
for keypress for about half an hour and that time was indicated as
render time. I posted a bugreport and Alan seems to have qualified it
as valid because it made its way into povray.bugreports


Peter Popov
pet### [at] usanet
ICQ: 15002700


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 26 Nov 1999 17:52:32
Message: <383f0f30@news.povray.org>
I see your post in bugreports so guess no need for me to do anything else?

Alf


Peter Popov <pet### [at] usanet> wrote in message
news:BZY8OECPVONTwzTC9QwvXrsUzVvm@4ax.com...
> On Wed, 24 Nov 1999 14:15:15 -0000, "Alf Peake"
> <alf### [at] peake42freeservecouk> wrote:
>
> >Peter,
> >
> >Problem seems related to camera+resolution.
> >I've used 160*120 as one of my regular resolutions since Pov 2.1
> >and feel certain I would have noticed this before if it was a regular
> >occurence.
> >I'll play with it a bit more.
> >Alf
>
> I tried it with a 4x3 image and it rendered in a flash. I let it wait
> for keypress for about half an hour and that time was indicated as
> render time. I posted a bugreport and Alan seems to have qualified it
> as valid because it made its way into povray.bugreports
>
>
> Peter Popov
> pet### [at] usanet
> ICQ: 15002700


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 26 Nov 1999 17:52:33
Message: <383f0f31@news.povray.org>
I'm a lost soul since pov became extinct on Compuserve. Dipping my feet into
newgroups for the first time the last couple weeks, and still learning how
to drive OExpress5.

Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/


Ken <tyl### [at] pacbellnet> wrote in message
news:383C6ECA.B56CD5CC@pacbell.net...
>
>
> Alf Peake wrote:
> >
> > Alan,
> >
> > Yes, I tried that but word-wrap made a right untidy mess of the paste
and I
> > wasn't sure if the post would be the same.
> >
> > Alf
>
> I used to have that problem too but now I just set my line length to about
> 100 characters and never have the problem anymore.
>
> --
> 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

From: Alf Peake
Subject: Re: Trace timer problem
Date: 26 Nov 1999 17:52:35
Message: <383f0f33@news.povray.org>
I find it usefull for adjusting AA or checking where the trace is sticking,
altho' 1 pixel/sec isn't too common these days with my new Celeron 500 :)))
Beats a 386SX-20

Alf

http://www.peake42.freeserve.co.uk
http://ourworld.compuserve.com/homepages/Alf_Peake/


Gerald K. Dobiasovsky <ger### [at] aonat> wrote in message
news:383c66f5@news.povray.org...
> I've never stumbled upon this bug, because I don't use the preview
> display under DOS (always staring at the statistics output instead ;)).
>
> --
> Gerald
> ger### [at] aonat
>
>
>


Post a reply to this message

From: Peter Popov
Subject: Re: Trace timer problem
Date: 26 Nov 1999 18:18:55
Message: <dxI=OOGnrReiGlDw4MeCEZnrYiyn@4ax.com>
On Thu, 25 Nov 1999 22:24:52 -0000, "Alf Peake"
<alf### [at] peake42freeservecouk> wrote:

>I see your post in bugreports so guess no need for me to do anything else?
>
>Alf

You may have noticed that the other 3 bugreports that I posted have in
the subject line the name of the user who initially spotted the bug.
Yours does not, for which I sincerely apologize. I sent a corrected
version immediately after that, but the way the moderation of
.bugreports works I don't think I could cancel the first one, and Alan
decided to let the first one through (probably thought that I have
sent the same message twice, ot seeing it appear in the message pane
immediately :) ). Proper credit is given in the post, though.

Seeing that it has actually made its way to .bugreports, there's not
much left to be done that fixing it :) If you have the time and
skills, that would be great. If not, the best thing to do would be to
KEEP ON TRACING :)))

See you around (and hopefully in p.b.i.)


Peter Popov
pet### [at] usanet
ICQ: 15002700


Post a reply to this message

From: Alf Peake
Subject: Re: Trace timer problem
Date: 27 Nov 1999 18:16:09
Message: <38406639@news.povray.org>
Peter Popov <pet### [at] usanet> wrote in message
news:dxI=OOGnrReiGlDw4MeCEZnrYiyn@4ax.com...
> On Thu, 25 Nov 1999 22:24:52 -0000, "Alf Peake"
> <alf### [at] peake42freeservecouk> wrote:
>
> >I see your post in bugreports so guess no need for me to do anything
else?
> >
> >Alf
>
> You may have noticed that the other 3 bugreports that I posted have in
> the subject line the name of the user who initially spotted the bug.
> Yours does not, for which I sincerely apologize. I sent a corrected

Not a problem Peter, glad to have helped.

> version immediately after that, but the way the moderation of
> .bugreports works I don't think I could cancel the first one, and Alan
> decided to let the first one through (probably thought that I have
> sent the same message twice, ot seeing it appear in the message pane
> immediately :) ). Proper credit is given in the post, though.
>
> Seeing that it has actually made its way to .bugreports, there's not
> much left to be done that fixing it :) If you have the time and
> skills, that would be great. If not, the best thing to do would be to

Never got further than the 6502, Z80 and basic so havn't a clue about the
innards of Povray :(

> KEEP ON TRACING :)))
>
> See you around (and hopefully in p.b.i.)
>
>
> Peter Popov
> pet### [at] usanet
> ICQ: 15002700


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.