Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 37 Β· Simulation and Workflows

Blender Rigid Body Physics: Falling, Colliding and Baking

Simulate falling and colliding objects with Blender rigid bodies: active and passive types, mass, friction, bounciness, collision shapes, caches and baking to keyframes.

Rigid body physics lets Blender move solid objects the way real ones move: they fall, collide, bounce, topple and stack, with no keyframes. It is perfect for crumbling walls, rolling dice, toppling dominoes and scattered debris. This lesson explains the settings, the simulation cache and how to bake a result.

Blender cannot run on this site, so the steps are given in words, and a Python stand-in implements a tiny version of the same physics (gravity, bounce, friction) so you can see how the settings change the motion.

Active and passive

Select an object, open the Physics tab (the orbiting-circle icon) and click Rigid Body. Set Type:

  • Active: moved by the simulation (a falling ball, a brick).
  • Passive: does not move by itself and acts as an obstacle (floor, wall). A passive body can still be animated, and then it pushes active bodies (a moving paddle).

Press Space to play the timeline and watch the active objects fall. Starting at frame 1 matters: physics simulates forward from the Start Frame of the cache, so scrubbing backwards or jumping may give odd states. Return to frame 1 to reset.

For many objects, select them and use Object > Rigid Body > Add Active or Add Passive, or Object > Rigid Body > Connect to join pieces with constraints (breakable joints for demolition).

Settings that change behavior

In the Rigid Body panel:

Setting Meaning
Mass Kilograms. Affects collisions and force response. All objects fall at the same speed in a vacuum, but heavy ones push light ones
Dynamic If off, the object stays kinematic
Animated The object follows its keyframes but still affects others
Friction 0 = ice, 1 = rubber. Controls sliding
Bounciness (restitution) 0 = no bounce, 1 = perfect bounce
Collision Shape Box, Sphere, Capsule, Cylinder, Cone, Convex Hull, Mesh
Margin Small gap used by the collision shape; tune if objects float or sink
Damping (Translation, Rotation) Slows movement, simulates air resistance
Deactivate / Sleeping Lets resting objects sleep for speed

Collision shape is the biggest performance lever. A Box or Sphere is very cheap; Convex Hull wraps the object in a simple convex shape and is a good default. Mesh uses the exact surface, is slow, and should be used for passive objects only (concave floors, terrain). Active objects with Mesh shape tend to jitter.

Scene-wide settings are under Scene Properties > Rigid Body World: Gravity (default Z = -9.81 m/sΒ²), Substeps Per Frame and Solver Iterations (raise for stacks that jitter), Speed (slow motion), and the Cache frame range.

Rigid body checklist

Types Active or passive
Mass Heavier pushes lighter
Friction How much it slides
Bounce Energy kept

Start at frame 1, then press Space.

1 / 2

What the solver does each frame

Simplified, each simulation step does:

  1. Add gravity to the velocity: v = v + g * dt.
  2. Move: position = position + v * dt.
  3. Detect collisions. For a floor hit, reverse and scale the vertical speed by bounciness, and scale the sideways speed by friction.
  4. Repeat for substeps, which make fast, small objects less likely to tunnel through thin floors.
Python Stand-in: a bouncing ball with gravity and restitution

Press Run (or Ctrl + Enter) to see the result here.

Program input Β· what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

With bounciness 0.3 the ball barely hops; with 0.8 it keeps bouncing for the whole shot. Each peak is roughly bouncinessΒ² times the previous peak, because height depends on speed squared.

Friction and sliding

When an object slides, Coulomb friction limits how far it goes: deceleration is mu * g (mu is the friction coefficient). Blender multiplies the two objects' friction values.

Python Stand-in: sliding distance from friction

Press Run (or Ctrl + Enter) to see the result here.

Program input Β· what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Low friction means a puck on ice; high friction stops the object quickly. Set friction on both the object and the floor.

Baking the simulation

A rigid body simulation is stored in a point cache. Open Scene Properties > Rigid Body World > Cache, set Start and End, then click Bake. Baking locks the result: you can scrub, render on a farm and get the same output every time. Free Bake clears it so you can change settings.

To turn the simulation into ordinary keyframes (for export or hand-editing): select the objects and use Object > Rigid Body > Bake To Keyframes. Choose the frame range and Step. Now the objects have regular keyframes (Keyframes) and the physics is no longer needed; you can remove rigid body from them.

Determinism rule of thumb: always bake before rendering an animation, otherwise a render with several machines or a restart can differ.

Workflow for a collapsing tower

  1. Model the bricks (bevel the edges slightly, because sharp edges make unstable stacking).
  2. Select all, Add Active; make the floor Passive.
  3. Set Collision Shape to Box for bricks, mass about 2 kg.
  4. Raise Substeps to 20 and Solver Iterations to 20 if the stack jitters.
  5. Use an animated passive sphere (Animated on, keyframes for movement) as the wrecking ball.
  6. Bake, then check from the camera (Camera and Render Output).
flowchart LR
  M["Model objects"] --> R["Add rigid bodies"]
  R --> S["Set shape, mass, friction"]
  S --> T["Test at frame 1"]
  T --> B["Bake"]
  B --> K["Optional: bake to keyframes"]

A reliable physics workflow.

Common mistakes

  • Giving the floor an Active type: it falls away with everything else.
  • Using Mesh shape on active objects (slow, jittery).
  • Scale not applied (Ctrl+A > Scale): collision shapes do not match.
  • Starting objects intersecting each other: they explode apart.
  • Changing frame while the cache is partly baked.

Check your understanding

Quick check Β· 4 questions

of 4 answered You scored / 4 Β· perfect!

  1. 1. Which rigid body type should a floor use?

    A passive body does not move by itself but still collides with active objects.
  2. 2. Which collision shape is the best default for many active objects?

    Simple convex shapes are fast and stable. Mesh shapes are slow and best only for passive bodies.
  3. 3. What does baking a rigid body simulation do?

    The bake saves every frame of the simulation in the point cache.
  4. 4. A ball with bounciness 0.5 hits the floor at 4 m/s. About how fast does it leave?

    Restitution multiplies the speed, so 0.5 x 4 = 2 m/s.

Summary

  • Rigid bodies are Active (simulated) or Passive (obstacles); settings are mass, friction, bounciness and collision shape.
  • Substeps and solver iterations improve stability; simple shapes improve speed.
  • Always simulate from frame 1 and bake the cache before rendering.
  • Use Bake To Keyframes to hand the result to an ordinary animation.

Next: Particles and Hair