I've been noticing this lately. Not all of my renders are completing. Why is it that the end of images, like this, are being left out, as the render process is stopping short for some reason? I think I remember reading in the manual somewhere that if your screen is only 1600x1200 and you try to render, within the Document Window, at 2000x2000 that something will get left out, but my this is the actual size of my render, on a 1600x1200 screen. So, there was no part of the Document Window unseen before the render started.

Poser running out of memory is the usual cause. Which version are you using? Poser 5 used to do that a lot, Poser 6 less so. If you're using it for a long time, it's wisest to shut down and restart because of the memory leak problems.

At least SR1. If there is SR2, that's in also. Restarting... Sheesh, I just got started! = )

I was also told that reducing the bucket size helps when I was having that problem trying to render a christmas scene.

Aha! I'd thought that too, but didn't remember to try, becasue I have no idea what the bucket size maens? Did lowering my bucket size just increase the time it took to render this?

Acadia, is that your real name, where dod you get it? I see you post all over the place, thanks for getting involved again. I remember your name, becasue at first I mistook it for "Arcade", so I can recall many of your threads!

Thanks Again!

= )

Message edited on: 02/08/2006 15:45

The name "Acadia" is taken from a snippet of Canadian History. You can find out more about that in google. And yep, no denying it, I'm a motor mouth, LOL Actually, I'm off work on long term disability right now, so I'm bored, bored, bored...and post lots.

The vucket size is the size of the square 'chunk' that Poser renders each time. By lowering it down, Poser is calculating the rendering info for a smaller area, therefore requiring less memory at any one moment. It's a bit of a balancing act, really. The smaller the bucket size is, then the more 'bites' Poser has to take to complete the picture, which can increase render times... on the flip side, by lowering the bucket and decreasing memory usage, it takes less time to do each square, thus reducing the time. I'm not sure quite wat the ratio here is in terms of increased/decreased render times (and being honest, I'm not sure I really want to go through umpteen different renders at differe bucket sizes just to find out for myself!!): anyone else got any ideas? jonthecelt

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

Here is a thread on bucket size.

I have the bucket size set on "adaptive" and let Poser decide the best size.When the render reaches something difficult, such as dynamic hair,you can see the bucket size reduce automatically. So far I've had no problems.

This can be caused by trying to get poser to do too many complex things in one render. for example, if you are using Face Off's skin shader system, it is a very complex and computer intensive material with lots of calculations etc. To fix problems caused by materials at render time, increase the shading rate (the default shading rate applied to all objects is 0.2, so if you change your shading rate to a higher amount, make sure that it is over the 0.2 mark. go up .1 at a time (aslong as your render doesnt take hours, if this is the case, jump straight to 0.5 or 1) Also, your texture sizes could be a problem when combined with complex/semi-complex materials. try reducing the max texture size, or alternatively, to get the best image, manually resize the textures used within your scene to a smaller size. texture filtering can also cause extra system usage. smooth polygon option adds extra polygons within smoothing groups of the object, increasing the objects complexity. depending on the image you are making, try turning this off. like above, the displace mapping option GREATLY increases the models complexity to model the bump map instead of using lighting to create the bump mapping. I hope some of this information helps you out.