Not sure if that is a bug or a fly... Okay, so I upgraded to the SR1. Haven't had much troubles before with the "memory bug", but found it a bit slow to render. But I can put up with that as long as it -finishes- the render anyway. Now, after the SR1 installation, I had three renders (rather big, I might add, need 'em for print size) in Firefly that just won't complete after, educated guess here, 98% of the whole image render. Using Win2k, 1 GB Ram, 3 or something VirtualRam, Athlon 1,8 Ghz, 10 something GB free on the hdd, a MSI 6600 something grafics card. It -is- a wee bit frustrating not to have renders finishing, especially since I should do a commission piece... BA

Have you dropped your bucket size? If it freezes and requires a reboot, it's something else. If you can rerender, then it's usually a bucket issue. If that does not work, I usually try to help cool the processor. I take the cover off and put a fan right on it.

I've had the same problem and didn't before I upgraded to the SR1.??? I think it's a bug.

By the way what in the heck is a bucket?

the way what in the heck is a bucket? LOL. Turtle...Your renders are just ...lucky? Bucket size is the amount of pixels or square that firefly renders at a time. Reducing the "square" by half(64,32,16,8,4) relieves your pc of brain power and gives it a better chance to finish a render. If a render just stops someplace and rendertab closes like it finished, just reduce bucket in rendersettings and try again. This is in P5 and P6. I'm just going on the info Ba gave. Could be many things...

Richardson: bucket size always is 32 for me, that seems to work best. I might have to size them down some more, though. I have to strg-ctrl-alt out of Poser when the render seems to go nowhere, but by now I have done two huge renders in the Poser4 engine and one smaller in the Firefly engine, so it looks like I might have been too impatient after all. I mean, nearly 48 hours of rendering can't be much, can it? ;-) Turtle, this might have been the punishment because Poser6 ran fine before we updated...g

BA, Do you have a high dpi setting? If you do, try lowering it. As a drastic measure, you can flip your scene upside down to force firefly to render the problem area first. Words are cheap...lol

Richardson, dpi setting is 300. Hmm, I shall try a lower setting, too. As well as that flipping around suggestion, I can always correct that in PS ;) Ange

I've had this "not finishing" problem in P5 on lots of things I've rendered hi-res for prints. Reducing bucket size seems to help a lot. Another thing to try is to reduce the geometric complexity of the scene. In some scenes, I found that I could safely remove objects from the left side and get a full render of the right side, and then vice versa. Then I would patch them together in photoshop. The real thing to watch out for is shadows crossing from one area to another that depend on all the geometry being there. Another one is to wait for the large render to freeze up, cancel the render, and then save the partial render result to a file. Afterwards (or for me, typically before), render a copy at half resolution. Then you can use the lower res to fill in the broken areas of the higher res image. Between those two techniques, I can usually get a high resolution image, but sometimes, it has taken as many as four or five images to patch the whole thing together. I've been told, but have not verified, that P6 lets you render rectangular sections of your scene. If so, you should just be able to patch it together with enough care. (For reference, some of these images were 3600 by 5400 and rendered on a Pentium 4 w/ 4GB of RAM.)