shadownet opened this issue on Dec 10, 2007 · 10 posts
shadownet posted Mon, 10 December 2007 at 12:52 PM
Hi,
Looking for any tweaks, tip, tricks, etc. to get Poser 7 to perform its optimal best on XP.
I have a 2.66 Intel Processor (dual core) with 3.0 GB RAM, ATI Radeon w/ 256 MB, and huge free hard drive space.
I have found using Rambooster helps, but I still get "out of memory error" when trying to render (seperate process) large scenes. What I don't get is why I show plenty of free RAM(often 1024 mb or more) available when I get the OME????
Rob
kuroyume0161 posted Mon, 10 December 2007 at 2:46 PM
'Cause 32-bit processes only get 2GB max normally. You could have 300GB and it won't help Poser running out of memory...
There is a thread here on getting Poser to use more memory (up to 3GB) - it requires some fiddling with Poser and the OS boot ini.
C makes it easy to shoot yourself in the
foot. C++ makes it harder, but when you do, you blow your whole leg
off.
-- Bjarne
Stroustrup
Contact Me | Kuroyume's DevelopmentZone
svdl posted Mon, 10 December 2007 at 3:36 PM
Poser 7 does not require fiddling. Windows does.
Open boot.ini from your C: drive in Notepad and add the text "/3G" after the text "/fastdetect". This will make Windows allow up to 3 GB of address space per process. Now both Poser 7 itself (integrated renderer) and FFRender can use up to 3 GB of RAM (virtual or physical) for rendering.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
shadownet posted Mon, 10 December 2007 at 4:33 PM
Thanks for the info. This explains why upping my system to 3 GB over 2 GB did not show me any marked improvement. The notepad edit looks simple enough, will definitely give this a whirl! :O)
pakled posted Mon, 10 December 2007 at 8:25 PM
there's also something with buckets in Poser memory...vague on that, but maybe it will job someone's memory...;)
I wish I'd said that.. The Staircase Wit
anahl nathrak uth vas betude doth yel dyenvey..;)
ghonma posted Tue, 11 December 2007 at 2:36 AM
Quote - add the text "/3G" after the text "/fastdetect"
'/3GB' not '/3G', see here for more info:
Also make absolutely sure to back up the 'boot.ini' file somewhere safe. One mistake in it and your system will refuse to boot anymore till you fix it.
shadownet posted Tue, 11 December 2007 at 8:13 AM
Hi Pakled, the bucket size can be reduced to save memory and can also be set to adapt itself as needed, not sure if that option applies when rendering in a seperate process. You can lower the bucket size in the Render editor and this does help, say if you have a bucket setting of 64MB and get an EOM you can reduce it to 32 or 16 and often FF will render.
ghonma, thanks for the additional info. I saw the 3G and thought maybe it should be 3GB. Definitely backed up the ini. :O)
shadownet posted Fri, 14 December 2007 at 3:23 PM
Another question (or two) . :O)
Would setting Performance Options (system properties) Memory usage from Programs to System cache help? hurt? or not really make much difference? Tested this (only a few times) and I could not see where it made much difference, so am curious.
Also, when setting the page file(s), is there any particular do's & don'ts I should know so as to get best results there?
Thanks again.
:O)
Telecino posted Sun, 23 December 2007 at 10:21 AM
To lower the memory usage of my scene and be able to put much more people and clothing, i use DownRezer, that helps manage the size of texture files loaded. You can search Renderosity about it. It works great.
I'm a dork, animating dorks: www.TheDorkers.com
shadownet posted Sun, 23 December 2007 at 2:16 PM
Hi Telecino,
Thanks for the tip! Will check it out! :O)
Happy Holidays!