I was surprised to find, while grouping a prop in poser. I find a message appear in front of me.."You are out of Memory". For a system I have with 2Gigs of Ram (DDr's PC3200's, dual channel at 400mhz), 160gb Hd (Primary), 80GB HD (Secondary), AMD XP 3200+ (2.2Ghz CPU), I get this message. Like WTH? All the grouping, work I was doing, is all lost have to redo.

Message edited on: 10/13/2005 09:55

How is your systems virtual memory setup? You might need to increase it.

Welcome to the club - I have virtually the same system. Doesn't seem to matter what you do with the paging files - it will still pop up from time to time (see the many threads here about it) I don't know if EF are ever going to address the issue....

join the club....yes I'm getting crazy with that..and to amke it wors the salesman from the shop where I brought the memories told that the happens because the Win XP 'dumps' the memory..and so I have to to re-instal WinXp to fix the problem...WTH...?every time I do have this problem? Pleeease..give me a better solution you super guys, super gods in computing..tell me something not so painfull. While making the virtual memory bigger does not affects...does it make any difference if I do buy a new graphic card? let's say..a Radeon X800 Pro PCI Express 256MB would it make any difference or not? anyone can tell anything about that? thanks

"Out of memory" is Poser's default error message. It (usually) has nothing to do with whatever caused the problem.

Poser uses a lot of stuff written by sub-contracted parties.

If any of these returns an error (for whatever reason) and the "error number" it returns isn't one that Poser recognises or can deal with, it resorts to reporting "out of memory".

And given all the legacy (ie. inherited) code I very much doubt that EF will address the issue.

I am a programmer. I know for a fact that handling errors in a user-friendly manner usually takes much more code than the actual code used for the module. You have to anticipate every possible place where things could go wrong, and add code at each point to check for that problem. Then you have to signal back to the "calling" function that "such-and-such" a problem occurred. The calling function then has to recognise that signal, and respond accordingly (and that's only 1 level of sub-calling).

And, of course, all this code takes up memory...

So there are many strategies for taking care of error reporting, ranging from the simplest ("lets just have a few error types, and try to shoehorn all the others into one of those few") to the most complex ("Let's deal with each error as fully as possible").

Poser chose the former.

And, given that Poser is a memory-hog in the 1st place, that was probably a wise decision...

Cheers,
Diolma

Message edited on: 10/13/2005 15:32

Well even if they shoehorn it diolma they really should have an "undefined error" rather than a "Out of Memory" one. Or do they have a contract to sell more memory?????!!!!

LOL @ Starmage.

Yes, they should have an "undefined error", but this has been a Poser thing that goes back as far as I can remember.

They should change it.

But there's probably several hundred (possibly several thousand) lines in the code that might need to be changed to catch them all. And that would cost money to find them all and correct them, and that would put the price of Poser up...

So, I'll just live with it.
@Robo2010: See my post #5. It is probably nothing to do with memory at all. It's much more likely to be a totally different problem. OTOH, How long have you had Poser open? Save the scene (under a NEW name). Quit Poser. Restart Poser. Load new scene. Poser has bad memory management. Memory fragmentation can often be an issue. When working with Poser, you need to save early and save often, with successive names (add a number, starting from 01 'cos you'll probably need more than 10 saves, and by starting from 01 they'll line up in sequence, to each save..). When all is done, then you can go back and delete all the unwanted ones..
Cheers,
Diolma

Message edited on: 10/13/2005 17:03

I doubt a change in video card will affect Poser - all it uses the card for is the open GL preview - so a super duper video card isn't going to help rendering or memory...