Path Tracing: The Decisions That Matter
A rendering method that simulates light by tracing many random paths through a scene, producing realistic global illumination, reflections and shadows.
The key figures
- Method
- rays bounce through the scene to estimate lighting
- Noise
- fewer samples produce more noise
- Examples
- Blender Cycles, Arnold and RenderMan
- Real time
- GPUs increasingly support path tracing in real time
Why this is worth getting right
Path tracing is the basis of most photorealistic rendering, and understanding its sampling helps balance quality against render time.
Do this, not that
Do
- Increase samples in noisy areas rather than globally
- Use denoisers to reduce render times
- Limit light bounces sensibly
- Optimize lights and materials that cause noise
- Test render times on a representative frame
Don’t
- Maximum samples everywhere
- Caustics and fireflies left unmanaged
- Ignoring render time budgets
- Denoising so strongly detail is lost
When to bring in help
Our advice Bring in help when renders are noisy or render times are too long for deadlines.
Where this comes from
- Blender Foundation — Blender manual: Cycles
- Pixar RenderMan — RenderMan documentation
The figures and practices above come from the sources listed.
Working on something like this?
We take on 3D Design & Development work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.