I am posting to this group because these are not POV-Ray core bugs but
rather ones of the windoze front-end

1) I am pretty sure this one's a bug. When using the rubberband select
to render a region, POV fails to free the system resource it takes. I
am not talking about program or data memory but about those 2x64 Kb
(thanks, Spider! :) ) that windoze allocates for icons, menus etc.
After about 15-25 renders the system goes really low of resources
(0-5% free). Closing and restarting POV solves the problem.

To replicate this bug try this. Open POV and a scene. Start a render
and stop it (so that the render window shows up). Now right click on
My Computer, select Properties and click on the Performance tab. See
the amount of free resources you have. Close this window now, you'll
open it later, because windoze doesn't update it automatically. Go
back to POV and use the rubberband to select a render region (I
haven't notices if its size matters, but the larger, the better,
methinks) Check the amount of system resources again. On my system
this procedure usually eats away 3-6 % of the resources.

2) I think this one has been mentioned before: when using adaptive
anti-aliasing, the pps indicator shows zero

System:
CPU: AMD K6/233
MB:  Intel Triton TX
RAM: 96 Mb SDRAM
OS : Windows 95 OSR 2.1, Windows 98
POV: Official POV-Ray for Windows v3.1e.watcom.win32.r1 (PII Opt.)


Peter Popov
ICQ: 15002700

Post a reply to this message

About 1), yep I'm always soft-crashing the program when I do many region selections in
a
row as I test a small area of a render for correctness and adjustments on a scene
file.
I just live with it and figure it's obvious enough for anyone to know about, esp.
Chris
Cason. Could be a limitation not figured out as of yet.
About 2), why did you tell me!? Now I will stare at that zero every time I render with
Sampling_Method=2 instead of 1, which I use quite often and never even noticed this
fact.


Peter Popov wrote:
> 
> I am posting to this group because these are not POV-Ray core bugs but
> rather ones of the windoze front-end
> 
> 1) I am pretty sure this one's a bug. When using the rubberband select
> to render a region, POV fails to free the system resource it takes. I
> am not talking about program or data memory but about those 2x64 Kb
> (thanks, Spider! :) ) that windoze allocates for icons, menus etc.
> After about 15-25 renders the system goes really low of resources
> (0-5% free). Closing and restarting POV solves the problem.
> 
> To replicate this bug try this. Open POV and a scene. Start a render
> and stop it (so that the render window shows up). Now right click on
> My Computer, select Properties and click on the Performance tab. See
> the amount of free resources you have. Close this window now, you'll
> open it later, because windoze doesn't update it automatically. Go
> back to POV and use the rubberband to select a render region (I
> haven't notices if its size matters, but the larger, the better,
> methinks) Check the amount of system resources again. On my system
> this procedure usually eats away 3-6 % of the resources.
> 
> 2) I think this one has been mentioned before: when using adaptive
> anti-aliasing, the pps indicator shows zero
> 
> System:
> CPU: AMD K6/233
> MB:  Intel Triton TX
> RAM: 96 Mb SDRAM
> OS : Windows 95 OSR 2.1, Windows 98
> POV: Official POV-Ray for Windows v3.1e.watcom.win32.r1 (PII Opt.)
> 
> Peter Popov
> ICQ: 15002700

-- 
 omniVERSE: beyond the universe
  http://members.aol.com/inversez/homepage.htm
 mailto://inversez@aol.com?Subject=PoV-News

Post a reply to this message

On Sun, 27 Jun 1999 07:14:56 GMT, pet### [at] usanet (Peter Popov)
wrote:

>I am posting to this group because these are not POV-Ray core bugs but
>rather ones of the windoze front-end

One actually is a core bug, believe it or not, but you don't have to 
post it to bugreports.  I've forwarded it.

>1) I am pretty sure this one's a bug. When using the rubberband select
>to render a region, POV fails to free the system resource it takes.

For those playing along at home, pvengine.c creates but does not
delete the pen it uses to draw the outline.  The longer you move
the mouse around, the more resources it uses.  

>2) I think this one has been mentioned before: when using adaptive
>anti-aliasing, the pps indicator shows zero

This one's in render.c.  Adaptive antialiasing doesn't call the
POV_PRE_PIXEL or POV_POST_PIXEL functions.

I've forwarded both of these with patches to the appropriate people.

Post a reply to this message

By the way, Peter, either your clock or your time zone is off by an
hour:

Date: Sun, 27 Jun 1999 07:14:56 GMT
X-Trace: 27 Jun 1999 02:14:29 -0400, 212.124.65.63

The way your clock is set, it looks like I fixed your bug ten minutes
before you posted it.

Post a reply to this message

Damn you're good...

-Mike

Ron Parker wrote:

> By the way, Peter, either your clock or your time zone is off by an
> hour:
>
> Date: Sun, 27 Jun 1999 07:14:56 GMT
> X-Trace: 27 Jun 1999 02:14:29 -0400, 212.124.65.63
>
> The way your clock is set, it looks like I fixed your bug ten minutes
> before you posted it.

Post a reply to this message

On Sun, 27 Jun 1999 07:19:23 GMT, par### [at] fwicom (Ron Parker) wrote:

>By the way, Peter, either your clock or your time zone is off by an
>hour:
>
>Date: Sun, 27 Jun 1999 07:14:56 GMT
>X-Trace: 27 Jun 1999 02:14:29 -0400, 212.124.65.63
>
>The way your clock is set, it looks like I fixed your bug ten minutes
>before you posted it.

Thanks for pointing this out, Ron. My clock is alright and my time
zone is alright (Sofija). It's just that the lamers that made windoze
98 (I upgraded yesterday) don't know where Sofia is and think it's at
GMT +01:00! Yeah, and they don't know how to spell it, too!

Problem is now fixed. I told windoze that I lived in Athens.


Peter Popov
ICQ: 15002700

Post a reply to this message

On Sun, 27 Jun 1999 07:04:46 GMT, par### [at] fwicom (Ron Parker) wrote:

<snip>
>This one's in render.c.  Adaptive antialiasing doesn't call the
>POV_PRE_PIXEL or POV_POST_PIXEL functions.

Does this mean that CPU usage histograms won't work either?

>I've forwarded both of these with patches to the appropriate people.

Thanks
Peter Popov
ICQ: 15002700

Post a reply to this message

Peter Popov wrote in message <3775ca8c.32616520@204.213.191.228>...
>I am posting to this group because these are not POV-Ray core bugs but
>rather ones of the windoze front-end
>
<snip 1 and 2>

Here's another

When selecting a region to render, if the region goes outside the image,
nothing will be rendered. Eg if my resolution is 512*384 and I try to select
a region
from 300-600*100-200 the picture will be all black

Machine 1:
P 150
64 MB ram
Win 95 OEM2

Machine 2:
P III 450
64 MB ram
Win 95 OEM2

Machine 3:
PII 233
64 MB ram
Win NT

Gail
*******************************************************************
* gsh### [at] monotixcoza              * ERROR: COFFEE.COM not found  *
* http://www.rucus.ru.ac.za/~gail/ * Insert cup and press any key *
*******************************************************************
   My Software never has bugs, It just develops random features
*******************************************************************

Post a reply to this message