Quick answer: Let resting bodies sleep, reduce the number of active dynamic bodies, simplify colliders, and tune solver iterations so physics scales with many objects.

Laggy physics with many bodies is too much active simulation. Sleeping and simplifying fix it. Here is how.

How to fix it

1. Let bodies sleep

Resting rigidbodies should sleep so they stop consuming solver time. If sleeping is disabled or bodies are kept awake by tiny forces, all of them simulate every step. Enable sleeping and tune its thresholds.

2. Reduce active dynamic bodies

Convert distant or settled objects to static, pool and despawn debris, and cap how many dynamic bodies exist at once. Fewer active bodies means less broadphase and solver work.

3. Simplify colliders and solver

Use primitive colliders over mesh colliders, reduce unnecessary contacts via collision layers, and tune solver iterations to the minimum that stays stable, so each step is cheaper with many bodies.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.