Blender Rigid Body Physics Tutorial: Simulating Collisions, Mass, and Wrecking Balls

There’s something deeply satisfying about watching a tower of blocks collapse in slow motion - especially when you built the tower and you’re the one controlling gravity. Blender’s rigid body physics engine lets you do exactly that, turning static models into dynamic simulations that react to forces, collisions, and momentum. Whether you’re building a Jenga tower, a wrecking ball demolition, or just dropping a Suzanne monkey onto a plane, understanding rigid body physics opens up entire categories of animation that would be impossibly tedious to keyframe by hand.

BornCG’s tutorial on simulating rigid body physics in Blender 2.8 remains one of the most accessible entry points to this powerful system. The instructor walks through everything from basic object properties to building complex chained simulations, with a capstone project that makes the abstract concepts tangible. If you’ve ever wondered why your physics objects behave like they’re underwater or why that stack of cubes refuses to fall over naturally, this is the tutorial that clears up the confusion.

Understanding Active vs. Passive Objects

The fundamental distinction in Blender’s rigid body system is between active and passive objects. Active objects are affected by gravity and can be pushed around by collisions. Passive objects stay put - they act as immovable obstacles, floors, walls, or constraints that active objects bounce off.

To add an object to the physics simulation, select it and use Object > Rigid Body > Add Active or Add Passive. You can also access these controls through the Physics tab in the Properties editor, where you’ll find sliders for mass, friction, and bounciness. The default mass is surprisingly light - around 1kg - so heavy objects like wrecking balls need their mass cranked up to 10kg, 20kg, or higher to behave convincingly.

One critical workflow habit that separates smooth physics work from frustrating debugging sessions: always return to Frame 1 before editing objects in a simulation. Blender caches physics calculations as you play through the timeline, and editing objects mid-cache produces unpredictable results. The cache gets confused, objects teleport, and you end up clearing and rebaking more than necessary. Get in the habit of hitting Shift+Left Arrow to jump to frame 1 before making any changes.

Collision Shapes: Speed vs. Accuracy

Blender offers three primary collision shape types, and choosing the right one matters for both simulation speed and visual accuracy:

• Convex Hull: The default. Blender wraps your object in a simplified “shrink-wrap” collision mesh that approximates the shape. Fast to calculate, works well for most objects.
• Box: The simplest option - just a rectangular bounding box. Use this when you need maximum speed and don’t care about subtle shape matching.
• Mesh: Uses your actual geometry for collisions. The most accurate but slowest option. Essential for objects with concave shapes or holes that convex hulls would fill in.

For a wrecking ball hitting a tower of blocks, convex hull works fine for the ball and most blocks. But if you’re simulating something with interior detail - a cup catching marbles, for instance - you’ll need mesh collision on the cup to prevent the marbles from ghosting through.

Building a Wrecking Ball: Practical Application

The tutorial’s capstone project involves building a wrecking ball on a chain that swings into a Jenga-style tower. This exercise demonstrates several practical techniques:

Chaining objects: Each chain link is a separate active rigid body, positioned and duplicated to form the chain. The sphere at the end gets joined to the final link using Ctrl+J, creating a single physics object with the ball’s mass.

Origin point placement: After joining objects, use Set Origin to Geometry so the physics system knows where the object’s center of mass is. Incorrect origins cause objects to rotate around the wrong point, producing that weird “wobbling around an invisible pivot” effect.

Mass and momentum: A 20kg wrecking ball behaves very differently from a 1kg ball. Higher mass means more momentum, which means the tower actually falls over instead of just wobbling. The tutorial demonstrates this by letting you compare different mass settings in real-time.

Simulation Speed and Scale

Here’s a gotcha that trips up even experienced Blender users: scene scale affects physics timing. Blender’s default grid is calibrated to real-world meters. If you build a scene with 10-meter-tall blocks, the simulation looks like slow-motion because gravity is pulling those massive objects downward at 9.8 m/s² - but the scale makes them look like they should be small.

The fix lives in Scene > Rigid Body World settings. Increase the speed multiplier - try 2x or 3x - and the massive objects will behave like appropriately-weighted smaller objects. This is the inverse of the filmmaking trick where miniatures are filmed at high frame rates and slowed down to look full-sized.

Viewport playback may lag on slower computers, but note that rendered output plays at correct speed regardless of viewport performance. If your viewport stutters during playback but the final render looks smooth, that’s normal - the physics calculation happens independently of the viewport refresh rate.

Baking and Converting to Keyframes

Once you’re happy with a simulation, you need to lock it down. Bake Current Cache in the Rigid Body World settings saves the simulation data so it won’t change if you accidentally nudge an object. Think of it as freezing the physics in place.

For more advanced workflows - exporting to game engines, editing specific frames, combining physics with hand-animated elements - you can Bake to Keyframes. This converts the entire simulation into standard Blender keyframes that you can edit in the Graph Editor, combine with other animations, or export freely.

Warning: Baking to keyframes generates a lot of data. On complex scenes with hundreds of physics objects, this can crash Blender or lock up your system for minutes. Save your file before attempting this on anything substantial.

Recommended Gear for This Tutorial

Watch the Tutorial

Level Up Your Blender Setup

Bottom Line

Rigid body physics in Blender rewards methodical setup and punishes sloppy workflow habits. The difference between a frustrating simulation and a satisfying one often comes down to small details: returning to frame 1 before editing, setting appropriate mass values, choosing the right collision shape, and understanding how scale affects timing.

The wrecking ball project demonstrates why this system matters - it’s the kind of complex, interdependent animation that would take hours to keyframe manually but emerges naturally from physics. Once you internalize the workflow habits, you’ll find yourself reaching for rigid body physics whenever you need objects to interact, collapse, scatter, or collide.

Start with simple drops. Work your way up to towers and chains. Bake your caches when you’re happy. And always - always - save before baking to keyframes.