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