Introduction to Physics Simulation: Rigid Bodies and Cloth

Blender Advanced

Chapter 8 · Introduction to Physics Simulation: Rigid Bodies and Cloth

Chapter 7's own tip box pointed here directly: some motion is genuinely more practical to simulate physically than to shape by hand with keyframes and F-Curves. This chapter covers exactly that — letting Blender's own physics engine calculate realistic motion automatically, rather than hand-animating every detail.

Why Simulate Instead of Hand-Keyframe?

A stack of blocks toppling over, a piece of fabric draping naturally over a chair, dozens of small objects scattering realistically after a collision — all involve so many interacting variables that hand-keyframing a convincing result would be extraordinarily tedious, if not practically impossible. Physics simulation calculates this kind of complex, interacting motion automatically, based on real physical properties rather than manually placed keyframes.

Rigid Body Physics: Objects That Collide and React Naturally

Marking an object as a Rigid Body tells Blender's own physics engine to treat it as a solid, non-deforming object that collides realistically with other Rigid Bodies — falling under gravity, bouncing off a surface, knocking into and displacing other objects, all calculated automatically once the simulation runs.

Rigid Body Settings: Mass, Friction, and Bounciness

Mass affects how an object responds when colliding with others — a heavier object displaces a lighter one more forcefully than the reverse. Friction affects how much objects resist sliding against each other. Bounciness (restitution) controls how much energy is retained after a collision — a high bounciness value produces a rubber-ball-like bounce, while a low value produces a dull, energy-absorbing thud with little rebound.

Cloth Simulation: Fabric That Responds to Gravity and Collision

Cloth simulation treats a mesh as flexible fabric, draping, folding, and settling naturally under gravity and reacting to collision with other objects — a flag rippling in wind, a tablecloth settling over a table's own surface, a character's own clothing responding believably to their movement.

Baking a Simulation: Making the Result Reliable and Scrubbable

Baking calculates and stores the simulation's own result for every frame in advance, rather than recalculating it live every time the Timeline plays or gets scrubbed. A baked simulation behaves reliably no matter how the Timeline is navigated, since every frame's own result is already stored rather than being computed fresh, forward-only, each time.

Where Simulation Ends and Hand-Animation Still Matters

Physics simulation excels at complex, physically-driven motion, but a character's own deliberate, expressive performance — a specific gesture, a meaningful pause, a stylized exaggeration — still genuinely benefits from Chapter 7's own hand-keyframed, carefully-eased animation. The two approaches are complementary tools for different kinds of motion, not competing options where one should always be preferred over the other.

Motion typeBetter fit
Objects toppling, colliding, scatteringRigid Body simulation
Fabric draping, folding, ripplingCloth simulation
A deliberate character gesture or poseHand-keyframed animation (Ch.7)
Simulated results often get rendered as separate passes
Chapter 9's own compositing material covers combining rendered elements after the fact — a simulated cloth pass rendered separately from a background, then combined together in the Compositor, is a common real workflow this chapter's own simulations feed directly into.
An un-baked simulation can behave incorrectly when scrubbing backward
It's tempting to assume a physics simulation always shows the correct, expected result no matter how the Timeline is navigated. By default, a simulation calculates forward, frame by frame, from its own starting point — scrubbing backward in the Timeline without first baking the simulation can show an incorrect, frozen, or inconsistent state, since Blender hasn't actually stored what the simulation's own result should look like at that earlier frame. Baking the simulation before relying on scrubbing or reviewing it out of order avoids this confusing, easy-to-misdiagnose behavior.

Hands-On Exercises

Exercise 1

A student wants a stack of wooden blocks to topple over realistically when knocked, with each block reacting believably to the others. Using this chapter's own material, explain which physics feature achieves this and why hand-keyframing would be impractical here.

📄 View solution
Exercise 2

A student scrubs backward in the Timeline to review an earlier part of their cloth simulation and finds the fabric looks frozen and doesn't match what played forward correctly the first time. Using this chapter's own warning box, explain what's happening and how to fix it.

📄 View solution
Exercise 3

Explain, using this chapter's own material, why a character's own specific, expressive gesture is still better suited to Chapter 7's own hand-keyframed animation rather than physics simulation, even though this chapter introduces genuinely powerful simulation tools.

📄 View solution

Chapter 8 Quick Reference

  • Rigid Body physics simulates solid objects colliding, falling, and reacting realistically
  • Mass, Friction, and Bounciness control how objects behave in a Rigid Body simulation
  • Cloth simulation treats a mesh as flexible fabric responding to gravity and collision
  • Baking stores a simulation's own result for every frame, making it reliable to scrub and review
  • Simulation and hand-keyframed animation are complementary, suited to genuinely different kinds of motion