Mon, Dec 23, 8:22 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 23 8:11 am)



Subject: What is "Bucket Size" ?


Kagato98 ( ) posted Sun, 06 October 2002 at 1:07 PM · edited Fri, 02 August 2024 at 5:13 PM

I still haven't figured that out - I scaned my manual's index, and it wasn't mentioned. Is that the size of the squares it renders in, possibly?


Kagato98 ( ) posted Sun, 06 October 2002 at 1:17 PM

Wait, wait. I just figured it out - It IS the squares that FireFly renders in. Changing the bucket size to a smaller square should take up less RAM, but give longer rendering times - but setting the bucket size to larger sizes takes up more less rendering time, but more RAM. Am I right on this?


Kagato98 ( ) posted Sun, 06 October 2002 at 1:18 PM

Err....."but setting the bucket size to larger sizes takes up less rendering time" . That's how that should read.


Jcleaver ( ) posted Sun, 06 October 2002 at 1:23 PM

Yes, you are correct.



thgeisel ( ) posted Sun, 06 October 2002 at 1:29 PM

seems to be right.but the default setting of 32 seems to be some optimum.tried 64x64 no increase of speed or only a little bit. making smaller i didnt try,think it has something to do,how ff calculates antialiasing.and how its done where one bucket hits the next.


nerd ( ) posted Sun, 06 October 2002 at 1:42 PM
Forum Moderator

Attached Link: Fire Fly

Kagato98. Read one thread up. How did I know somebody would ask this...


Kagato98 ( ) posted Sun, 06 October 2002 at 2:00 PM

Thanks for the thread, Nerd.


Dave-So ( ) posted Sun, 06 October 2002 at 4:08 PM

Thanks for this...considering bucket size was what was killing my render times in Default FF mode...

Humankind has not woven the web of life. We are but one thread within it.
Whatever we do to the web, we do to ourselves. All things are bound together.
All things connect......Chief Seattle, 1854



JHoagland ( ) posted Sun, 06 October 2002 at 7:16 PM

At the risk of starting an agrument, here is the stock answer: "Read the manual". Specifically, look in the section on Renderings and FireFly Settings.


From the Poser 5 printed manual, chapter 46, "Using The FireFly Render Engine", page 335, paragraph 2: Bucket Size: The bucket is the area being rendered at any one time... Increasing the bucket size increases the area being rendered at once but requires greater system resources. Use caution when enlarging the bucket beyond its default size, and monitor your system resources.


VanishingPoint... Advanced 3D Modeling Solutions


Dave-So ( ) posted Sun, 06 October 2002 at 9:21 PM

Jhoagland...I have read the manual, and in fact quoted it....in a different thread...but what it says and what it means are 2 different birds.... Because...if you DECREASE the bucket size...it increases your render time, and vice versa... For me, if I see "requires greater system resources", I equate that to mean slower render time, and I think many of us assumed that...but it is just the opposite.

Humankind has not woven the web of life. We are but one thread within it.
Whatever we do to the web, we do to ourselves. All things are bound together.
All things connect......Chief Seattle, 1854



Jcleaver ( ) posted Sun, 06 October 2002 at 9:40 PM

Not to belabor the point, but the manual in this case is correct, it has just been misinterpreted. Perhaps the manual could have been a little clearer.



Dave-So ( ) posted Sun, 06 October 2002 at 9:57 PM

yes..misinterpreted...a good topic for the future Poser for Dummies book

Humankind has not woven the web of life. We are but one thread within it.
Whatever we do to the web, we do to ourselves. All things are bound together.
All things connect......Chief Seattle, 1854



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.