Another GB will make a difference. That's for sure.

CPU usage up to 50% means that you're not making use of the multithreaded rendering capabilities of Poser 7. Go to tEdit -> General Preferences, switch to the tab 'Render", and make sure the number of threads is set at 4.

Larger renders can also benefit from the option 'Separate Process'. This means that a separate render process is started, which again can use up to 2 GB (3 GB if you trick Windows XP) of address space. If you render in Poser itself, quite a lot of address space is used by the Poser program itself, leaving less address space for the render data.

Here's how you can tell Windows XP Pro (doesn't work on Home) to allow 3 GB of address space per process instead of the normal 2 GB.

• open c:boot.ini in a text editor (Notepad), the easiest way to do this is to right-click the My Computer icon, choose Properties, tab Advanced, button Startup and Recovery, and then choose the button to edit startup options manually.
• add the text '/3GB' to the end of the line that reads 'multi(0)disk(0)rdisk(0)partition(1)WINDOWS="Windows XP ...'
• and save.
  After the next reboot, Windows will allow programs to use up to 3 GB of (virtual) memory each, instead of the normal 2 GB. Poser 7 can make use of this extra GB. Earlier versions of Poser cannot.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff