xenophonz and others have been calling attention to "the memory bug" since receiving Poser 6. I wonder, is this an umbrella term for a whole host of memory-related issues, or is it one specific sort of lock-up or crash? I've seen that xeno is having trouble getting complex scenes to render, that makes sense. Is that the only "memory bug," or are there others associated with other factors? For what it's worth, I have 1GB RAM, nVidia FX5500 v-card with 128MB memory, 7000MB virtual memory split beween two drives. I haven't had any lock-ups yet in P6, including scenes with one Millennium figure and lots of props, and another with two Mil figures and fewer props. Could it be that having virtual memory on a drive separate from the one that Poser and the OS are on makes a difference? Mostly I'm curious to know if the scene size issue is the main one that people are having with memory, or if there are more that "the memory bug" refers to. Thanks for any accounts.

As I've indicated in other threads on the topic, my own crashes occur upon attempting a render. The reason why I keep harping on this issue is to draw attention to it. The notorious MB severely limits the functionality of P6 for me.....and for many others. Squash the Memory Bug, and P6 will belong in the software Hall of Fame.

They are working on it. That's about all that one can expect or ask for.

For me this only seems to happen with a complex figure (Jessi) plus conforming clothing and the Winter Queen wings all loaded, then the render settings in the 'auto' window turned up as high as possible - i.e. the slider all the way to the right. Moving it one notch left kills the bug, but I suspect it would come back if another figure was added. The bug only appears when I try to render the scene, so it isn't an OpenGL problem, for example.
2Gb machine with nvidia GeForce FX 5600 XT with 128 Mb on board memory (I think).

it was good to see CL come through with the Content Service Release last night. We are all sure they are working on the technical patch. In addition to those like XENOPHONZ who actually pushed the release to the edge and discovered this general memory "leak"/"blockage", there are many like myself who have ordered and will install as this main problem gets solved. ::::: Opera :::::

BTW - lest anyone get the idea that this is something new......

I "fixed" the rendering problems in P5 by doing all of my Poser renders in Vue.

I can do that again with P6, I suppose. Vue Infinite is a truly great app for renders.

This is an issue that's been building over a long period of time with me.

I had high hopes that P6 would fix the native render difficulties. When I discovered that it didn't, I was just a little disappointed......

Thus, my "obsession" with the issue.

To mitigate this -- I trust CL to work it out.

They've done well so far.

Interesting spedler, I've only used the manual settings. I'll try auto at the highest settings. I sort of want to see this bug myself ... weird, I know. :-)

I sort of want to see this bug myself Try three or four mil figures, with clothes/hair/background props/buildings/etc.........

OK, I have see The Bug, and it is The Enemy. Way too easy to replicate. I loaded the DAZ Woodland Playset, plopped the hi-res Winter Queen into it, and used the highest auto render settings. Got the memory error message (and a totally erroneous message about missing textures) pretty quickly. Went back and tried again at my default manual settings (3000MB max texture size, three raytrace bounces ... no shadows in this case as I'm using IBL/AO) it's rendering now with no problem (and no missing textures, LOL.) This scene is WAY too simple to cause memory problems ... not even half of what xeno suggests trying. I get it now. This isn't a problem for basic renders that I can share online or view on a computer, but I'm doing more illustrations for a magazine these days, and will need to render at very high quality and sizes. I saw the message at CL indicating that they know there's a problem. Let's hope the wait for a fix won't take too long, this isn't acceptable for some rendering contingencies. Otherwise, I'm a happy Poser 6 camper, fer sure.

"Try three or four mil figures, with clothes/hair/background props/buildings/etc......... " 9 mil figures with clothes, shoes, hair & a number of props and still no crash for me and renders just fine. So I do think you have to push it further then that perhaps to see the bug. I've tried 12 mixed mil figures all textures, clothed and haired and still rendered fine.... But that was the max I could do, adding one more figure or prop would result in the render bug. Perhaps when the bug will show is also machine related, I've always got very little running in the background.

9 mil figures with clothes, shoes, hair & a number of props and still no crash for me and renders just fine. So I do think you have to push it further then that perhaps to see the bug. It's good to see that it works this way for someone......but based upon the posts, this doesn't appear to be the experience of most people. CL has admitted that the bug exists. Perhaps when the bug will show is also machine related, I've always got very little running in the background. I think that the key here might be "machine related" -- but the software needs to able to work well across the majority of PC's that are out there. Not just on a few. It's great that you aren't having this trouble. Unfortunately, that fact doesn't fix it for the rest of us.

Otherwise, I'm a happy Poser 6 camper, fer sure. Otherwise, I am too. It's a fantastic app.

I got the bug for the first time last night. V3, t-pose, some morphs for body and face, V3 tunic and pants, default lighting, and nothing else in the scene (not even a background color change). I worked for hours just fine, and got the error when trying a high-res render.

High res renders had worked on the same file yesterday so it's likely some combination of:

1. A memory leak and it happened because I worked with the same file for four hours; or

2. Swapping large textures in and out a lot, because that's what I was doing for the four hours (creating a new clothes set for the tunic and pants).

Yep, I got the bug a couple of times too, and I was rendering just one figure... :) (slow comp). But once I reduced the "max texture size or whatever" setting a couple of notches, it rendered great.

do all of you having this memory bug have "Use external binary morphs" turned on? I'm just curious if this memory bug is the same thing that Weirdjuice posted about right as P6 came out. That had something to do with the PMD format causing trouble. Since I knew there was a problem I unchecked that box when I installed P6. I haven't had any renders give me out of memory errors. (Though I certainly have had other bugs :p) I haven't been pushing poser all that hard though. The most I've had in a P6 scene is 2 mill figures, the Daz Dragon's lair, and a few low poly props. I also have 2 gigs of RAM, but hey it might be worth trying.

"Perhaps when the bug will show is also machine related, I've always got very little running in the background." It's certainly a possible factor. I violated my own advice when trying the render this morning. I was playing music through iTunes, which does eat up a big chunk of physical RAM. Interesting to see how max texture size seems to play a part. LaralynMcW, those factors are also likely to slow or halt renders. As you may know people often advise to save your scene, close Poser, then re-open the app and scene to render. Rebooting can help, too. Closing Poser is evidently the only way to truly purge RAM held hostage. I don't believe those memory-boosting apps do much to help during an active Poser session.

"CL has admitted that the bug exists." I'm not denying the bug at all.... I've just noticed a typo that makes it seem that way. "I've tried 12 mixed mil figures all textures, clothed and haired and still rendered fine.... But that was the max I could do, adding one more figure or prop would result in the render bug." That should have been: I've tried 12 mixed mil figures all textures, clothed and haired and still rendered fine.... But that was the max I could do, adding one more figure or prop WILL result in the render bug.

I have managed to do 4 in one scene with the render slider at the notch down from final. Poser 5 would never render the scene...

As an experiment after this render was complete I added Maddie to the scene with a dress, necklace and hair and up came the dreaded "Out of Memory"..

I'm on an AMD 3200 with 1 gig ram and Radeon 9800.

Just seems to vary greatly from machine to machine.

Another thing to keep in mind is that not all clothing and hair is created equal. For example: certain hairstyles are much more demanding of system resources than others. *********************************************************** If I was walking through the woods, and I saw a group of ladies like that.......it would definitely get my attention. After an initial "hmmmmmm........?", I'd probably head off in some other direction.

Yeah... Kinda like some 50s SF horror movie... INVASION OF THE BIMBOS FROM MARS!

The image reminds me of the children in Village of the Damned.

I use a spyware screening program that notifies me when an a program has been added to start when Windows starts and this morning it notified me that UserFaultCheck had been added. Investigating this program showed that it has something to do with a "memory dump". Last night was the first time I ran Poser 6 for any length of time and did quite a few renders (nothing complex at all), so I'm wondering if this is what triggered this program to be activated by Windows XP. Just curious - not too concerned if nobody knows the answer.

"The image reminds me of the children in Village of the Damned." Yes I was actually thinking the same thing.

LOL... Yes I am not impressed by the image myself, it started off being intended to be a Wedding Party image - but I gave up on any sort of expressions or continuing with the posing when P5 wouldn't go anywhere near rendering it. So this was really a test of P6. But now that you have suggested it I may go back and rework it with different clothing and do the Village of the Damned thing or "Invasion of the Generation 3's" Thanks for the ideas - now if I can add some fog without P6 falling over.......

redon634 I suggest you report that quirk to CL. That is EXACTLY the kind of thing that makes a programmer sit up and take notice, some oddball interaction that flags somehting else. No kidding, you could do a service to report it. ::::: Opera :::::