 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Using V3.5 RC 5 under w2k on an athlon processor I get the following
exception. Can anyone suggest what might be the cause? -Jim
Time For Trace: 0 hours 13 minutes 15.0 seconds (795 seconds)
Total Time: 0 hours 13 minutes 17.0 seconds (797 seconds)
----------------------------------------------------------------------------
CPU time used: kernel 0.24 seconds, user 794.11 seconds, total 794.35
seconds
Render averaged 604.27 PPS over 480000 pixels
POV-Ray finished
Preset INI file is 'D:\PROGRAM FILES\POV-RAY FOR WINDOWS
V3.5\RENDERER\RES800.INI'.
Preset source file is 'D:\Program Files\POV-Ray for Windows
v3.5\include\grapes\grapestemglobe.pov'.
Rendering using command line '+ov10005 +a0.1 +h600 +w800 -gw +c'.
Persistence of Vision(tm) Ray Tracer Version 3.5.beta.RC5 win32 (.icl)
This is a time-limited beta test version. No re-distribution
of any sort is permitted.
Copyright 1991-2002 POV-Ray Team(tm)
This Windows version by Christopher J. Cason
Parsing Options
Input file: D:\Program Files\POV-Ray for Windows
v3.5\include\grapes\grapestemglobe.pov (compatible to version 3.5)
Remove bounds........On Split unions........Off
Library paths: D:\Program Files\POV-Ray for Windows v3.5\INCLUDE
D:\Program Files\POV-Ray for Windows v3.5\INCLUDE\GRAPES\GRAPES
D:\Program Files\POV-Ray for Windows v3.5\INCLUDE\GRAPES\GRAPES_UV
C:\WINNT\Fonts
Output Options
Image resolution 800 by 600 (rows 1 to 600, columns 1 to 800).
Output file: v10005.bmp, 24 bpp (system format)
Graphic display......On (type: 0, palette: 3, gamma: 2.2)
Mosaic preview......Off
CPU usage histogram.Off
Continued trace......On Allow interruption..Off Pause when done.....Off
Verbose messages.....On
Tracing Options
Quality: 9
Bounding boxes.......On Bounding threshold: 3
Light Buffer.........On Vista Buffer.........On Draw Vista Buffer...Off
Antialiasing.........On (Method 1, Threshold 0.100, Depth 3, Jitter
1.00)
Animation Options
Clock value.... 0.000 (Animation off)
Redirecting Options
All Streams to console.........Off
Debug Stream to console.........On
Fatal Stream to console.........On
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console......Off
Scene contains 5 frame level objects; 1 infinite.
Returned from renderer due to access violation exception
POV-Ray finished
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Jim Charter" wrote:
> Using V3.5 RC 5 under w2k on an athlon processor I get the following
> exception. Can anyone suggest what might be the cause? -Jim
If the system is using NTFS, perhaps POVRay does not have permissions to
access/modify/view/etc. the source file or if this happens every render, one
of its own files.
If this is the case change the security settings on the related files to
slowly give System or User more permissions or just give Everybody full
permissions on the file.
N Shomber
WinXP Pro
Athlon 1500 XP
POVRay 3.5 RC5
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for the suggestion. I checked the scene files and they all have
open permission. Also, the render will run ok if I turn off
anti-aliasing, or eliminate most of the objects, or zoom the camera out
so that the objects only take up a small proportion of the image area.
So it would seen that the component files can all be accessed okay. The
scene consists of 15 mesh2 objects, 14 grapes and a grape stem. The
grapes stem is textured with a uv map, the grapes are textured with
media interiors. The stem renders okay by itself. The problems seem to
start when I specify anti-aliasing with too many objects or over too
much of the image area.
All other things being equal, how does specifying anti-aliasing increase
the demand on resources. I would have guessed it just requires more
computations. Does it require more memory?
N Shomber wrote:
> "Jim Charter" wrote:
>
>>Using V3.5 RC 5 under w2k on an athlon processor I get the following
>>exception. Can anyone suggest what might be the cause? -Jim
>>
>
> If the system is using NTFS, perhaps POVRay does not have permissions to
> access/modify/view/etc. the source file or if this happens every render, one
> of its own files.
>
> If this is the case change the security settings on the related files to
> slowly give System or User more permissions or just give Everybody full
> permissions on the file.
>
> N Shomber
> WinXP Pro
> Athlon 1500 XP
> POVRay 3.5 RC5
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Charter wrote:
> Thanks for the suggestion. I checked the scene files and they all have
> open permission. Also, the render will run ok if I turn off
> anti-aliasing, or eliminate most of the objects, or zoom the camera out
> so that the objects only take up a small proportion of the image area.
> So it would seen that the component files can all be accessed okay.
It may also be an access or size limited Windows Swap File. If you do not
have administrator permissions these settings cannot be changed. However,
if you do have admin privelages, Right click My Computer. Click Properties.
Go to the Advanced tab and select Performance Options. By clicking Change,
you can set new size limits for Windows memory paging or swapping.
At least in Win98, a search for a file named "*.swp" on the local hard
drives will result with one large file. This is the swap file. **Be
careful** You may check its permissions, but whatever you do, do not leave
it open long, nor change or delete it.
> The
> scene consists of 15 mesh2 objects, 14 grapes and a grape stem. The
> grapes stem is textured with a uv map, the grapes are textured with
> media interiors. The stem renders okay by itself. The problems seem to
> start when I specify anti-aliasing with too many objects or over too
> much of the image area.
(See Docs 5.2.6.4 Anti-Aliasing Options)
Depending on which method is being used, Anti-aliasing is based on either
contrast between pixels or within them. If mode 2 is used, each grape or
object or whatever will increase pixel contrast. This will cause more need
for the actual aa algrithms.
> All other things being equal, how does specifying anti-aliasing increase
> the demand on resources. I would have guessed it just requires more
> computations. Does it require more memory?
It will require more memory because each super-sampled pixel would be
preserved so that future neighboring pixels don't need to re-shoot that that
location. Storing this may significantly increase memory usage. (perhaps 4x
or more!)
N Shomber
WinXP Pro
WinPOV 3.5 RC5
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I now strongly suspect the swap file, thanks for your help!
>
> It may also be an access or size limited Windows Swap File. If you do not
> have administrator permissions these settings cannot be changed. However,
> if you do have admin privelages, Right click My Computer. Click Properties.
> Go to the Advanced tab and select Performance Options. By clicking Change,
> you can set new size limits for Windows memory paging or swapping.
>
>
> It will require more memory because each super-sampled pixel would be
> preserved so that future neighboring pixels don't need to re-shoot that that
> location. Storing this may significantly increase memory usage. (perhaps 4x
> or more!)
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
