Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 29 8:45 pm)
Any idea at what size it takes for it to happen? or is it all "new window" renders? This may seem lame but here is an idea. Change your screen setting to the highest posible size. Then just resize you document window as high as it will go. After you are done just reset your settings. Anton anton@daz3d.com
-Anton, creator of
ApolloMaximus: 32,000+ downloads
since 3-13-07
"Conviction without truth is denial; Denial in the
face of truth is concealment."
Unfortunately this issue is related to the Poser 4 renderer and the format on which it was based, when it was created on a Mac many years ago. The original Poser renderer is tightly wrapped around using the Macintosh PICT format. PICT files have a dimensional limit of 4096 pixels in either direction. Try an experiment in Photoshop by creating a PICT file larger than 4092 (a 2 pixel buffer on each side). It can't be done, even on Windows. The inherent relationship on PICT for the original Poser renderer is another reason for the new P5 Firefly renderer. Firefly has no inherent pixel limits.
I did some experiments, and it seems to kick out at higher sizes. One image worked up to about 2300 pixels high, and at 2500 went white and didn't render. I'm going to try deleting certain objects and see if it's a specific model that's causing problems. I changed the virtual memory size and it does it less now, but a full page scene for me (3150 x 2025 pixels) still hits a wall sometimes. Thanks for the suggestions!
Just tested it on my system @ 3150x3150 using P5 with the P4 renderer. I used Daz Mil Dragon with textures and Vic2 and it rendered fine in a separate window. I do have my virtual memory set to 4095-4095 (4 GB) so windows doesn't have to grow it when it needs more. I noticed as the render progressed it seemed to get slower but it eventually finished. TF, what is your virtual memory settings?
I can no longer get to this fix on the CL site, so copy it out-- it worked for me: XPHome, Pent4 1.8 and 2.4g proc-- 50 to 60 Gb free. I was unable to render outside the window-- though I could make the window as big as I wanted. Emily *** 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
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'm trying to render a series of images by the end of the week, and most of the scenes I set up render fine in the main window, but when I try them at full size (3150 pixels high), it won't work. I have a grey background, but the window turns white when the render starts. The progress bar shows it rendering the file, but when it finishes, the window closes and it's like it never even rendered. I tried the P4 render engine, and it tells me I have insufficient disk space to render (I've got 60 gigs free, and 1024 megs of ram). I adjusted my virtual memory size as it spells out on the Curious Labs website tech support, but it still doesn't work. The scenes aren't that complicated, and some of them work, but I've got to get these images done, and the little version in the main window won't cut it. I love the new features in P5, but the current performance is letting me down.