Anyone know when CL are going to pull their fingure out & sort the memory problem out - as it's driving me nuts!! every time I go to render a fairly large seen I get the out of memory message. I have an ATI 256MB G/Card, P4 3ghz processor with 3Gig of Ram. So I doubt it's my system....is it??

they are programers all they will say is "soon" and based on my personal observations of posts in the forums, most (not all) people experiencing the problems have over 1 gig of ram. Few people with 1 gig or less, seem to be experiencing the memory problems.

Intresting...

i've got less than a gig and i've had it bad at times. :(

I have 1 gig and I don't think I have ever had a memory problem with Poser 6. Now problems doing reflections and refractions are another story. But they say they are going to fix that too.

i heard it was next week on the service release

I guess we're just going to have to wait for CL to sort it out - however long that will take!! Problem with reducing your memory is what do you do with apps like Vue/Bryce where as the memory you have the better.

I do hope so - figures crossed!

I've got 1.5 Gig, and instead of getting the out of memory error, my render just dies. Yesterday a render died with a single figure, a prop and NO TEXTURE! That, when it doesn't just lock the UI when dialing a body part. Yes, I've updated the drivers. No, I'm not using OpenGL. So far the program is completely unusable, and I'm begining to climb up the walls, and plain not wanting to use it. Very annoying.

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2248015

Hopefully, SR1 will address the memory problem to everyone's satisfaction.

If you like, you can follow the link to the last memory bug thread. And then you can follow the links embedded in each thread jumping backwards to the thread before it for about 4 threads or so. Finally ending with the Curious Labs SR1 announcement thread.

All of these threads have been posted in the last few days.

Have fun!

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2243391

Anybody else notice that the freezing(memory bug) seems to happen in the auto mode..if i render my final pic in manual and click shadows and smooth polygons and/or raytracing, the pic looks great and I never get the "not enough memory" pop up. Wonder why that is???

I got it once while rendering. I dont remember the settings. And I got it while still constructing the picture and didn't even get to render it.

I Have 2 gigs of ram and have only had One Out of memory error. and that had to do with my displacement settings. You might be on to something though as I don't use auto mode. Pretty much everything I've done in Poser 6 has either been cel shaded or procedural so there were no big textures to choke things.,.. still this is a better record than I've had with poser 5 (which just freezes rather than giving an error when it runs out of ram) The only big bug I've experienced in Poser 6 is the flashing mat room nodes when Main camera is on. (That needs to be crushed big time)

i have no problem when it acts as a door stop. works great every time. :)

I've had the issue, too. Does anyone know if it can be fixed (or avoided, anyway) by doing multiple area renders, and just doing it in small portions?

The email I got from CL lead me to believe that the SR should be out this week or next. I think everyone gets the bug sooner or later; in my experience, it seems like anytime you start dealing with large textures, you run into the problem (stands to reason: large textures = more memory).

It worked fine with a file yesterday, but when I open and try to resave it today, I get the out of memory error. I've learned to save all my files in incremental steps so it doesn't eat ALL of my work anymore. The length of time we've had to work around this bug has been very frustrating.

i usuaully get it with large textures + Texture filtering. The auto thing is intreging not because it's auto, but because it turns on texture filtering when turned up. I usually just crank it up then turn off texture filtering and turn down my texture to 2x the size of the image or 3000 what ever is less. (I've noticed no real difference in haivng it 2x the image or 4x the image so for images under 1500px this forumla seems to work fine. Even after the fix I'll probably stick with this as it help render times a good bit. That is unless someone can offer proof that there is a difference. I'm always open.)

Message edited on: 05/11/2005 09:21