 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When I try to open my large file (337 MB) I get a -5000 error message saying
the file can't be used. When I click "OK", the window closes and POV_Ray
starts parsing tokens. This goes on for a bit more than five minutes,
parsing about 410000K tokens. Then the render stalls for a couple of
minutes, and after a while the render status bar read "Relclaiming memory".
After another minute, the "Out of memory" error menitoned in my previous
message appearrs on the Message window and the render shuts down.
This happens when I have nothing other than POV-Ray open. Can I fix this in
some way, or is the file just too big for the amount of RAM I have on my G5
(1.5 GB)?
Thanks,
Greg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sounds to me like the scene just contains more objects than your computer
can handle. Where did you get this scene from? What sort of objects does it
contain?
- Slime
[ http://www.slimeland.com/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think you're right. It's a POV export of a protein data bank file from DS
Visualizer by Accelrys. There are a couple of spheres and a few thousand
colored_smooth_triangles. The export function from Visualizer is usually
very clean. I adjust the camera position, paste in a standard three light
set up, and render away. It works fine for smaller files, but this is a
very large protein.
I think I need to work on this problem from the Visualizer end. I may be
able to cut the file size down by changing some of the parameters for
working up the pdb file.
Greg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Greg Williams wrote:
> When I try to open my large file (337 MB) I get a -5000 error message saying
> the file can't be used.
Either the file is locked or you do not have the necessary permissions to
write to that file. As such, POV-Ray fails to store your preferences along
with the file, which it tries to do before every render.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> Either the file is locked or you do not have the necessary permissions to
> write to that file. As such, POV-Ray fails to store your preferences along
> with the file, which it tries to do before every render.
>
Thakns you!
Can you tell me where in the documentation I can read about this? I'ver
scrolled through the TOC several times, and read some the places that
looked like they might be appropriate, but I haven't been able to find the
right section.
I didn't do anything with this file that I haven't also done with quite a
few others, so I don't think this is a problem with the Visualizer export
function.
Greg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Greg Williams wrote:
> Can you tell me where in the documentation I can read about this?
The POV-Ray documentation won't tell you. Locking files and file permissions
are handled by the operating system.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hmm...then that isn't problem. I did check this with the Get Info command
for the file. It's not locked, and I do have permission. I am the only user
of the computer and have no access restrictions in place.
>
> The POV-Ray documentation won't tell you. Locking files and file permissions
> are handled by the operating system.
>
> Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wait! I did make a discovery about the access issue. For some reason, for
this file, I had read but not write privileges, so I couldn't change the
file structure. I don't know why this one file was different from any of my
others, but for some reason, it was different nonetheless.
I gave my self access to write, and the -5000 error did indeed go away.
Excellent! Thank you, very much.
However, that doesn't solve the memory error problem. I still get:
Parse Error: Out of memory. Cannot allocate 272 bytes for pattern
transform.
File Ca2+Surface.pov line 4827160
This doesn't seem to have anything to do with POV-Ray, however, so I'll stop
pestering about it. I'll work on the Visualizer end to decrease the file
size, if possible.
Thanks again for the help.
Greg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I too have had memory problems, both under MacOS X and Windows. In fact, I
actually had a render abort with an 'out of memory' error after about 70%
completion, which I've never seen before! Luckily I was able to switch off
some scene elements that had already been rendered and restart the trace
with the +C switch.
I am a little confused though - I thought POV-Ray used virtual memory when
it runs out of physical RAM. In which case, it should merely slow down
instead of aborting or crashing...
The only way to solve such issues as far as I can tell is just to be as
efficient as possible with code and objects :(
Bill
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I tried both Mac and WIndows, and neither was able to finish the job.
Neither one of them is a whimpy computer, either. I was able to go back to
the source program, and remove enough scene elements to cut the file size
from about 335 MB to about 250, and that has worked for me. So I'm
narrowing in on the limits of what POV-Ray can handle on my computers.
Greg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
