Soft-body deformation

An object is a network of nodes (point masses) linked by beams (massless springs with damping). Each step every beam applies force from its length deviation and damping, nodes integrate, and collisions push nodes. A beam whose force passes a deform threshold permanently changes its rest length, and one that passes its strength breaks, so parts detach. In BeamNG.drive vehicles are authored in JBeam: nodes have weight, beams have beamSpring (stiffness), beamDamp, beamDeform, and beamStrength. Beams do not resist bending or twisting, so cross braces are needed for rigidity, and stiff beams on light nodes vibrate or explode (the documentation's example stabilizes a structure by raising nodes from 6 kg to 7 kg). Finite-element and position-based methods are alternatives.

Visceral, readable damage. Crashes crumple metal where they hit, and the damage changes how the vehicle drives. Players experiment with crashes as much as they drive.

• node density and placement
• beam stiffness and damping per part
• deform and break thresholds
• physics step rate
• which parts are soft and which are rigid or cosmetic
• coupling of deformation to function, such as steering or engine damage

• Stiff beams on light nodes vibrate or explode, so every structure needs stability tuning.
• CPU cost per vehicle limits how many soft bodies can run at once.
• Hand-building node-beam structures for every vehicle is a large authoring cost.
• Too-soft settings make solid objects look like jelly.

• Damage changes handling, which changes driving, which causes more damage.
• Crash testing becomes its own play style and community genre.
• Deformed tires and suspension couple to grip and vehicle dynamics.

• Can node-beam structures be generated automatically from a visual mesh and material labels?
• Can learned deformation surrogates run many soft bodies at once on consumer hardware?