I am getting repeated out-of-memory problems in Poser 6 mid-way through compmosing a scene. The PZ3 file then gets corrupted to zero bytes. Hours of work gone. Curious Labs - this is no longer funny, considering it's software I paid for. How about you repay me for my time and effort lost in return ? I am getting really, really fed-up with this situation.

I agree this needs to be fixed STAT, but we are all very much warned. Suggestion when working in hard hat zone: make frequent incremental backups of your pz3, like jessie01.pz3, jessie02.pz3 etc. that way if you hit a corruption wall you do NOT lose hours and hours of work. Also, everyone is reporting that at the moment we should exit all the way out of Poser6 and back in again to blow out the memory problem. ::::: Opera :::::

Even with frequent saving, once you hit that sudden and very unexpected "Out Of Memory Error", the whole PZ3 file reverts to zero bytes - gone, all gone. Maybe need to save to different filenames at every save. Dunno. Situation sucks big time, for a commercialware.

Yes, different file names each save, as I proposed, and exiting each time you do so (not 'save as'). During hard hat time... ::::: Opera :::::

Yeah I've lost several scenes this way, seemed to happen when I added multiple figures. I agree, needs sorting out.

And according to the EULA, there's not a damn thing you can do about it. Not even if it reduces your entire system to slag. Happy thoughts!

Yes, I agree that the memory bug is a major issue.

Hopefully CL will quickly get out a service release to address the problem.

In the meantime, Opera's suggestion of saving incremental versions of your scene will do the job. It's irritating to have to interrupt your workflow that way -- but it sure beats having to do it all over again!

Com'on, CL -- this is a GREAT app. Please don't let one flaw like this spoil it for some.

The sooner that we see that service release, the better.

Unless the service pack is rushed and contains more problems, then it isn't better. I'd rather wait a few weeks and suffer than get a fix that'll have me screaming even more.

What are you guys creating to get the whole thing crashing anyway? My largest scene until now had 14 people in it (6xM1, 6xV1, 1xP4man and 1xDon) All of them with head & Body textures (except for the P4 man). All the figures fully clothed with high res textures on the clothes and the P4 & Don both had a full knight armor on. Besides that there was the P4 horse with armor and DAZ Charger with spline bender armor. Also I had a microcosm textured ground tile, some rocks, fences, flags, a number of weapons and a fully textured battle tent. No crashes in working on scene at all. Poser 6 still responds quite well. Only problem is that I can't render the scene at all, but knew about that problem already. Fyi, I've got 1Gb of Phys Ram in my machine.

"And according to the EULA, there's not a damn thing you can do about it. Not even if it reduces your entire system to slag." You have no comsumer's rights there? Consumer rights overrides any EULA!

FYI: I don't care WHAT program I'm working in, I always do incremental saves. Poser, Max, PhotoShop... Any of them. It's never a good idea to drive a car without a spare tire. :)

It's never a good idea to drive a car without a spare tire. :) True.....but when it comes to computers, it's usually a good idea to carry around about a dozen or so spare tires. And a spare car, for that matter.

and some oil, a transmition and 3 or 4 brake calipers. :)

No crashes in working on scene at all. Poser 6 still responds quite well. Only problem is that I can't render the scene at all, but knew about that problem already.

So far, the only time that I've experienced a crash is during an attempted render. Some others are reporting crashes while working on the file itself -- not during a render.

The "crash" consists of an out-of-memory warning dialog, followed by a corrupted file. The program itself doesn't come down, but the file gets messed up. Missing textures, etc.

A back-up copy is a great idea.

I've been able to recover from the problem by exiting Poser, and then re-opening the file. After this, I was able to render the scene with no problem.

In a case like this, no one can really explain why some individuals have problems like this, while others don't. There are simply too many variables involved. Differing hardware setups, differing software configurations on individual systems, not to mention differing operating systems.

One cannot always point at something specific, and say "this is it!".

BTW - the memory bug affects those that it affects regardless of how much system RAM they have. It eats up all of the physical memory, and then it instantly goes down as soon as it uses up the available supply.

I fixed that problem with mine. Under Manual, I have the texture set at maximum, and bucket set at like 64 and it renders just like fire fly, with no memory problems so far.

Message edited on: 04/05/2005 15:23

and it renders just like fire fly With IBL AO? I'd like to see that happen in Poser 4.

Re edited it, sorry, it was a typo.

Cool. ;-)

The only crash that I've had so far was when trying to save the scene while in the Material Room. Didn't seem to like that very much for some reason. Otherwise, no difficulties.

Have any of you tried the fix posted at Curious Labs? The suggestion is to turn down hardware acceleration by a setting or two! I've tried this but have not had much Poser time since so I can't be certain whether it's worked! Fingers crossed - Curious Labs describes this as a suprisingly simple fix if I remember correctly and if it works it certainly is!!! The fix can be found on Curious Labs Poser 6 support page (it's about the only thing on there)

For me, I have done as CL suggested, and it helped the software load completely, that's about it. My problems are related to getting it to operate without suddenly going comatose on me. It's behaving like a terrorist - I never know when I'm going to get hit. Yes, yes... I'm taking precautions such as saving extermely often into new files, and wasting a lot of time exiting and re-launching etc,etc. Nice piece of work, this new commercialware. I apologise to all of you for my bad temper. I'm not normally like this.

You may want to turn off some of the background things windoze has running, that will free up more memory. Remember, everything you have running in the background or a non active window eats up memory so the less running the more you have for Poser. :-)