Replicant opened this issue on May 29, 2003 ยท 14 posts
Replicant posted Thu, 29 May 2003 at 10:20 AM
I was working in Poser last night creating and doing test renders on a new figure with no problems. I loaded it back in today and every time I try to render I get an 'Insufficient memory to render at the current resolution' message. This on a brand new 2.4Ghz P4 with a gig of Ram, WinXP Pro and P4 with Propack. All I'm trying to render is a Vicky3 with hi-res texture. No other props, figures or maps. Only trying to render at 800x640 with 4 lights. Can someone explain whats happening here?
Expert in computer code
including, but not limited to, BTW; IIRC; IMHO; LMAO; BRB; OIC;
ROFL; TTYL. Black belt in Google-fu.
SAMS3D posted Thu, 29 May 2003 at 10:30 AM
you should try to delete the rsr that is in your geometries folder for the object...bet it works then. Sharen
Replicant posted Thu, 29 May 2003 at 10:34 AM
Correction. The message reads 'Insufficient disk space to render at the current resolution.' And its doing it with other figures too. Just tried to render a basic Mike.
Expert in computer code
including, but not limited to, BTW; IIRC; IMHO; LMAO; BRB; OIC;
ROFL; TTYL. Black belt in Google-fu.
JVRenderer posted Thu, 29 May 2003 at 10:42 AM
It happened to me one time, but with 3000 X 2600. I don't know if this helps. I increased the virtual memory size to 4098 and rebooted the computer and it solved the problem.
Software: Daz Studio 4.15, Photoshop CC, Zbrush 2022, Blender 3.3, Silo 2.3, Filter Forge 4. Marvelous Designer 7
Hardware: self built Intel Core i7 8086K, 64GB RAM, RTX 3090 .
"If you spend too much time arguing about software, you're spending too little time creating art!" ~ SomeSmartAss
"A critic is a legless man who teaches running." ~ Channing Pollock
Replicant posted Thu, 29 May 2003 at 11:30 AM
Thanks for the suggestions but nope. I increased my virtual memory to 4096. My view window opened mostly white with a gray corner rectangle. Any figure I load in is invisible in the window. Virtual mem set back to default and I can see, load and pose figures but they wont render.
Expert in computer code
including, but not limited to, BTW; IIRC; IMHO; LMAO; BRB; OIC;
ROFL; TTYL. Black belt in Google-fu.
SAMS3D posted Thu, 29 May 2003 at 11:36 AM
Did you check your render options window....how does that look...Sharen Also, nothing is clicked to invisible right?
skee posted Thu, 29 May 2003 at 11:38 AM
I have had this happen and I find that if you are on A PC, if you go to the task manager and (Ctr Alt Delete) and close poser this way and then restart poser it works. I think that poser has a memory leek and is still use part of your memory until you close it this way. Hope this helps. skee
NOTE: No trees were killed in the sending of this message, but a
large
number of electrons were terribly inconvenienced.
PeterWahoo posted Thu, 29 May 2003 at 1:16 PM
This is a known issue with Poser and Windows 2000 & Windows XP. Curious Labs suggests adjusting your swap file size to fix the problem. I've successfully reinstalled Poser on a different hard drive and fixed it myself. After that, if I got the error, it meant I had to defrag the hard drive. Believe it or not, sometimes Poser is telling you the truth when you get that error message. I think we sometimes underestimate the amount of room our hard drives need to render and run our software. I can't help notice you didn't tell us how much free space is on your hard drive.
queri posted Thu, 29 May 2003 at 4:33 PM
Did you use the memory patch for Pro Pack at Curious Labs? I'm iffy about too much defragging wearing my drive out. Otherwise, this has been known to help especially if you have Poser installed on an auxiliary drive.: Quoted from common FAQs at CL. 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 10 or more in the maximum size field. Click set. Click OK. Click OK. Click OK. You may have to 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 10 or more in the maximum size field. Click set. Click OK. Click OK. Click OK. You may have to 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 10 or more in the maximum size field. Click set. Click OK. Click OK. Click OK. You may have to restart the System. Poser will now be able to render up to its maximum size of 4090 pixels x 4090 pixels @ any resolution Emily
geoegress posted Thu, 29 May 2003 at 5:24 PM
yup- with me too- it's telling me to defrag
Replicant posted Thu, 29 May 2003 at 6:03 PM
I've tried changing virtual mem as suggested with no effect. The drive is less than 15% full at the moment as its a new installation and the object I'm trying to render is p4 dork with no props or background. 800x640. My machine and Poser were running perfectly yesterday. This has changed overnight. Defragged, virus-checked and STILL it says not enough disk space.
Expert in computer code
including, but not limited to, BTW; IIRC; IMHO; LMAO; BRB; OIC;
ROFL; TTYL. Black belt in Google-fu.
Replicant posted Thu, 29 May 2003 at 6:12 PM
Smacks head repeatedly on keyboard. . . . . Pinhead that I am! Thanks queri. I had forgotten to reinstall the memory patch. Must have taken Poser a few days to realise it wasn't there before it packed up. As soon as I installed it I was off and running again. :o).
Expert in computer code
including, but not limited to, BTW; IIRC; IMHO; LMAO; BRB; OIC;
ROFL; TTYL. Black belt in Google-fu.
JohnRender posted Fri, 30 May 2003 at 10:30 AM
{Believe it or not, sometimes Poser is telling you the truth when you get that error message. I think we sometimes underestimate the amount of room our hard drives need to render and run our software.} I always thought that Windows would adjust the virtual memory as needed. And why does this error message say to "allocate more memory to Poser"? The last I checked, you can't "allocate" memory to Poser on a PC... this is a Macintosh feature!
PeterWahoo posted Sat, 31 May 2003 at 7:37 PM
Poser is a silly program. It tells you some things that are not true, and it's "error-reporting" vocabulary is limited.