Have anyone had an out of memory error in P6? I was working on a figure today, had all the morphs I wanted, loaded mats, hair, etc and did a test render on her face. I decided to save before tweaking some more and got an out of memory error pop up with a suggestion that I save the scene. I have ample RAM, and I checked and Windows reported 443 megs of physical RAM free so I was surprised but I went and saved anyway - or tried to. Everytime I tried saving, either on same file or creating a new one I had the out of memory error pop up. I had saved not too long before the error so I didn't worry too much so I closed Poser, used a utility that I have to clear up my RAM and when I loaded the file again it was empty! I checked it in explorer and sure enough, the file was 0 bytes in size. Ugh! I didn't have a backup with another name :(. Anyone have that happen? Is there any solution for it? And on an unrelated note - is there a way to change the display of the message board so that topics with recent responses go to top - a "bumping" board so to say? I've been searching in my control options but can't find a way to do so...

Well - you aint Jonah.... Just do a search through the forums - you will find plenty of threads about the "memory wall"

Never ever ever save a scene after getting a "out of memory" message. Best try saving the figure with everything in the library instead. It is something CL is working on and knows about though. Also do a search for "fragmented" and see the thread on obj files. It can partly explain what you ran into if you were rendering alot.

Thanks guys - plugging "memory wall" and "fragmented" into search has yielded lots to read about it. Darn - first time I run into this error though I've been using it for a while (preordered P6). Funny it also happened after I increased my RAM heh.

If it has happened after increasing your RAM you might want to look at your swap file size and reduce it.

looks at nickedshield's reply I wish I knew more about hardware.

I have 2 GB RAm, and I get the out of memory issue just doing a final render on the DAZ Troll, nothing else. But as others have said, CL is working on it.

I have my swap file set to system managed but I'll play with a few custom settings and see how it works, thanks for the suggestion.

@ byAnton, A short explanation of a swap file: In the early days before motherboards were capable of handling, plus windows, gigabytes of memory the swap file aka virtual memory was a place on the hard drive set up to fool windows into thinking it had more ram. I'm a little rusty on my current specs so I might be wrong on this but it's my understanding that windows only recognizes 2gig of memory.. ram and swap. The new windows 64 is supossed to up that. The old rule of thumb was to set the swap file 1-1x's the ram. That was fine when the ram was 128-512MB. So by maxing out the ram to 2gig the only real advantage is speed. The speed of the ram versus the spedd of the hard drive. Hope that helps a little.

still greek to me but I will have Merrilyn's husband Barry wak me trough it. Thanks!

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2243391

SR1 might squash the memory bug.

Or so one would hope.........

WooHoo!

man, I've NEVER had this popup, I get the render stopping mid way and the like (happened in P5 too), take a look in my gallery at my last two images, there complex! (especially the last one, with over 250 props, 2 figures, complete with armour and weapons! IBL, AO, and multiple other lights. not one memory error (except for renders cutting out) that last image went to over 2000mb of memory use when rendering! (so I split it into 3 parts to get it to complete the render, but it never bugged out on me I cant see why it happens to some and not others

Oddly enough, I have 1 gig of RAM and let Windows XP handle the virtual memory, don't try to force it into a fixed amount, and I have yet to have any "Out of Memory" problems with Poser 6. Maybe the people having the problems are trying too hard in messing around with their system.

You can try limiting the total of real and virtual (paged, swap, whatever you want to call it) to something less than 2GB total. E.g. 1GB real and 960MB virtual. It won't stop P6 wasting memory (even by P5 standards), but it might stop P6 failing quite so badly when it does deep six it's memory allocation. No version of Poser to date appears to be able to contain itself to the 2MB address limit imposed by Windows on all applications. Go over 2Gb in any version and the results vary, but they are all ultimately terminal. When it goes over 2Mb it'll be writing on memory allocated for other uses - presumably the 2Gb Windows reserves for each executing applciation for its own OS use - and things will go badly wrong. As to why P6 uses memory so badly relative to P5 - which itself was pretty bad versus P4/PP - check one of my recent posts (search on layingback) which links back to a post by WierdJuice than explained what he discovered.