Wed, Dec 11, 6:48 AM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

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.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: Need help on rendering larger files on Win2K


JimYount ( ) posted Fri, 11 January 2002 at 8:56 PM ยท edited Wed, 11 December 2024 at 6:43 AM

(I've also posted this in the general section) The Poser folks and I are struggling with a problem on my Dell Precision Workstation 530 (512MB RAM, lots of hard drive space). I'm getting the "insufficient disk space" warning when attempting to render images larger than about 1000 pixels square. I've tried the "workaround", setting the pagefile.sys to 10mb, with no luck. I'd really appreciate hearing from anyone who has run into "extra" challenges in Win2K, and solved them. I really need 3000 to 4000 pixel files for my glass carving work.. Thanks in advance! Jim


geep ( ) posted Fri, 11 January 2002 at 11:44 PM

file_255254.jpg

I am running Win98 384 MB RAM 2 x 10 GB HDD Poser 4 Renders up to 4k x 4k .... no problems. When I tried 5k x 5 k, well, see attached pic. cheers, dr geep ;=]

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


cheers,

dr geep ... :o]

edited 10/5/2019



ScottA ( ) posted Sun, 13 January 2002 at 6:52 PM

Jim, I use Poser with the Propack and a dual boot setup. Win2k&Win98 using FAT32. I can render up to 4090 pixels and I only have 128meg RAM. So I'm guessing this is a system related problem. If you are using Poser4 without the ProPack. There is a patch on the curiouslabs website that is made for people who are using Win2k. If you haven't installed it. You should give it a shot. ScottA


JimYount ( ) posted Sun, 13 January 2002 at 7:00 PM

Thanks, Scott... I'm running 4.0.3 without ProPack. I didn't find the patch you mention, perhaps I'm looking in the wrong place. Could you give me a specific location? Or is it the 4.0.3 updater that you are referencing? Jim


ScottA ( ) posted Sun, 13 January 2002 at 7:15 PM

Hmmm...It's been a while since I used Poser without the Propack. But I think the 4.03 update was the one I used to fix my Win2k troubles. So I guess you've already got the best update installed already. The "Insufficient filespace" error might be leading you in the wrong direction. Something as simple as Windows not knowing where your temp folder is located can cause that error. And you could be chasing a ghost. I'm not sure I could figure it out unless I had the system in front of me to play around with. ScottA


Thorgrim ( ) posted Tue, 15 January 2002 at 12:48 PM

I'm on W2k now, but I had this problem a while ago in Win95/98. When I phone Medicreations about the problem. I was told that Poser 4 uses the environment variables TEMP or TMP for locating its temporary files. So you might want ot point these variables to a directory on the disc with the most free space. To set these variables or check them do the following... 1) Press the Start Button 2) Seleect Settings->Control Panel 3) From the control panel select the system module 4) In the system module select the Advanced tab 5) From the Advance page select Environment Variables. 6) The TEMP and TMP variables should be in the User variables section You can change or create them there. Also I have been told more than once that you can go above Poser 4090 pixel limit by rendering your pic as a one frame animation using the as a series of pictures option. I have not tryed this yet though. I hope this helps, Thorgrim


Thorgrim ( ) posted Tue, 15 January 2002 at 1:00 PM

As a further note, I've always found it a good idea to have a temp partition on my least used drive. Currently I have about 3 gig devoted to this partion. All my temp stuff points to this partition including the temporary files for the Internet explorer.


acottted ( ) posted Wed, 06 February 2002 at 2:38 AM

I also have a dell 530 with lots of ram and lots of disk space and was running win 2000 pro and had the same problems, if I was tricky I could render at 2400 x whatever, but not above and lots of steps to get that, same messages as you show and no amount of moving temp files or switching virtual got me above that - I finally cleared out my second disk drive and installed Win xp pro on it as a dual boot and then installed poser 4.0 and then upgraded to 4.0.3 and then added pro pack and my problems are solved - I tried renders after 4.0.3 and they worked also so pro pack is not necessary - I now let win xp control my virtual/page file and can render at 4090 x 3270 and everything is ok again - if you have a separate partition and/or seaparte drive, win xp (I had an OEM version so I don't know about an upgrade) will go do a dual boot and not have any problems - this really solved a vexing problem for me - Ted


JimYount ( ) posted Wed, 06 February 2002 at 9:19 AM

Ted, Thanks so much for the input. I had been avoiding an upgrade to XP Pro, since Win2K was doing everything for me; I'll consider it now. Any reason I should not just upgrade the entire machine? XP Pro seems like an easy step from Win2K, I'm guessing the upgrade would go smooth on such a new machine. Jim


acottted ( ) posted Wed, 06 February 2002 at 9:26 PM

Jim - although I don't know for sure as I haven't moved all of my stuff over (do run the compatibility checker first), I think everything on my system is doing ok with XP so you should be ok going up without dual boot - Ted


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.