Wed, Nov 27, 6:02 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 27 5:12 pm)



Subject: Insufficient Disk Space question


Pharie82 ( ) posted Fri, 23 January 2004 at 5:05 PM · edited Wed, 27 November 2024 at 6:01 PM

I have this reoccuring problem when i try to render sometimes where I get a popup message that says Insufficient Disk space to render at current resolution. I'm running Poser 4 with all the updated on a PC. I usually render everything at 3000 px 100 dpi. I have 10 gigs of free space on my drive, but still get the message, even when I lower the size to 2000 px. Can anyone help me with this? PLEASE?


dlk30341 ( ) posted Fri, 23 January 2004 at 5:20 PM

I have 50G left on my HD & sometimes still get that message trying to render 1157 & less. And yes, I do defrag 1x a week. Only solution that I've come across is to reboot & try again & that has always worked for me. I'm not sure what causes it, but that's only I way I can get around it. Also I have nothing running in the background other than my broadband connection.


geep ( ) posted Fri, 23 January 2004 at 5:53 PM

The cause is the lack of RAM recovery by the OS. That's why rebooting clears the problem. ;=]

Remember ... "With Poser, all things are possible, and poseable!"


cheers,

dr geep ... :o]

edited 10/5/2019



dlk30341 ( ) posted Fri, 23 January 2004 at 6:00 PM

hmmm..I have 1g of Ram with the latest update..using PPP


galactron22 ( ) posted Fri, 23 January 2004 at 8:43 PM

I'm using PPP also, and I had the same problem a while back. I made it dissapear by changing the Virtual memory size on your PC.

Ask me a question, and I'll give you an answer.


nakamuram ( ) posted Fri, 23 January 2004 at 9:09 PM

Set your virtual memory to 0, then reboot. After rebooting, set your vm back to it's original size or larger. You should be OK, though you will eventually run into this problem again.


galactron22 ( ) posted Sat, 24 January 2004 at 12:05 AM

Actually by raising your VM to 2 gigs, or higher (depending on the size of your HD), this problem should be solved, for example I have a 2.8 Gig machine, with 1 Meg of memory, a 60 Gig HD and a second 120 gig HD, I can take about 2 Gigs per drive, that gives me 5 Gigs of memory to play with. With that much memory I sholud be able to render anything in Poser with no problems.

Ask me a question, and I'll give you an answer.


xantor ( ) posted Sat, 24 January 2004 at 8:17 AM

Memturbo might help with this problem, it recovers the ram that has been used but unrecovered by other programs.


Nance ( ) posted Sat, 24 January 2004 at 9:55 AM

As far as I know, no one has found a single solution that works at all times, on all systems. Not even going to go into the ridiculous ritual I have to employ when it strikes.


nakamuram ( ) posted Sat, 24 January 2004 at 11:49 AM

Raising the amount of virtual memory prolongs the amount of time between occurrances of the problem. Not a real solution, but a good work around if you have enough disk space.


galactron22 ( ) posted Sat, 24 January 2004 at 1:36 PM

I've had mine set with more VM fo about a year, and I haven't had any problems, this solution not anly helps Poser, but also improves PC performance.

Ask me a question, and I'll give you an answer.


crowbar ( ) posted Mon, 26 January 2004 at 4:12 AM

it is definately improved if you increase your virtual memory settings for the drive poser is located on (if you split your hard disk into separate volumes)- 2 or 3 gigs as top setting works - windows suggests a size which works well as the minimum - must be lots of memory leaks when poser runs


Privacy Notice

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.