'Our of Memory' Render problem

[Chrissyboy]

Hi fxgogo

What OS were you using? I don't know how to fix it for Windows, but for Macs the solution is to move to OSX.

Seeyou - C

[anobrin]

I agree !!
every big scene file that ever ran out of memory for me
In MAC OS9 has always rendered no problem MAC in OSX
:beer:

[fxgogo]

Unfortunately I am Windows 2000. I have the latest service pack installed as well. So a move to OSX is an impossibility for me. Thanks anyhow.

[AdamT]

Originally posted by fxgogo
Unfortunately I am Windows 2000. I have the latest service pack installed as well. So a move to OSX is an impossibility for me. Thanks anyhow.

I've had this problem in W2K too. Did you get a message saying your cache size was too small and needed to be adjusted? Anyone know how to set W2K so it adjusts the cache automatically? Any chance your scene exceeds the 2 gig limit of W2K. Did you know that W2K can only address 2 gigs of memory? So many questions....

[JIII]

For all those people who didn't know this. In mac os nine you must set the memory yourself. Click on the application then hit apple button I this will get info then click on memory then raise it to the roof. In OS X this is done automatically. This is why it didnt matter how much ram you put in your computer it still wouldnt increase your preformance unless you raised the programs allotment.

[flingster]

how do you know you didn't run out of memory?
how big is your page file set to?
any messages in event viewer?

page file cache settings are at:
control panel > system .system properties > advanced tab >performance settings >advanced tab > vitual memory

dunno if this will help...should be around there for win2000.
(rule of thumb i think its 3times size of ram..however if you got 1gig of ram then probably around 1.5gig page file...it can also help with file fragmentation if you actually fix the size of the page file rather than let windows handle it....this gradual fragmentation means that the system performance over time will deteriorate over time...and is just bad....hence running disk defragmentation is good....also windows in-built disk defragger is not the best route....however we are getting off the subject...back to memory....cache size....bit AdamT did you get anymore info....i presume page file cache...see above.

[fxgogo]

Ok, a lot of questions. I will do another render tonight and check the error message, if it pops up. My page file is set to 3gigs (using the same rule you mentioned), and it is a fixed size, so it can't be that. ....time passes....

I have just done some render tests, and with more than 45000 particles it uses up all my physical memory and gives an 'out of memory error'. That is a bit tooo many particles I know, but I wanted to find out what was doing it. So I have reduced the particle count and it should be fine. I will do multiple passes to get th effect I want.

Now what would be wanting so many particles you ask. Well I am doing a 'text into dust' effect, and I need all the particles to make up the text in the beginnning and look like proper text with no holes.

Oh, by the way Flingster, I looked in my event viewer to find loads of disk errors, which i did not know about. Thanks ;)

[flingster]

3 gigs sounds overkill...but then i did say 3xtimes!:wip:
anyways....you can also set performance alerts to keep track of mem usage (administrative tools)

what about other scene elements which effect memory usage...eg hard shadows, volumetrics,caustics, to name a few...i'm sure others with far more experience than me can give you some pointers.
come on boyz n gurlz....reasons for increasing memory usage in cinema are......:wavey:

[fxgogo]

Well the other elements should not take effect cause the material is fully luminous. I did not have lights in the scene. When I did a test with a compositing tag, it resulted in no time reduction. Anyway here is the result of my efforts. I will have a animation up shortly.

I have moved the picture to this thread so others not following this one can see it. Here is the link: http://www.cgtalk.com/showthread.php?s=&threadid=47997

[flingster]

nice stuff...animated sounds cool.
so how did you solve the mem issue?

[fxgogo]

Here is the animation:

http://www.slowlymakingsmoke.com/particles.mov

[kiwi]

Excellent :thumbsup:


Stu.

[fxgogo]

Originally posted by flingster
nice stuff...animated sounds cool.
so how did you solve the mem issue?

Well I basically reduced the amount of particles I used and render two passes with different seed numbers in the particle generators. I ended up having about 30 000 of them in the scene. I noticed in the task manager, that as the scene was preparing C4D would grab tons of ram, probably as it was working out and creating the particle field. Then once it fiinished rendering the frame, it would dump almost half a gig of memory, before moving onto the next frame and starting the whole process over again. It would be nice to have a system that allowed bucket rendering or some type of memory optimisation, but 30000 sphere in a scene is quite hectic.

[flingster]

good job...worth the extra effort and particles...to get the result.

bucket rendering i think would be nice to see in R9...i think its on the list being compiled on here...so i live in hope.
:thumbsup:

[AdamT]

Cool animation. I wonder if you couldn't have used Pyrocluster and fewer particles?

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.