Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Dec 04 2:47 am)
Welcome to the Poser Technical Forum.
Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)
This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.
New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.
I have the exact same problem yet mine sometimes even barfs at trying to render a 1280x1024 image (usually my images/renders become wallpaper for my computers since I royally suck at doing anything I would consider 'for public consumption') on my Win2000 system. I can take the SAME pz3 file and render it on my laptop running Win98 and it renders just fine.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
with a new computer and Win 2000/SP1 with lots of ram and disk space, I get this insufficient disk space errors on rendering at 2000x1600 at 72 pix/inch - increasing virtual memory beyond 3 GB with 1 GB real ram makes upgraded poser 4.03 with pro pack SP2 load/open with invisible figures and wierd screen. I rendered an 111 MB .pz3 file ok at 2000x1600 at 72, but sometimes can't render a 0.7 MB file with only one of the same characters - are there other tricks to get poser/propack to look at disk space correctly or is there something else going on?? my old computer could render at 3090X2470 at 72, although slowly.