How Does BeamNG.drive's Soft-Body Physics Work?

Updated

BeamNG.drive simulates every vehicle as a network of nodes (mass points) connected by beams (springs), all solved in real time. Instead of animating a pre-built crash, the game calculates how force travels through that network, so deformation, weight transfer, and damage emerge from the simulation rather than being scripted. That is the core reason crashes feel visceral and vehicles behave differently depending on how and where they are hit.

The two building blocks: nodes and beams

The BeamNG physics engine treats a vehicle as a soft body rather than a rigid one.

  • Nodes are mass points placed throughout the vehicle. Each one carries weight and moves independently.
  • Beams are springs that connect nodes to each other. They resist stretching, compression, and bending to varying degrees.

Because the body is a mesh of these points and springs instead of a single solid shape, it can flex, crumple, and tear. A rigid-body model can only move and rotate as one piece; a soft-body model can bend at every connection, which is what allows a fender to fold while the chassis stays roughly intact.

Why every component is simulated

The engine's design goal is that each part of a vehicle is simulated in real time, not approximated with a single collision shape. In practice this means:

  • The frame, panels, suspension, and other structures each contribute their own nodes and beams.
  • Forces applied at one point propagate through the network to the rest of the vehicle.
  • Damage is a local result: beams that exceed their limits break or deform, and the surrounding structure responds.

This is why two crashes that look similar can produce different outcomes. The impact point, angle, and speed determine which beams fail first, and everything downstream follows from that.

How crashes and the damage model stay accurate

The accuracy comes from the same mechanism, not from a separate damage system bolted on top:

  1. A collision applies force to the nodes at the contact area.
  2. Connected beams stretch or compress beyond their thresholds.
  3. Beams that fail stop holding their nodes together, so the structure separates or folds.
  4. The resulting shape is whatever the remaining beams can support.

The engine describes this as an "incredibly accurate damage model," and the reason is structural: the visible damage is the physics state. There is no separate animation playing a dent; the dent is where the nodes ended up.

Why it feels real

Realism here is a side effect of simulating the whole body continuously rather than switching to a canned reaction at the moment of impact. Weight, momentum, and structural stiffness all feed into the same calculation, so:

  • Heavy vehicles and light vehicles respond differently to the same hit.
  • Off-center impacts twist the body instead of just pushing it back.
  • A weakened structure behaves differently on the next impact.

The visual result and the physical result are the same thing, which is why the crashes read as convincing rather than as effects.

What this means if you are deciding whether to try it

If you want a driving or crash simulation where outcomes are computed rather than scripted, the soft-body approach is the feature to evaluate. If you mainly want predictable, repeatable arcade handling, the same flexibility that makes crashes realistic also makes vehicle behavior harder to predict. The trade-off is inherent: more simulated detail means more variation between runs.