Back when I rendered on my old AMD single core tower, I didn't think anything of this. But now I have an HP laptop that has a triple core AMD processor and 4 gigs of ram. It is doing it still.

Has anyone successfully rendered something at 1800+ X1800+? (that was the last size I tried to render.) If I remember correctly I have never gotten a render larger than 1500on one side to render completely in Poser 7.

I was just able to render a 2000x2000 scene in poser 7. It was a simple scene and I just used the very basic render settings. Perhaps it's a memory issue.  check out http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2830394 for some ideas. And maybe someone with better knowlege will come along with some help.

I have managed 3000 x 2400 on my desktop machine with just 512 mb of real memory.

Thats just under 22 mb to store the image in memory.

Try checking task manager when Poser is running and watch memory use.

In Poser 8, I've done 5000x5000 pixel renders with very high quality settings, containing a V4, clothes, and some scenic props and had no problems, and I've done 2500x2500 pixel renders of similar complexity and had Poser choke, or simply close down before the render finished. My only guess is that something in the scene is causing a problem, and it might not be something which is obviously huge/complex. Possibly AO or reflections on some props can be the death of a high resolution render...

Quote - I have managed 3000 x 2400 on my desktop machine with just 512 mb of real memory.

Thats just under 22 mb to store the image in memory.

Try checking task manager when Poser is running and watch memory use.

Yeah, I used to do that. I would render in a separate process (which helps a lot, btw), and watch to see if the memory of FFrender.exe approached 4gb. If it did, the render would not complete because right around 3.9gb, the render would always close. Thankfully, this isn't a problem for me in Poser2010.

Just a thought but what dimensions is your monitor , and have you set 'render to exact dimensions'  in the render settings ?

My monitor is a 17" laptop screen. I do have render to exact dimensions checked and it still dies usually telling me that there is not enough memory. This is even after I poen up the task manager and set poser to high priority... I have not been able to find firefly renderer in the task manager on this laptop though.

Sorry it took me so long to reply I pulled a double at work and  just got home a few minutes ago. Ill be winding down some before I  come back to this thread. Thanks to everyone who replied.

Quote - My monitor is a 17" laptop screen. I do have render to exact dimensions checked and it still dies usually telling me that there is not enough memory. This is even after I poen up the task manager and set poser to high priority... I have not been able to find firefly renderer in the task manager on this laptop though.

Make sure you have "render in a separate process" checked. Otherwise, the renderer will not appear as a separate process in task manager. And use the task manager to set Poser to a "below normal" priority before you start rendering. FFrender.exe will not appear until the rendering actually begins and it will take the priority that is assigned to Poser.exe.

the largest I have rendered was 9000X9000;
4 GB RAM may not be enuff for that. YMMV.

A suggestion, load Poser, delete the figure, import background image and use a image thats over 2000 x 2000 . Then render that.  If that does not render you have a major problem.

Well I set it to render in a separate process and do far i am up to 2500 on a side so that seems to have fixed my problem for now. Though Poser does force my laptop to groan and complain about memory usage even when setting poser to low and FFRender to high. I just ignored all the complaints and let it continue rendering.

Thanks for the advice, I have not had time for much poser lately so I have forgotten a lot (damn I need to relearn VSS from scratch i think, hopefully it all comes back easily)

You might check your settings for virtual memory. I just set mine to system managed and leave it.  You can get problems if its set too low.

LOL well that may have had something to do with some of it the vityual memory was set at 256... I cranked it up to the max . I'll see how that goes now

Quote - Well I set it to render in a separate process and do far i am up to 2500 on a side so that seems to have fixed my problem for now. Though Poser does force my laptop to groan and complain about memory usage even when setting poser to low and FFRender to high. I just ignored all the complaints and let it continue rendering.

 

Thanks for the advice, I have not had time for much poser lately so I have forgotten a lot (damn I need to relearn VSS from scratch i think, hopefully it all comes back easily)

I find that it works best if you do not set either ap to a high priority, but have them both running at below normal. If you set Poser.exe to below normal before you start rendering, then ffrender.exe should run at below normal as well, and for me, that works best. Putting it at high seems to make the problems somewhat worse. YMMMV.
This thread gives a decent explanation of how to set up a shortcut to do the work for you:

http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2778338&page=4#message_3492982