Fri, Nov 22, 8:20 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)



Subject: Speeding up FireFly rendering


stewer ( ) posted Mon, 07 July 2003 at 3:00 AM ยท edited Tue, 12 November 2024 at 7:58 PM

Attached Link: http://www.cxi.cx/pixels/faq/view.php?firstentry=0&category=Rendering

I have posted this in another thread already, but it might get overlooked: Here's how to make FireFly render fast! * Reduce the number of pixel samples. A value of 1 will give you aliasing artifacts but will render much faster than with the default of 3. * Check "remove backfacing polygons". * Disable displacement mapping. * Increase minimum shading rate. This can make your textures and some objects appear coarse but again speed up rendering. Don't hesiate to try values of 20 or even higher. * Increase the bucket size as far as your RAM allows to. Try values like 64 or 128, if you have simple scenes or lot of RAM, 256 is doable too. See the attached link for more information about what bucket size means. Using these optimizations, FireFly is rendering most scenes noticeably faster than the Poser 4 renderer on my computer. Of course, most of these speed optimizations affect render quality too, but these are great for draft renders if you want to check your lighting etc. More hints? Here you go: * Bucket size does not affect the quality of the image. If your RAM allows to, use large values here for production rendering too. * If you don't need to see single-sided polygons from the backside, always keep "remove backfacing polygons" checked. Faster, but no quality loss. * When using lots of lights, raytraced shadows can actually be faster than shadow maps, plus they will need less RAM. Experiment here. * If you have Moirartifacts, try enabling texture filtering, increasing pixel samples and/or increasing post filter size. Let me know if there's interest in a FireFly FAQ, I'd be happy to set that up.


Hanz ( ) posted Mon, 07 July 2003 at 3:51 AM

Thanks a lot for sharing, stewer! I, for one, am somewhat ilitterate when it comes to the firefly rendering engine, and I most often just go with the default settings as I assume those to be the best. I will definitely try out these hints of yours, as speed is a sought after factor. As for the FireFly FAQ, yeah Id be interested. :) -Hanz


dolfijntjes ( ) posted Mon, 07 July 2003 at 6:25 AM

Thank you and yes I would be very interested in a tutorial it tooks hours sometimes to render


Dave-So ( ) posted Mon, 07 July 2003 at 7:04 AM

FAQ would be a great help... also, a bit more explanation of why or what each of those settings is doing... Thanks much :)

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



Dave-So ( ) posted Mon, 07 July 2003 at 7:06 AM

what is TEMPEST ???

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



Momcat ( ) posted Mon, 07 July 2003 at 7:07 AM

Absolutely! A FAQ would be quite an asset. >^_^


lululee ( ) posted Mon, 07 July 2003 at 8:14 AM

A FAQ would be great. Thanks for sharing your expertise.


stewer ( ) posted Mon, 07 July 2003 at 8:53 AM

Attached Link: http://www.keindesign.de/stefan/poser/renderer.html

Here's a first try...might be helpful, although it's basically a rehash of the manual. Dave-So: Tempest is the "big brother" of FireFly - it's the render engine of Pixels:3D which FireFly is based on.


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.