Poser has got to be one of the worst programs ever, I have heard people experiencing the issue I am currently having even when they have enough memory on their machine. I mean seriously, is there any reason WHY I get these irritating ass messages such as "not enough memory" or "cant load texture file". Has anyone else experienced this problem? Its annoying. If there is a way I can fix that please help. Thank you. I mean if buying more memory will fix the issue, I guess thats what I'll do next time.

I used to get that with earlier versions of poser, but not once since poser pro 2012.

Love esther

If i load a scene with 9 fully dressed daz figures in a poser house, i eventually get a slowdown but no messages.

I've experienced this with Poser Pro 2012 with and without SR2 myself, it seems to be related to the external morph targets, as the out of memory message often comes with another message stating the PDM file could not be loaded.

I'm yet to file the bug, I'll try to point out the exact conditions under which the problem apears before doing so.

I love external morph targets, it makes the scene load and save SO much faster, but it can cause so many problems I'm starting to think it's not really worth using.

Oh I ALWAYS disable that feature routinely.  what a pity.

Quote - Poser has got to be one of the worst programs ever, I have heard people experiencing the issue I am currently having even when they have enough memory on their machine. I mean seriously, is there any reason WHY I get these irritating ass messages such as "not enough memory" or "cant load texture file". Has anyone else experienced this problem? Its annoying. If there is a way I can fix that please help. Thank you. I mean if buying more memory will fix the issue, I guess thats what I'll do next time.

Are you running Poser or Poser Pro?

If you are running Poser, it is 32-bit & you will have a 2Gb per process limit, regardless of the amount of memory you have installed. This isn't so much a Poser issue as it is a 32-bit issue.

PoserPro is 64-bit and should use all available memory.

I haven't had the Out of Memory issue since P2012Pro either, even running the 32bit version. Had it a lot in previous versions.

What I'd like to know is why Firefox (the latest version) is using up to 500Mb of memory for a damn web browser. That's rediculious!

Yep, used to get that message all the time with Poser 8.  It went away as soon as I moved to a 64 bit version (PP 2010).

My biggest problem was huge textures.  Most renders don`t need 4000 pixel image maps for shoes or or 1000 pixel maps for eyes, for example.  They can be scaled down, and it should help with some memory issues.  Aside from that, running the renderer in a separate process helps.

Dont blame Poser.  Running todays content on 32 bit versions of it is probably just too much for many scenes if you`re not willing to work very efficiently.

Well I am using Poser 7 and my machine is 64 Bit. I was considering upgrading to Poser Pro 2010 because I hear Poser 9 isn't 64 Capitable either. The thing is, I have this room that uses about 6 Million of the memory and then that message will show up on me. So you guys recommend that I upgrade or what?  Because I am planning on it. I can't afford Pro 2012...Its way too expensive right now. But Poser Pro 2010 seems just as good as Pro 2012.

Quote - Yep, used to get that message all the time with Poser 8.  It went away as soon as I moved to a 64 bit version (PP 2010).

My biggest problem was huge textures.  Most renders don`t need 4000 pixel image maps for shoes or or 1000 pixel maps for eyes, for example.  They can be scaled down, and it should help with some memory issues.  Aside from that, running the renderer in a separate process helps.

Dont blame Poser.  Running todays content on 32 bit versions of it is probably just too much for many scenes if you`re not willing to work very efficiently.

I will blame the program because regardless it shouldn't be doing that period. I mean I've used Maya on a lot of pcs it wasn't capable with and never got a single error issue at all and Maya doesn't  have new versions of the same program every single year either. Smith Micro just keeps upgrading year after year after year when they can just do what the makers of Maya does and create one that is superior than the rest until they can finally think of something  worth upgrading to. For instance. Poser 2012 has a good render engine yet it still sucks at Animating. I don't use large scenes either I always use small scenes. its not really the size of the scene in terms of structure since I have used  those sci fi rooms and they are HUGE in terms of how much you can put in them vs a few smaller rooms I have used and got that error and there were times when I would have my figures all nude and try to render them and still I get an error so I'm assuming it has a lot to do with how much went into the morphs, textures, etc. I only use Poser because its quicker or else I would be all over Maya if I knew how to use it. I mean hell I would gladly purchase Poser 2012 if it were cheaper to get and fixed all the problems but why do that when I can get Pro 2010 which is also 64 bit? Its only common sense that when you design a product you should keep in mind that not everyone will be using the same system so why not just create a version that works with all systems like Poser Pro 2010  and 2012. It took them up till Poser pro 2010 just to do this. If you ask me I just feel like Smith Micro is trying to rip people off with all these newer versions that rarely offer anything over the previous. Hence why I might just wait until they come out with a Poser 2013 or 2014 instead of grabbing Pro 2012 lol. There is a possibility. I only want whats best for my machine. And anything with limitations is crap by my standards.

I'm ok. Winxp 32 bit...No probllem with memory...Get it alot with Daz though. I have to reboot and try again. Reason I always save save save alot.

Quote - > Quote - Yep, used to get that message all the time with Poser 8.  It went away as soon as I moved to a 64 bit version (PP 2010).

My biggest problem was huge textures.  Most renders don`t need 4000 pixel image maps for shoes or or 1000 pixel maps for eyes, for example.  They can be scaled down, and it should help with some memory issues.  Aside from that, running the renderer in a separate process helps.

Dont blame Poser.  Running todays content on 32 bit versions of it is probably just too much for many scenes if you`re not willing to work very efficiently.

I will blame the program because regardless it shouldn't be doing that period. I mean I've used Maya on a lot of pcs it wasn't capable with and never got a single error issue at all and Maya doesn't  have new versions of the same program every single year either. Smith Micro just keeps upgrading year after year after year when they can just do what the makers of Maya does and create one that is superior than the rest until they can finally think of something  worth upgrading to. For instance. Poser 2012 has a good render engine yet it still sucks at Animating. I don't use large scenes either I always use small scenes. its not really the size of the scene in terms of structure since I have used  those sci fi rooms and they are HUGE in terms of how much you can put in them vs a few smaller rooms I have used and got that error and there were times when I would have my figures all nude and try to render them and still I get an error so I'm assuming it has a lot to do with how much went into the morphs, textures, etc. I only use Poser because its quicker or else I would be all over Maya if I knew how to use it. I mean hell I would gladly purchase Poser 2012 if it were cheaper to get and fixed all the problems but why do that when I can get Pro 2010 which is also 64 bit? Its only common sense that when you design a product you should keep in mind that not everyone will be using the same system so why not just create a version that works with all systems like Poser Pro 2010  and 2012. It took them up till Poser pro 2010 just to do this. If you ask me I just feel like Smith Micro is trying to rip people off with all these newer versions that rarely offer anything over the previous. Hence why I might just wait until they come out with a Poser 2013 or 2014 instead of grabbing Pro 2012 lol. There is a possibility. I only want whats best for my machine. And anything with limitations is crap by my standards.

Sounds like you don't like Poser at all. So by all means, use Maya. 

What's happening, by the sounds of it, is you're trying to do something that exceeds the limits of your version / machine, etc, and in fact the program is apparently handling that state of excession and telling you, within reason, what the problem is...?

In my book, as a program behaviour, that's fair enough.

This is quite an old version of Poser you're using now too...

Sure, I'd hope that Maya would also effectively handle such error conditions and tell you what the matter is... certainly for the kind of money it retails at.

But its worth noting that some programs, including some very expensive high-end programs, will simply crash out altogether and exit, without managing to do any kind of error handling, when there is a memory excession issue like this...

I've never used a version of Poser prior to Poser 9 (I've now sidegraded to Pro 2012) and I've never experienced this issue (even on my previous Core 2 Duo, 4GB RAM machine).

As I understand it there is quite a lot of new stuff in Poser 9/2012, over Poser 8/2010... featurewise.

But there will also be substantially more, I suspect, in the way of performance and stability enhancements... which seems to be what your core concern is here?

Cheers ;-)

Quote - I will blame the program because regardless it shouldn't be doing that period. I mean I've used Maya on a lot of pcs it wasn't capable with and never got a single error issue at all and Maya doesn't  have new versions of the same program every single year either. Smith Micro just keeps upgrading year after year after year when they can just do what the makers of Maya does and create......

There have been 5 releases of Maya in the last 4 years and 21 in the last 14 years.  Whether it is the same program or not is subjective.

You can find release history at http://www.toxik.sk/maya-startup-window-history/

You don't mention if the crash comes at render time or not. I suspect it does. If this is the case, PP2010 MAY help. PP2010 is not a 64 bit program. It is still 32 bit. However, the firefly renderer IS 64 bit in that version, so if you render as a separate process, you can get the advantages of extra memory. 

My own advice is to have at least 8Gigs in your machine. Since I've gone to 2012 and full 64-bit support, I've noticed that my renders can use up to about 5 gigs of memory at render time. That's telling me that the process was very crowded when it was all forced into the 2 Gig limit that the 32-bit process dictated.

As to your other issues, it is your choice whether to use Poser or not. If you decide to do so, we'll try to help. If not, Daz Studio is free. You might have better luck with that software.

don't forget out of memory is also the default error.. the one poser falls back on if it can't work something out, even if it's not ram related....

Quote - don't forget out of memory is also the default error.. the one poser falls back on if it can't work something out, even if it's not ram related....

Now THAT is behavior that I think needs to be changed. I wonder if anyone has ever asked SM to change the default to something like "An unknown error has occurred." It WOULD help in troubleshooting.

Interesting point Khai-J-Bach... yup, BasicWiz's suggestion would be a good one in that case!

Out of interest, Cyberdene, you've said you're running on a 64 bit system... but what actual machine spec are you running on, in terms of processor and memory?

Cheers ;-)

Quote - don't forget out of memory is also the default error.. the one poser falls back on if it can't work something out, even if it's not ram related....

See, that makes a lot of sense, since I've gotten that error with only a couple of characters loaded, and I have 12Gb of ram installed on a 64 bits system.

It's an old bug that never was fixed and has nothing to do with memory. One common source of this error is when Poser loads a figure or prop with external geometry and is unable to locate the associated obj file, then gives an "out of memory" message instead of telling that was unable to find "xxxxx.obj".

When Poser runs out of memory it gives no message, it only stop working or crash or its windows and dialogs begin to vanish and any other effect, but no "out of memory message". Probably you will need to restart the computer

The latests versions of Poser are supposed? to handle memory more efficiently (plug the holes) than previous versions. So the issue isn't/mightn't be just a 32/64 vs issue, or a Daz/Poser issue, but more a result of more/less memory efficient codes between versions. Or even perhaps achieving a sweet-spot with hardware components (graphics card/memory modules) that cooperate more efficently together.

I must be blessed when I say that Poser (4 thru to 2012) has generally been pretty rock solid for me if I use it sensibly and accept each versions limitations. If you want to hammer nails with a screwdriver, you have to expect problems.

Out of interest, you're using Maya but PP2012 is too expensive to upgrade to?

I would say it's certainly worth it to upgrade to PP2012. PP2012 is nothing compared to Maya price wise.

First thing first. What are your machine specs?

Quote - Poser has got to be one of the worst programs ever.

Seriously? I don't agree. I think it's superb for what it does.

What are your machine specs? What OS are you using?

Have you tried closing down unneeded processes? Do you multitask? Are you animating?

hi all,

check my signature: Missing Manuals. The site has now got two tutorials on handling resources issues. My Running out of Memory especially addresses 32bit programs, and as I still don't know whether Poser7 is LargeAddressAware, the provided tools may help to pump up the limit to 3Gb instead of the usual 2Gb limit. then: tell me, so I can help others as well.

In the meantime, I'm with Kawecki. As long as Poser can tell you anything, it's not out of memory. The moment it runs out, Windows pulls the plug immediately.

Note: since Poser costs 5 - 10% of Maya, and offers more than 5-10% of Maya, it has a better price / performance ratio. Just adjust your expectations, you get what you're paying for.

"and as I still don't know whether Poser7 is LargeAddressAware,"

it is. as is all the Poser Pro series (Poser Pro was 7 enhanced)

Thanks, I started checking from P8 up, that's why I don't know about 7.

So Poser7 and up will be able to address 3Gb user ram in a 64-bit environment. Not 2Gb. Still not enough for a full dressed crowd, but one can do decent scenes though.

Quote - Thanks, I started checking from P8 up, that's why I don't know about 7.

So Poser7 and up will be able to address 3Gb user ram in a 64-bit environment. Not 2Gb. Still not enough for a full dressed crowd, but one can do decent scenes though.

My P8 would sometimes quit on a render with one Vicky.  When you have a set of clothing (9 or 10 figures) and each clothing figure has several material zones each with 4000x4000 pixel image maps, plus the same sized specularity maps, plus displacement maps, plus reflection maps, plus bump maps...

Easy enough to fix, but a little time consuming.

Do you want make Poser out of memory?

Take some cr2 file and open with a text editor, for example Vicky4. You will find at the begining of the file

figureResFile :Runtime:Geometries:DAZPeople:blMilWom_v4b.obj

Replace this line by

figureResFile :Runtime:Geometries:DAZPeople:this one does not exist.obj

Then look forward in the cr2 file until you find again the same thing repeated. Replace the line again and save the cr2 with other name (to not destroy the original file).

Next open Poser and load this new created cr2 and see what happens with Poser.

Quote - In the meantime, I'm with Kawecki. As long as Poser can tell you anything, it's not out of memory. The moment it runs out, Windows pulls the plug immediately.

No, Windows won't. When a program tries to allocate more memory than is available to it, the allocation will return with an error code. The program can then respond to the error code.

The automatic bucket resizing in older Poser versions was built around that - when the system did not fulfill memory requests any more while rendering, the renderer would free all the memory that was used for the bucket so far, reduce the bucket size and do another attempt.

Quote - Do you want make Poser out of memory?

Take some cr2 file and open with a text editor, for example Vicky4. You will find at the begining of the file

figureResFile :Runtime:Geometries:DAZPeople:blMilWom_v4b.obj

Replace this line by

figureResFile :Runtime:Geometries:DAZPeople:this one does not exist.obj

Then look forward in the cr2 file until you find again the same thing repeated. Replace the line again and save the cr2 with other name (to not destroy the original file).

Next open Poser and load this new created cr2 and see what happens with Poser.

What version of Poser are you using on what OS? When I try that, I get a file dialog with the caption Please locate "this one does not exist.obj"

@Stewer: as long as the program communicates with Windows it's not out of memory yet, and the old (multi threaded) bucket rendering was apparently a neat process not using more than requested. The Windows message was an (negative) answer to the request.

The real thing happens when a program uses more than requested / allocated / granted. That's a "writing outside user area" error, triggered at the hardware level of your PC and fatal immediately for various good reasons. Recent OS versions, responding to that hardware trap, only kill the process instead of everything else too (the famous Blue Screen of Death).  
This apparently can happen during the (single threaded) Prepare to Render phase, when the memory usage goes two to fourfold.

But whatever, semantics.

Agree with the "can't find ..." remark, although Cyberdine is talking P7. But I can't remember having had that message at all, since Poser 1 that is.

Quote - @Stewer: as long as the program communicates with Windows it's not out of memory yet, and the old (multi threaded) bucket rendering was apparently a neat process not using more than requested. The Windows message was an (negative) answer to the request.

The real thing happens when a program uses more than requested / allocated / granted. That's a "writing outside user area" error, triggered at the hardware level of your PC and fatal immediately for various good reasons. Recent OS versions, responding to that hardware trap, only kill the process instead of everything else too (the famous Blue Screen of Death).  
This apparently can happen during the (single threaded) Prepare to Render phase, when the memory usage goes two to fourfold.

But whatever, semantics.

Agree with the "can't find ..." remark, although Cyberdine is talking P7. But I can't remember having had that message at all, since Poser 1 that is.

The "can't load texture" error used to happen with P8 quite frequently, though I think it may have been fixed in an update.

http://www.runtimedna.com/forum/showthread.php?46409-texture-errors-in-poser-8/page2

Quote - No, Windows won't. When a program tries to allocate more memory than is available to it, the allocation will return with an error code. The program can then respond to the error code.

This is the theory, but not always happens. The programm code can request a memory block, but the programmer forgot to chect if the returned handle was valid. Later the code will try to use this memory that does not exist and in some point Windows will crash.

Another case is more subtle. Let suppose that you have 500 Mb of still available memory (physicall + virtual) and the programm requests 490 Mb of memory so Windows will return a valid handle and the programm will be able to use it, but this only left 10 Mb of free memory. Windows also needs memory and if your program wants to open a dialog box or menu, Wndows will not have memory to do it, so the dialog box opens empty, the icons from your destok begin to vanish and in the end you will not able to do anything. Restart the computer or at least shut down your program with CTL-ALT-DEL.

Another case is more complicated. You have 2 GB of free memory (physical + virtual) the program request a block of 400 MB and this time the programm displays a message that there is not enough memory, why???, how is possible to not have memory if there are 2 GB of free memory. Well you have 2 GB of available memory, but the memory is so fragmented that there do not exist a continuous block of 400 MB of free memory. Restart the computer.