Fri, Feb 7, 9:53 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 07 7:37 am)



Subject: Help rendering images....


rockets ( ) posted Wed, 28 November 2001 at 4:37 PM ยท edited Fri, 07 February 2025 at 7:06 AM

This problem is driving me nuts. Most of the time I am unable to render images in large sizes. I go to render options and check the new window box and poser will start to render. After rendering a little bit, it will go nuts and blur the colors the rest of the way up. Sometimes I can render large images, but I have a feeling it has something to do with items I've used in the image. For instance, I have Poser4 with the upgrade, no pro pack. Would this be the cause? In any case, is there anything I can do about it?

My idea of rebooting is kicking somebody in the butt twice!


Cin- ( ) posted Wed, 28 November 2001 at 5:09 PM

I've had that happen before, and it's usually when I've got other stuff going on in the background... try closing everything except poser... I think it has something to do with the amount of available memory... I could be wrong... but it's worth trying... hope that helps!


BoomerK ( ) posted Wed, 28 November 2001 at 6:16 PM

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=464945

It could be a problem with available memory. Take a look at this thread--is that the problem you're having?


Purr3D ( ) posted Wed, 28 November 2001 at 6:34 PM

Sometimes it is also caused by one or more of the objects you are using having a corrupted rsr file


rockets ( ) posted Wed, 28 November 2001 at 6:57 PM

Thanks for responding. Yep Boomerk, that is exactly what mine does. I don't know how Marybeth was able to get a screen shot of it because my computer locks up and I have to reboot. Anyway I went to the link you suggested and downloaded the thingie. I guess I'll find out if it works the next time I go to render. Thanks for the tip and keep your fingers crossed for me. :-)

My idea of rebooting is kicking somebody in the butt twice!


BoomerK ( ) posted Wed, 28 November 2001 at 7:12 PM

Rockets-- If you're using MemTurbo, I recommend setting the options so that RAM is recovered automatically when the alarm level is reached. I have the auto recover level set at 15M. Also, be sure that the "Don't auto-recover unless CPU usage is below X %" option is NOT checked. Good luck--let us know how you make out.


Kiera ( ) posted Wed, 28 November 2001 at 7:32 PM

That happens to me when using certain objects in a scene. Usually there is something (I don't know what) about an object that breaks renders to new windows. I make a new document, use a default pose, load the figure textures, and add the objects one by one, doing a test render (no antialiasing, no shadows, small new window) for each item. The problematic object breaks the render. Once I find the problematic object, I render it alone and add it to the figure in post. The fact that it usually renders alone tells me that the problem is PROBABLY a memory issue. I only have 128 MB of RAM.


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.