Since my scenes got more complex in Poser 6 and I want the firefly renderer to deliver the best it could do. I wanted to know how much memory you guys are using. Even if I only use V3 without hair I can't crank up to 'final' mode in firefly. Next week I want to add some more memory but do some of you have some experiences on this? I was planning on getting 1GB extra since the memory for my machines costs approx 335euro (360dollar) per gig... So does 2GB in total do the job or are there some people with 2+ gigz and still having memory problems? (I'm using Poser 6 + SR2)

2GB Ram here. It's not enough, either. I tend to split my scenes into separate pieces and do multiple passes. That's something I did since P4PP, though.

2Gigs (DDrs) here as well and I do get the "Out of Memory" error message.

You really shouldn't use final render settings as texture filtering usually isn't necessary and will only increase the amount of memory needed for textures (about 3 times or so). Poser can only use 2GB of memory as any other app running under 32bit Windows. So Memory required by Poser itself, the scene (textures, geometry) and the memory needed for calculating the current bucket cannot exceed that. And memory always means virtual memory. Virtual Memory= RAM+Swap file. So if you've set your swap file to 4GB and all your other open applications require less than 2GB and Poser still runs out of memory, then no RAM in the world will help you render the scene, as Poser already needs more than 2GB to render the scene. When this happens, you may do something like: remove textures that aren't seen or reduce their size, change maximum texture size within Poser's render options, reduce bucket size, disable texture filtering, etc. There are enough topics on that.

I just read this on 2 other forums, what a letdown as I just built a new rig with 4 gig for gaming, but mostly to use the highest settings in Poser, oh well. Hopefully the next version will be 64 bit capable.

I only have 512MB DDR ram, I can't render full scenes. I can assemble them in Poser, but then I have to hide everything but one (or maybe 2 figures, depending on what they are), and then assemble it in post work.

2 gig here and still get the error and I only ever use the next setting down from full. So go figure..... Must admit I am just a bit disappointed

2 Gigs here too and P6 just choked rendering a single V3. Just after a fresh restart even!

@Dizzi: On this resource I found that it is possible to let an application use 3GB max memory instead of 2 (though I'm still stuck at 1GB yet) ;-) ------------------------- http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx ...The maximum amount of memory that can be supported on Windows XP Professional and Windows Server 2003 is also 4 GB... The virtual address space of processes and applications is still limited to 2 GB unless the /3GB switch is used in the Boot.ini file.... The /3GB switch allocates 3 GB of virtual address space to an application that uses IMAGE_FILE_LARGE_ADDRESS_AWARE in the process header. This switch allows applications to address 1 GB of additional virtual address space above 2 GB. The virtual address space of processes and applications is still limited to 2 GB, unless the /3GB switch is used in the Boot.ini file. The following example shows how to add the /3GB parameter in the Boot.ini file to enable application memory tuning: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(2)WINNT="????" /3GB -------------------

On this resource I found that it is possible to let an application use 3GB max memory instead of 2 (though I'm still stuck at 1GB yet) ;-) That's for applications that are compiled to take advantage of more than 3GB. Poser isn't one of those.

So what's coming clear to me is that it would be a waste of money to insert more than 2GB in this machine since Windows just consumes 190MB, leaving 1.8GB of RAM for Poser. Today I did some experimenting on raytracing instead of pre-rendered lightning maps, although the rendering time increases, it uses less memory. @SamTheRapy, Robo2010, tastiger, Do these memory problems also occur on simple scenes or only the complex ones?

My issue seems to kick in if I try to go more than one figure - my last product I tried to do the promo shots using both figures a V3 and M3 - not overly loaded with Morphs, your regular size texture maps and dynamic hair. I actually had texture size set to 2048 and texture filtering off but up comes the message. Funny thing is under no service packs I manged a render with V3, SP3, Laura and Maddie clothed but they were all using the same figure texture map. Also in Poser 5 I have manged bigger scenes with dynamic hair - so it's hard to put my finger on it. My issue is that with Poser 6 - it doesn't seem to matter what settings I use and I've tried all the tricks from various threads but still no joy. What I have noticed is on most renders my ram is dropping to about 700 meg once Poser starts the render process. So I'm really at a loss with whole issue.... Maybe an idea would be for someone to come up with a "benchmark" test scene so as we could try it out and see if it is just certain machines that suffer this problem or what. As I said above - it's somewhat of a letdown to me as P6 has all this nifty stuff but can't seem to get it all clicking together at once.

@Tastiger My problems seem to grow when the texture sizes are larger. 1050 really is the max for me and therefor I even lowered the bucketsize to 12. So I'm getting more RAM tomorrow since 1GB isn't gonna cut it for Poser. With no servicepacks on poser I had many memory leaks and deadlocks, especially when experimenting with dynamic clothing and dynamic hair. A few friends of mine also had these problems so we were very pleased with the service pack.

I'm using SP2 and still encountering problems - I may just try lower texture sizes and buckets again :)

Today I've added some RAM to my system and it seems to work a lot better. Although it seems the renderer of Poser can't handle complex scenes (about 2-3 million polygon's). I really hope this will be fixed in the next servicepack. @Tastiger, I've tested a V3 character with DM's Alina morphs & high res textures equiped with Egypt Hair on the same scene I had a Daz Hires Skeleton (based on M3) with P6 Dynamic hair) and I was able to render it with the settings: resolution: 1600x1200 cast shadows: on ray trace: on ray trace bounces: 1 min shading rate: 0.2 pixel samples: 4 max texture size: 4096 bucket size: 32 smooth polys: on Although I have to admit, the first 2 times the rendering progress bar was still at 0 after an hour or 2 so I figured it crashed. Thnx guys for the feedback. Although 2GB still won't solve every memory issue, I've learned that more than 2GB isn't necessary for Poser since it can only allocate 2GB. I've upgraded my system and am pleased to say it works a lot better!

Hi Phlegethon, as it looks like you are from Europe, take a trip to Germany, 1 Gig DDR 400 RAM is at about 90 . Until now I had NO probs with memory and Poser. May be you have should try to set your SWAP file to 2048 Mbyte min and max.

@Jules53757 Here in the Netherlands it's a little more expensive, about 110 - 125 for standard DDR 400 memory. But unfortunately my system's old memory was Corsair XMS DDR 467 (PC3700) and my system is an Intel P4 3.0 running at 3.6Ghz stable, because of this the FSB runs at 960Mhz so the DDR is clocked at 240Mhz (or 480 because it's doubled) so DDR400 wasn't going to cut it. Now I've bought some Corsair XMS PC3200 (DDR400) memory extra since the extra 220 is way to much for a mere 300Mhz, It's now running stable at 3.3Ghz with the memory clocked at 220Mhz (440), and slightly slower timings (Intel likes Mhz, AMD likes tight timings). I now set the memory page file to 2048MB (was 1526MB) going to try that now. Thnx for the tip.

and make the pagefilesize fixed min and max the same size. Best performance you get when when you start with no pagefile and defrag and after this create the new Pagefile.