|
![](/i/fill.gif) |
Mike8 nous apporta ses lumieres en ce 10/08/2006 17:42:
> Hello,
> I haven't posted before, so please bear with me. I've been using pov-ray
> for several months, and I have encountered a recurring problem. When I try
> to render any file larger than 6 Megabytes the renderer says 'parse error
> could not allocate 256 bytes for transform' and the render aborts. The
> largest file I need to render is 20MB. I am running POV-Ray 3.6 on Windows
> XP pro, with 1 Gigabyte of RAM, and I increased my virtual memory to 20GB,
> with no effect. Is there anything I can do or am doing wrong?
> Michael
>
>
>
By larger than 6Mb, do you mean the source file?
The source file takes some memory.
Any texture will take some more and image_map can take lots more. If you need to
apply the same image_map to several objects, it's probably better to define a
texture with it and use that texture. This ensure that you only have 1 instance
of the image file loaded.
Any file that you #include will also take some more memory.
Are there objects that are generated proceduraly? If so, how many? It's easy to
have some millions of objects that way.
Try rendering with the task manager open. How much does the process
"pvengine.exe" use? Maybe that during the parsing process you need more than the
maximum amount of memory that windows can allocate to a single process. If I
remember correctly, it's about 2 Gig, up to 3 with some tweaks.
Increasing your virtual memory to 20 Gb can't help, as the OS can't cope with
more than 4 Gb, the limit imposed by the 32 bits architecture, any more than 3
Gb is just a waste of disk space.
You can try rendering with the -d switch to suppress the render window and free
the memory it use. Usefull if you render very large images.
--
Alain
-------------------------------------------------
Error in operator: add beer
Post a reply to this message
|
![](/i/fill.gif) |