I've not been on the forums in quite sometime thanks to school, and the like, but I'm getting back in to working with poser. Well... for starters here are my system specs: AMD 64 3200+ (oc'd to 2.4ghz) 2gb DDR 400 60gb HD 100gb HD 120gb SATA HD 8x Lite-On DVD+/-RW GeForce FX 6800 GT 256mb(PCIX) Audigy 2 sound card Asus A8N SLI Ultra Now. I can run max, maya, and cinema 4d all at the same(no rendering... I'd need an X-2 for that lol). But the minute that I fire up Poser, all hell breaks loose. For instance, I'm working with Stonemason's Urban Living, Urban Ruins, and Wusamah's Major Cache for a project for school. I merged my two commandos into the scene with the Urban Living and Urban Ruins models open. I go to save, and Poser says its out of memory. Taskmanager says its only taking 600mb of ram. I shut down Poser, restart the system, and boom, same damned thing. Is there a patch or something to fix this damned problem? I subscribe to the "new" e-frontier's newsletter, and have not seen mention of a service pack yet. WTF is with the former curious labs that they're not fixing these problems? As it stands right now, I have to export everything to OBJ format and then import it into Max or Maya. Which ain't fun. If yall have some ideas, or know of a patch, I'd be most appreciative. And no quips about getting more ram :). If the other programs on my computer can play nice with my Ram, Poser will be made to do so as well. Thanks all! and a shout out to bbratche, and everyone else that I know, but can't remember their names for the life me! Blade Wolf

There is an SR1 for poser 6 but I still get memory issues but not as many. There are mixed reports about SR1, some say P6 has been great since installing it with no further problems and then there are the others, like me that still get issues but nowhere near as many. Your specs are beter than mine by the way. [P4 3.4 GHz hyperthreaded, 1Gig RAM, X600 Radeon graphics]. thefixer, poser coord.

It's frustrating, sems to be on a machine to machine basis - I am at the stage of pulling my hair out the only way to find out the limits of the program is to try it - funny thing is it doesn't seem consistant. I've enen had it give the "can't find a texture or not enough memory" error but then go on to render the scene.

I get that one occaisionally. Me thinks that Curious Labs would do well to sell its programmers to MS... :) Anyways, I'll try SR1, and see if that works. If not, back to Poser 5 for me.

The solution may lie in Windows. Try increasing your paging file size. It can also be better if the paging file is on a different disk to the program.

will try that. I had to curb windows Pigsty of a paging file earlier. Damned thing was taking up almost 12gb of space. why can't MS make a DECENT OS???! goes over and kicks MS for good measure

Paging files are something I have never really gotten a full grasp on - can someone give us a good base figure to use as a starting point setting for paging files, as I thought I had read somewhere too large of a paging file can affect the computer as well as too little?

The minimum size setting is reccomended to be 1.5 times the amount of RAM you have. The maximum setting should be OK at 3 or 4 times the Ram size

And should one set a paging file for each drive?

Never tried that. I suspect that if you did Poser would use the one on its own drive.

Thanks for the advice - just found out you can only go to 4 gig max page file - will play around with the settings and see what happens

Makes no difference, already did all that!!!!

Poser has no control over the page file... Doesn't hurt to have a page file on each drive as windows then might choose the swapfile that's best at the moment (as not swapping to the same drive it's currently loading data from...) And it's not really Poser's fault when it can't handle scenes with textures that exceed the 2GB per application limit Win32 imposes.

there are some slight differences in how memory pages between different versions of windows; I don't see any reference to what you are using. General advice: reduce your paging file to the minimum setting (usually 2mb), reboot. you will get most likely a "insufficient virtual memory" warning, ignore. defrag the drive that the paging file is on. when complete, set the minimum swap file size to the same size as your physical memory (in your case, 2gb); set tyhe maximum size to 1.5 times your physical memory (in your case, 3GB). make sure your swap file is on your fastest physical drive. depending on your version of windows, in performance options set application response to background applications; this will slightly slow you down but increase your systems ability to handle things smoothly. Poser 4 had some issues with addressing memory addresses greater than 2gb, if I recall correctly; if your running multiple applications, try starting up poser first, it might make a difference. credentials: Systems Engineer since 1991, Poser user since Poser 2.

General poser advice Use Spankis S.T.O.M.P. to defragment objs & strip out extraneous groupings http://www.renderosity.com/messages.ez?Form.ShowMessage=2228908 Delete unnecessary textures, if a character has their mouth closed then you don't need inner mouth, teeth, gums & tongue to have any textures If a body part is hidden by clothing & has been made invisible make sure you delete textures applied to it For urban scenes parts that are obscured behind other parts should be stripped of textures All these textures that won't show up in the final render do nothing except chew up memory so get rid of them, reduce the memory footprint of the scene and reduce the pz3 filesize Oh and if you're using raytraced reflections ditch the reflection maps, they're for the luddites using obsolete 8 year old Poser 4

And don't forget that "out of memory" is Poser's "catch-all" error when it doesn't know how to report an error properly. So it may have nothing whatsoever to do with memory.
Or it can be caused by memory fragmentation (where the memory gets split up into lots of little bits, but none of them are large enough for the next bit of memory that Poser wants..) - the only cure for that is to exit Poser (save 1st if possible), which grabs all the memory that Poser was using, returns it to the operating system and coalesces it into a single lump, then restart Poser and load the last viable save..

Cheers,
Diolma

Message edited on: 10/15/2005 14:48