Hanging buckets caused by high-quality settings
If a bucket takes a long time to render, it is usually caused by too high complexity/settings. Learn how to easily troubleshoot and optimize scenes with problems of stubborn buckets and render like a pro!
Hanging buckets caused by a technical error
Hanging buckets are a typical symptom of underlying scene issues. They can be caused by a whole range of things, from broken objects reflecting improperly on other objects to 3D settings that are overly high. In this part of the guide, we will cover identifying and troubleshooting technical problems.
‘Hanging buckets’ and how to find the cause of them
Hanging buckets can cause you to waste hours in rendering (possibly causing you to fail in meeting a deadline) and worse, burn your budget if you are rendering on a cloud render farm. How to fix it? First, you need to identify first what’s causing it.
Different rendering sequences
We checked different V-Ray bucket rendering sequences for their performance and perks. It’s important to have an understanding of these render sequences because later they play a role in solving hanging buckets. Check it out and optimize your scenes like a professional render wrangler!
V-Ray buckets 101
Check out our guide on how to optimize buckets in V-Ray. Today we present the first part, in which you will learn what buckets are and what is their role in rendering. We’ve tested various types of scenes with different bucket settings like sizes, and ratios to check which ones are most RAM and rendering speed efficient.
How to save money using FPE?
The FPE (Frames Per Execution) setting allows you to render several frames in a row without the need to reload the scene on a render node, and potentially may improve rendering performance/efficiency. More about FPE in our guide: https://garagefarm.net/documentation/how-to-use-and-optimize-frame-per-execution-fpe
Priorities. Fast rendering or Cheap rendering?
Many render farms offer rendering priorities that can help you balance price and get the frames as soon as possible. Priorities will determine how many nodes are allocated to your project, and where your job sits in the render queue.
Rendering tests for stills
When it comes to still images, the trick is to test a lower resolution version of the final image first. Based on such test you can calculate an estimated cost for the full resolution. You should keep in mind that still resolution tests could not scale in a directly proportional relationship to the resolution and it’s good not to set too low a test resolution.
Flicker/noise test render
Rendering a test of consecutive frames gives you an opportunity to check if a potentially noisy section of your project animates well enough. This way, you can make adjustments before you commit to the full cost of the final render.
Why step testing is the best way to estimate rendering cost?
You can get a quick estimate using render farm cost calculator. But remember, it’s only an approximation. To get a more accurate estimate for animations, we recommend testing a few frames on the farm using a step.
5 tips on how to save money on a render farm
There are many things that factor into the cost of rendering that may lead to a mismatch between the estimated cost and final cost. 😕 Learn our 5 tips to avoid bill shock and render like a pro! 🔥
What is OB hour?
Checking the pricing of most GPU farms you probably came across the mysterious 'OB hour' unit. What it is? Why do GPU render farms base their pricing on it? And most importantly: how to calculate the price per OB hour?