Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 29 7:57 am)
I have 1.79 Gig left on my C drive I have 21.5 Gig left on my D drive Since I posted the last reply, I played with my virtual memory settings. But each time I changed something, Poser wouldn't work right at all. My virtual memeory settings are now set at "system managed size". Poser works well, but will not render many images of a specified size. Rendering to the windows always works.
When you're talking about graphics programs, 1.7-10GB is not very much. So therefore, your problem was(is?) the lack of hard drive space. As for the swap file, Curious Labs recommends adjusting your swap file settings. I found it easier just to get a much larger hard drive (currently 120GB), and reserve that for Poser alone. On the rare times that error occurs again, I defrag the hard drive. The problem is then solved. By the way, this question is asked and answered once or twice a week. You might find some great insights by doing a search or browse through the forum.
I found that I could not exceed 2000 pixels width on my renders while experiementing. I cleared another gig off my C Drive and there was no change. Can someone tell me why I can not go past 2000 pixels width with out getting the error "Innsufficient Disk Space to Render at Current Resolution". I checked the Poser manual and it does not mention a size limit. thank you marty
HI- in P5 reduce the bucket size and turn off back side polys will help a bit- but your problem really is your drive. You can find a 80 gig drive online for about 80 bucks. also- if you put poser on your d drive you'll get better performance (thank god all you have to do is cut and paste the program over :)
I've found it helps if you move your paging file off your main drive.
What we do in life, echoes in eternity.
E-mail
| Renderosity
Homepage | Renderosity
Store | RDNA
Store
I never got this problem fixed. I tried every possible suggestion, defragmented everything, messed with the virtual memory, upgraded the physical memory, rearranged the partitions, you name it. I eventually just upgraded to P5 (and I'm glad now that I did). Sorry to be so negative. I do wish you luck (some people really did find a way to fix the problem!). bonni
"When a man gives his opinion, he's a man. When a woman gives her opinion, she's a bitch." - Bette Davis
I've found the CL's Poser Pro Pack Memory Updater fixes the problem for me on PPP: For Poser Pro Pack users with greater than 1GB of total memory (RAM + virtual memory = more than 1 GB.) to run normally. jen
Check out my full gallery at Cliff-Dweller Artworks
I find that when I try and render at too high a resolution I get a similar problem. I have 4 gb of ram (3 shows up)so should really have a 10 gb pagefile or so but WindowsXP only recognises a 4 gb pagefile. Hopefully XP64 will address this (I use a dual opteron) but then I guess I will need to get a 64 bit poser and vue4pro to take advantage. In the end though I suspect the problem lies with Poser as I can move problem scenes that crash on Poser to Vue 4 Pro and then import more stuff and render it at very high res in superior or ultra mode without trouble. However, if Poser is loaded in the background it crashes :)
"I am extraordinarily patient, provided I get my own way in the end" - Margaret Thatcher 1989
I've seen this error pop up too, but only when rendering with the P4 render engine. My Poser is installed on my d: drive, with over 60 Gb of free space, defragmented. It happens both with small scenes (small in number of figures and props) and very large scenes. Usually Poser dies on the spot when the error pops up, after reboot the render usually works. It may have to do with Poser memory leaks.
The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter
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.
I have been using PPP and P5 for some time on my old Pentium 2 computer with Windows 98 OS and never saw this message before. I commonly render at 2000 pixels. I have reciently purchased a Sony VAIO PCG-K23 Notebook PC (2.8 GHz Pentium 4, 512 MB RAM, 60 GB Hard Drive, Combo Drive). It has Windows XP Home OS. Now I am getting the error message while attempting to render alot! "Innsufficient Disk Space to Render at Current Resolution" By the way, I have lots of space on my hard drive. The hard drive was factory partitioned into a c: and d: drive. I have over 10 gigs available on the c: drive and much much more on the d: drive. Help! marty