I keep getting “memory allocation error, probably due to insufficient memory”. I have 2 gigs of Ram, now does this possibly have to do with setting up memory allocation (somewhat like a scratch disk)? If so where can I adjust the memory? I am trying to render about 4000 frames with some particle/metaball with some simple geometry.

thanks

Windows I assume?

No, there's no scratch disk to setup…Did you monitor your memory as it was rendering? Was it constantly climbing? Without more detail, it's hard to make a suggestion, but it certainly seems like that's the problem. In theory it shouldn't, unless your data is constantly increasing. Since you're using windows, and XP I'll bet, there is one thing I know about although not through Houdini - the management of the swap file is awful in XP(a *little* better in 2000). Essentially, windows tries to be “smart” about it's usage, and if a given app is running for a long time(which I suspect 4000 frames qualifies ), it starts swapping out stuff. Not sure if that's related at all.

Workaround? Do it in chunks. Even better, use a script that renders it in 300 frame chunks - that way you don't need to be there. That'll be your best bet.

Cheers,

J.C.

Totally agree with JC there. In a textport, type: help viewwrite
This will allow you to do flipbooks directly to disk. Make sure your textport is not covering your viewer when you do it though.

thanks for great info. the render is merely to test the camera moves and fx, not final render. just dropping the image rez to 75% in flipbook setup seems to render ok. but i think doing things in chunks makes sense. someone also mentioned rendering different components (objects and fx animation) separately and compositing in COPs. though i haven't played around with COPs much yet.

jcoldrick, you are correct. i am using XP Pro, and now i know why people keep bringing up issues about swap files! :roll: