Blender 5.0 Cycles volumes: what changed and when to use Biased

Blender 5.0 changed how Cycles handles volumes. If you render clouds, smoke, fire, or overlapping volume shaders, this is one of the first release notes worth reading carefully.

Here is the practical version for artists and small studios.

What changed by default

Cycles 5.0 ships a new null-scattering volume algorithm as the default.

In plain language:

• It is unbiased
• It reduces blocky artifacts where volumes overlap
• You no longer babysit step size / max steps / homogeneous volume settings the same way as before

For a lot of scenes, that means fewer mysterious volume tweaks and cleaner overlaps.

When the new default is enough

Stay on the default (Biased off) when:

• You want correctness and fewer artifacts
• Volumes overlap and the old stepper looked blocky
• You are fine letting Cycles handle stepping

This is the "set it and forget it" path for many shots.

When to turn Biased back on

Blender still lets you enable Render → Volume → Biased, which restores the older ray-marching style controls.

Try Biased when:

• Clouds or thick volumes feel unexpectedly slow
• You need tighter artistic control over step quality vs speed
• You are optimizing a heavy animation and the unbiased default is too expensive

Rule of thumb: start unbiased for look, switch to Biased if the clock becomes the problem.

Other volume-related notes in 5.0

A few extras that show up in real production:

• Smoke/fire can use NanoVDB (often less memory, some performance tradeoffs)
• Subsurface scattering got more accurate (can cost a bit more time)
• Keep an eye on version matching: local 5.0 vs farm 5.0 matters for consistent frames

Always check the official release notes for your exact patch (5.0.0 / 5.0.1+), because corrective releases fix real render bugs.

Farm tip: pin the Blender version

Whether you render locally or on a farm, match:

• Blender version
• Engine (Cycles)
• Color management / output format

Fxrender supports current Blender versions (including the 4.2 / 4.5 / 5.0 line), so you can keep the same version for lookdev and finals.

Quick artist checklist

1. Open the scene in Blender 5.0
2. Render a volume test frame on defaults
3. If artifacts appear in overlaps, stay unbiased and adjust lighting/density before panic-tuning
4. If time explodes, enable Biased and tune
5. Compare one frame before you commit a full animation

Want GPU time for volume tests without locking your laptop overnight? Try Fxrender — Cycles and Eevee, private storage, Free plan starts at 15 minutes.