skinmez opened this issue on Oct 12, 2002 ยท 10 posts
skinmez posted Sat, 12 October 2002 at 4:10 AM
nwalker posted Sat, 12 October 2002 at 5:50 AM
I recently got that error in Poser 4 and I have a pretty beefy system (P4 2.4ghz, 1g RAM). I was rendering to a new 2000 x 1000 window, got the error and decided to save my work and reboot. Once I saved, I could then render to a new window without rebooting. YMMV, but try saving your image first and then rendering. -Nancy.
Replicant posted Sat, 12 October 2002 at 9:04 AM
You're not necessarily out of memory. This is one of Poser's standard error messages and means that the .rsr file associated with one of the .obj files in your scene has become corrupted. Find the obj files in the Runtime/geometries/foldername folder and delete the associated .rsr. Poser will rebuild it the next time you load the object.
Expert in computer code
including, but not limited to, BTW; IIRC; IMHO; LMAO; BRB; OIC;
ROFL; TTYL. Black belt in Google-fu.
doldridg posted Sat, 12 October 2002 at 9:18 AM
It could also mean that your disk that your pagefile (swap file) is on has become full.
skinmez posted Sat, 12 October 2002 at 5:52 PM
Thanks for the answers. It's seems like rebooting my system before rendering works but it's strange. I never had to do that before... Thanks
hankim posted Sat, 12 October 2002 at 6:34 PM
There are actually two different error messages. If it is the "Insufficient Disk Space to Render at Current Resolution" message, you can adjust your memory -- there are directions in the Poser 4 Top Ten FAQs at Curious Labs. The message for missing objs and corrupt rsrs is indeed the "You are out of memory" message. I just point this out because a lot of people are casual in their usage of disk space and memory, and the two messages indicate quite different problems :-)
jsj posted Sun, 13 October 2002 at 9:39 AM
I often encounter the same problem. "there are directions in the Poser 4 Top Ten FAQs at Curious Labs." Could you point me to the page on provide a link as I have browsed the whole CL website (I think) and I'm not able to find such topic. Thanks in advance. Jay
hankim posted Sun, 13 October 2002 at 12:29 PM
From the CL web site -- "Poser 4 Poser can't render high resolution images. Error appears "Insufficient disk space to render" After some intense investigation we believe we have a work around. It turns out that Windows NT 4, 2000 and Windows XP must be using some space for the pagefile.sys file on the same partition that Poser is installed, to render large images. The pagefile.sys is the virtual memory or temp space for Windows. An approximate minimum would 10 MB. This amount might have to be increased for more complex scenes and animations. The maximum should be 10 MB or greater. To modify the Virtual Memory: Windows NT 4 = Right Click my computer. Click the performance tab. Click change. Click the drive Poser is installed on. Enter 10 in the Initial size field. Enter 500 or more, in the maximum size field. Click set. Click OK. Click OK. Click OK. Restart the System. Windows 2000 = Right click My computer. Select the Advanced tab. Click Performance option. Click Change. Select the drive Poser is installed on. Enter 10 in the Initial size field. Enter 500 or more, in the maximum size field. Click set. Click OK. Click OK. Click OK. Restart the System. Windows XP = Click Start. Right Click My Computer in the menu. Select Properties. Select the Advanced tab. Click Settings, next to Performance. Select the advanced tab. Click Change. Select the drive Poser is installed on. Click the Custom size button. Enter 10 in the Initial size field. Enter 500 or more, in the maximum size field. Click set. Click OK. Click OK. Click OK. Restart the System. Poser will now be able to render up to its maximum size of 4090 pixels x 4090 pixels @ any resolution " They are using frames, so I couldn't cut and paster the actual address to this, but it is under "Support," then "Tech Support," then "Top FAQs." It's not really obvious; you have to scroll down a ways, and it doesn't jump out at you, for sure :-)
jsj posted Sun, 13 October 2002 at 9:04 PM
Thanks for the info hankim. I did a test render and everything works fine. Thanks again. Jay
hankim posted Sun, 13 October 2002 at 11:09 PM
np :-)