@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.

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!

@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.

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?

@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 -------------------

Merry X-mas to you too Vilian! Very cute card, I hope those hamsters finish the snowman in time ;-)

Message edited on: 12/25/2005 16:59

@DareWolf No, Poser doesn't have a memory leak but it really uses the available memory as inefficient as possible. Terminating the rendering engine frees all memory. I hope they fix this in SR3 or Poser 7 since it's been a problem in Poser 5 also.