How do I make the'tweaks' to the system's virtual memory?

> Personaly, I don't know, other than setting it's total volume. Other peoples
> have mentioned it.

I created the model in a 3D CAD program called MLCad and converted it to POV
format with another called L3P. This works very well on smaller files, but I
have hit a celing at 4.5MB. So I don't know very much about the code
contained within the file itself, only that the 4.5MB file has over 10,000
lines of code, many of which seem to repeat themselves. This would be a
mess to streamline, so fixing my memory capacity is the only practical
solution I can think of. Any more advice you may have would be greatly
appreciated!
Thanks,
  Michael

Post a reply to this message

"Mike8" <nomail@nomail> wrote in message 
news:web.44dba7fbd8ca351dbca05e450@news.povray.org...
> 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?

   Hi Michael

     I may be wrong here, (it's a long shot), so please forgive me if I am, 
but it's worth a try as I too have had problems with a 1 gig system whereby 
I can't open one of my favourite image editing programs unless I do this. 
When you go into your VM dialogue box in Control Panel, use the 'Custom 
size' option and enter in the 'Initial size' field: 2024.

   In the 'Maximum size' field, enter: 4048 and restart your comp.

   Again, not sure if it will work, but anyway, good luck.

    ~Steve~






>  Michael
>
>
>

Post a reply to this message

"St." <dot### [at] dotcom> wrote:
>
>    Hi Michael
>
>      I may be wrong here, (it's a long shot), so please forgive me if I am,
> but it's worth a try as I too have had problems with a 1 gig system whereby
> I can't open one of my favourite image editing programs unless I do this.
> When you go into your VM dialogue box in Control Panel, use the 'Custom
> size' option and enter in the 'Initial size' field: 2024.
>
>    In the 'Maximum size' field, enter: 4048 and restart your comp.
>
>    Again, not sure if it will work, but anyway, good luck.
>
>     ~Steve~

No effect. Thanks anyway, it was worth a shot. I wish to correct an
inaccurate statement that I made earlier: the file I'm having trouble with
isn't 10,000 lines of code, it's 235,225 lines. That might make a slight
difference.
Thanks again,
   Michael

Post a reply to this message

"Mike8" <nomail@nomail> wrote in message 
news:web.44df727e3fb029bebca05e450@news.povray.org...
> "St." <dot### [at] dotcom> wrote:
>>
>>    Hi Michael
>>
>>      I may be wrong here, (it's a long shot), so please forgive me if I 
>> am,
>> but it's worth a try as I too have had problems with a 1 gig system 
>> whereby
>> I can't open one of my favourite image editing programs unless I do this.
>> When you go into your VM dialogue box in Control Panel, use the 'Custom
>> size' option and enter in the 'Initial size' field: 2024.
>>
>>    In the 'Maximum size' field, enter: 4048 and restart your comp.
>>
>>    Again, not sure if it will work, but anyway, good luck.
>>
>>     ~Steve~
>
> No effect. Thanks anyway, it was worth a shot. I wish to correct an
> inaccurate statement that I made earlier: the file I'm having trouble with
> isn't 10,000 lines of code, it's 235,225 lines. That might make a slight
> difference.

      Gah, sorry. It works for me with my editing prog. but then I have to 
change it back again to play Oblivion...  :(

   As an aside, I remember asking if PoV could handle large files some 
four/five years ago, (3.1g?), and I received the answer that, yes, PoV could 
easily handle a 100Mb's file. Back then, I was using sPatch frequently, and 
a 'heavy' sPatch file (for me) could easily have been over 4.5Mb's. I think, 
(back then), that I only had 256Mb memory, and I could still render an 
image. So, I'm thinking that maybe something is wrong with the way that one 
(or maybe two), of the programs that you've used are at fault?

     Have you tried to start from the beginning again?

    I'm intrigued and fascinated at what you are trying to achieve with 
235,000 lines of code and want to see the result/s!  ;o)

     Again, good luck.

     ~Steve~

Post a reply to this message

>    As an aside, I remember asking if PoV could handle large files some
> four/five years ago, (3.1g?), and I received the answer that, yes, PoV could
> easily handle a 100Mb's file. Back then, I was using sPatch frequently, and
> a 'heavy' sPatch file (for me) could easily have been over 4.5Mb's. I think,
> (back then), that I only had 256Mb memory, and I could still render an
> image. So, I'm thinking that maybe something is wrong with the way that one
> (or maybe two), of the programs that you've used are at fault?
>
>      Have you tried to start from the beginning again?

I tried this render on three different computers with POV-Ray version 3.1
and 3.6 several times. None of them has ever managed it, though, my most
powerful computer did render a 7MB file today, barely. (4.5 MB is the
largest file I've been able to render thus far, the file I'm trying for is
about 8.5 MB.) I even stripped away some elements of the model to reduce
it's size with no effect. I think it's because the file was created by
another program from a CAD program model.

>     I'm intrigued and fascinated at what you are trying to achieve with
> 235,000 lines of code and want to see the result/s!  ;o)
>
>      Again, good luck.
>
>      ~Steve~
If I get this thing working I'd be happy to send a pic, though I doubt it's
nearly as impressive as you think.
Thanks again,
   Michael

Post a reply to this message

Mike8 <nomail@nomail> wrote:
> I wish to correct an
> inaccurate statement that I made earlier: the file I'm having trouble with
> isn't 10,000 lines of code, it's 235,225 lines. That might make a slight
> difference.

  Note that the size of the .pov (or .inc) file isn't necessarily related
to how much memory POV-Ray will need to render the scene. It isn't even
related to how much memory POV-Ray will need to parse the file.

  The only case where a big file will consume memory is if you open it
in the winpov editor (in which case the editor will consume the memory.
naturally). If you don't open it in the winpov editor then the file by
itself doesn't consume memory.

  If the file has been automatically generated by some program then it
probably contains almost as many primitives as lines of code (or at least
a number of primitives directly proportional to the lines of code), in
which case the file size is somewhat indicative of how much memory
POV-Ray will need to render the scene.

  But take into account that file size is not *always* such an indicator.
It's perfectly possible to make a 500 bytes .pov file which will require
gigabytes of memory to render, as well as a 500MB .pov file which requires
just some kilobytes of memory to render.

-- 
                                                          - Warp

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
>   Note that the size of the .pov (or .inc) file isn't necessarily related
> to how much memory POV-Ray will need to render the scene. It isn't even
> related to how much memory POV-Ray will need to parse the file.
>
>   The only case where a big file will consume memory is if you open it
> in the winpov editor (in which case the editor will consume the memory.
> naturally). If you don't open it in the winpov editor then the file by
> itself doesn't consume memory.
>
>   If the file has been automatically generated by some program then it
> probably contains almost as many primitives as lines of code (or at least
> a number of primitives directly proportional to the lines of code), in
> which case the file size is somewhat indicative of how much memory
> POV-Ray will need to render the scene.
>
>   But take into account that file size is not *always* such an indicator.
> It's perfectly possible to make a 500 bytes .pov file which will require
> gigabytes of memory to render, as well as a 500MB .pov file which requires
> just some kilobytes of memory to render.
>
> --
>                                                           - Warp

That is good to know, thanks. Still how can I render this file without
converting to a 64bit OS and motherboard??
Michael

Post a reply to this message

Mike8 <nomail@nomail> wrote:
> That is good to know, thanks. Still how can I render this file without
> converting to a 64bit OS and motherboard??

  I wonder if the linux version could render it...

-- 
                                                          - Warp

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
> Mike8 <nomail@nomail> wrote:
> > That is good to know, thanks. Still how can I render this file without
> > converting to a 64bit OS and motherboard??
>
>   I wonder if the linux version could render it...
>
> --
>                                                           - Warp

Is there ANY way that I can render this file without changing OS or
architecture? I just got a new computer, I can't afford another one just to
render images. What adjustments can I make to my system, or software should
I download, to increase the amount of virtual memory the OS allocates to
individual programs? I looked at Microsoft, but I couldn't find anything
that specifically addresses the virtual memory problem.
I really appreciate your help everyone, thanks for trying.
   Michael

Post a reply to this message

"Mike8" <nomail@nomail> wrote in message 
news:web.44e6a4f73fb029bee8eab8b00@news.povray.org...
> Warp <war### [at] tagpovrayorg> wrote:
>> Mike8 <nomail@nomail> wrote:
>> > That is good to know, thanks. Still how can I render this file without
>> > converting to a 64bit OS and motherboard??
>>
>>   I wonder if the linux version could render it...
>>
>> --
>>                                                           - Warp
>
> Is there ANY way that I can render this file without changing OS or
> architecture? I just got a new computer, I can't afford another one just 
> to
> render images. What adjustments can I make to my system, or software 
> should
> I download, to increase the amount of virtual memory the OS allocates to
> individual programs? I looked at Microsoft, but I couldn't find anything
> that specifically addresses the virtual memory problem.
> I really appreciate your help everyone, thanks for trying.
>   Michael

   Michael, is it possible that you could upload the 8+Mb file somewhere, 
and I'll see if it runs on my machine? I believe that I may have a similar 
system to yours, (at least, I hope so, (apart from XP Home)):

    Windows XP Home (5.1, Build 2600) SP2
    AMD Sempron(tm) Processor 2800+, 1.6GHz
     1024MB RAM
     Page File: 214MB used, 2734MB available

   Other than the above, I can only suggest a couple more things that you 
can try:

     Faulty memory? You could try Memtest: http://www.memtest86.com/

     Have you tried disabling all background services? (Although, this 
shouldn't really be a problem as I run fairly heavy files with all services 
running).

     Anyway, let me know if you upload the file and we'll see if it throws 
any errors here.

     ~Steve~

Post a reply to this message