I've been working on a project for some time.  And, over time it seems the scenes I am working with are taking longer to open. I noticed today that after a CLOTH room simulation crashed due to memory - I checked on the task manager and noticed that the amount of memory allocated to a scene with nothing but one figure was over 300 meg.  I think the crash was a fluke but I don't remember in the past scenes taking so much memory.

I remember checking this form time to time and I swear that a one figure scene would generally boot up and while idle be under 200 Meg in allocation.

Can anyone tell me what the memory allocation is when Poser boots to the preferred state with no figures or content?  I am running Win 7 64 bit Poser 2012. This could be a virus but am unsure.  I do have the SR2 update installed for 2012.  Mine with ol' Andy in there is at 311 meg. Seems high to me.

My renders don't seem to be taking any longer but the memory being allocated to the executable is enormous.   What role do textures and material shaders play in this? 

Thanks.

There is a 3.1 update for PP12/Poser 9. Not sure if that's your problem, but you're missing an update or two ;). Every scene, when opened, caches texture files, so (it's been my experience anyway) that the longer you have Poser open, the more you change things (like textures), the more different scenes you open, the slower it gets. I just save and close and reopen every so often ;).

Laurie

That goes the same for rendering after scene manipulations.  How much RAM memory do you have?

How many levels of undo are in the general prefs.  The default is 100.  If you are having memory issues, try lowering the default number of undo's. also periodically open the general prefs and clear the undo cache.  Also lower the number of renders to have saved.  If you have been changing textures, you might want to save the scene, close Poser and even reboot the system. 

8 Gig RAM which should be plenty for what I am doing.  But what I can't figure out is why a scene with NOTHING in it gets over 300 meg alllocated to the executable. If this is correct then it must be the textures I have added.  I would like to know what other see when they boot Poser up with nothing in it.

I have the 3.2 update for PP 2012. It's installed.

FWIW, I only have 6 gigs of ram and I am not having the problems you are having. Sure, it gets slow after awhile of texture caching and rendering, but not like you describe.

Laurie

Hi there

I've 20GB installed and my largest scene can take up to 5GB RAM and when rendering I'm close to 9-10GB,but my scene consist from Stonemason scene and he using very large textures and plus other props from TrueForm like Bedroom and usually I'm using 2-3 V4 heavily morphed with SSS textures and what I've check'd usually textures are ranging from 2k to 4k and several clothing and hairs etc and due this my scene can take so much RAM,but on HDD is around 600-800MB,just shame Poser doesn't support instancing or some sort instancing,yes I know Game Dev have poly reduction

I've got 20GB RAM,but I think I will need soon upgrade to more RAM which means new MB and new CPU,8GB is OK,if you are not planning larger scenes,but I would upgrade to more RAM,RAM is not expensive there

Hope this help 

Thanks,Jura

     I can confirm that there was a SR3.1 for P9/Pro2012.  Among other things, I think it fixed the Internet Explorer 11 problem which a Windows update caused.

     Consider how many polygons the cloth has, and whether there is any intersection of cloth and doll.  Using a lower poly cloth prop and ensuring that there is no intersection of the cloth with the doll may make a dramatic difference.

     How much RAM is enough depends on your usage habits.  I often exceed 8GB.

Did you lower your undo levels and delete the undo cache?  When you say loading an empty scene takes 300 megs, is that a new scene being loaded after you have been working on another scene in the same session? 

Hi there

My Poser Pro will boot with preferred state and RAM reading is 213MB,with one V4 fully morphed and with clothing etc Poser RAM readings sit around 531MB

Thanks,Jura

This is all helpful.  It may be the Realskinshaders that I added to the figures in the scene.  Lots of nodes etc.  That would require more memory?  I suspect so.

Anyway, based upon the last comment - the fact that an empty scene boots up and is allocated 300 MG - doesn't seem unreasonable - although I swear I remember it being lower.  I did change the UNDO levels.

The scene that before would boot up at around 700 mg is now at 3.5 GIG due to 7 figures each with mulitple shader nodes now whereas before for example the faceroom skin only had one or two - now it has a dozen or so.  Funny thing is that the render is not all that slower but the memory allocated is pretty high now.

I don't believe that the complexity of shader nodes will affect memory particularly, unless those nodes are adding a whole bunch of textures that otherwise wouldn't be used.

In PP2014, my default scene (custom lights, skydome, and a primitive) uses 175 MB. However, after several hours of using Poser without rebooting it, that same scene will easily load using 400 MB. I often get scenes that use 2 GIGs just to view (and 8 GIGs to render). But if I close down Poser and reopen, the scene may have dropped to less than a GIG. 

Are there memory leak problems with Poser these days? OPs problem is familiar. The last two renders I have done have failed to complete because they reached the limit on my machine (16GB). Last render (long spear in the gallery) is just one figure and a background and that ran out of memory!

I would agree that shutting down Poser and rebooting it should get the memory back to what I would think would be more reasonable as you say.  But that is not working.  It's like there are cached files somewhere that I cannot clear.  Not sure where to look for this

Try opening up the general prefs.  Go to the tab that lists the undo levels.  There is a button the clear the cache.  Try clearing the cache to see if that is where the problems is. 

I did that already. And then I went to the texture cache and cleared that too.  An empty scene still opens up with over 300 meg allocated to the poser executable.  I am considering a re-install.  I just don't think that is right. 

I did that already. And then I went to the texture cache and cleared that too.  An empty scene still opens up with over 300 meg allocated to the poser executable.  I am considering a re-install.  I just don't think that is right. 

Yours Library are external or Embedded ? Because I'm using External there,Poser will boot up with 213MB,but if you will take External Library Process(LMGUIAIR.exe) taking 113-114MB at boot up,then Poser will take in total: +/- 326MB

And I forgot to add,I'm using Poser Pro 2014

Thanks,Jura

Libraries are EMBEDDED.  Yes I would expect the 213MB like you are seeing as well but it consistently boots up now with 310Mg + with NOTHING in the scene.  It's got a hold of something.  I just don't know what. I am pretty sure an uninstall / reinstall will correct it.  But, I wish I didn't have to do that. 

Libraries are EMBEDDED.  Yes I would expect the 213MB like you are seeing as well but it consistently boots up now with 310Mg + with NOTHING in the scene.  It's got a hold of something.  I just don't know what. I am pretty sure an uninstall / reinstall will correct it.  But, I wish I didn't have to do that. 

Hi there I've just tried to set my Libraries to embedded and my Poser Pro will boot up with 344MB 

Same like you I don't have nothing in scene,scene is empty etc

Thanks,Jura

Here is a little something to consider, and I just so happen to discover this by just experimenting.  Which viewing option are you using in your preview?  OpenGL or SreeD?  I discovered in PP2014 with an external Library that switching from SreeD to OpenGL increased memory consumption of the application alone.  On my system, a grand total of approximately 200mb on an empty scene jumped to nearly 245mb switching to from SreeD to OpenGL.  Interesting that a simple switch in feature would cause Poser to demand more memory.