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