Every 1/360 of a second, the car on the test track is solved again from scratch: where each tyre touches the road, how hard the springs push, how much each tyre slips and grips, what the engine, clutch, gearbox and differential do, and how the whole car moves. Nothing is animated or canned. It's all physics, in plain C++ that doesn't care which game engine runs it.
This is the order of operations inside Vehicle::computeStep. Assists act first (only through real actuators: brakes, throttle, shifts), then the four stages, then a telemetry snapshot of about 130 values.
Under each tyre: 5 points across the contact patch plus 3 envelope probes ahead and 3 behind, so kerbs and pothole edges are felt before the patch reaches them. Springs, bump and rebound damping (separate slow and fast settings, like a real two-way damper), bump stops, anti-roll bars, and each wheel's own unsprung mass bouncing on the tyre's vertical stiffness. Each wheel's camber to the road comes from its geometry: static camber, camber gain as the suspension moves, caster as it steers, and the body's roll.
Slip angles build up over a relaxation length (0.45 m by default) instead of jumping, which is what makes a car feel like it has weight on turn-in. Grip comes from a Pacejka Magic Formula with load sensitivity and combined slip, scaled by camber (best leaning about 2° into the turn), tread temperature, tyre pressure, and the compound's grip on wet or loose ground.
Engine crank, gearbox input, all four wheel speeds and their longitudinal slip are solved in one implicit system, with the clutch, gears and differentials as stick/slip constraints. Up to 12 iterations per step.
Tyre forces, suspension forces, self-aligning torque, rolling resistance, aerodynamics and gravity are summed on the chassis, a rigid body with 6 degrees of freedom, which is then integrated. Aero uses the speed through the air (wind included): drag, a floor whose downforce grows as it runs lower until it stalls, and a rear wing that stalls past its critical angle. Each tread then heats from sliding and cools in the airflow.
A spinning wheel is tied to the road by the tyre's slip stiffness. That coupling settles in about 0.1 ms, far shorter than a 2.8 ms step, so stepping it forward naively explodes at low speed. The usual fixes (heavy substepping, clamping slip) change the physics. OpenRoad Dynamics instead solves every shaft, every slip and every clutch/differential constraint together, backward Euler, every step.
Unknowns per step: engine crank speed, gearbox input speed, four wheel speeds, four transient slips, plus one multiplier per active clutch, gear or differential constraint. At zero speed the slip equation becomes a spring, which is what lets the car sit still on a hill without creeping.
About 330 numbers describe one car, plus its engine torque curve. Tyre data can be generated from nothing more than a size and category (e.g. 335/40 R21, ultra-high performance).
| Tracked every step | How many | What |
|---|---|---|
| Chassis | 6 DOF | Position and orientation, linear and angular velocity |
| Each wheel | 4 × 5 | Spin, unsprung vertical travel, transient slip ratio, transient slip angle, tread temperature |
| Drivetrain | 2 + state | Engine crank speed, gearbox input speed, gear, clutch engagement, shift timer |
| Ground | 44 | Contact samples and envelope probes, with the surface's grip, roughness and micro-texture |
| Crash structure | ~110 + 380 | With realistic damage: nodes (position, velocity) and elastic-plastic beams (rest length, plastic deformation, torn); asleep, at no cost, until something is near |
| Parts | ~40 | Per wheel: toe, camber, mount offset, bend, torn off, puncture and deflation; steering offset and lock; radiator, coolant, engine temperature and damage, seizure; drag and wing |
| Telemetry | ~130 | Speed, sideslip, yaw rate, g-forces, inputs vs actuator outputs, rpm, gear, every aid's intervention, downforce, drag and stall flags, and per wheel load, slip, forces, grip used, camber, tread temperature, brake torque and lock |
The same physics, with the parts changed. Every setting is in the units a setup sheet uses, and the results come from the model, not from a lookup table.
Headless core only, single-threaded on a 2.1 GHz cloud Xeon. These numbers cover physics and ground handling, not a game engine's scene queries, rendering, audio or game logic, so they're not a promise of how many cars a game can run.
| Scene | CPU per 60 fps frame | Ground rays per frame |
|---|---|---|
| Player car: 60 Hz world × 4 substeps, 5-point contact + envelope probes, ground cache | ~0.08 ms | ~24 |
| + 16 nearby AI cars (lighter fidelity) + 300 traffic cars | ~0.43 ms | ~108 |
| + 1,000 traffic cars instead of 300 | ~0.77 ms | ~150 |
On kerbs and potholes the cached 60 Hz × 4 configuration stays within about 5–8 % of a 2,000 Hz reference, with about 4× fewer ground rays than querying directly at 240 Hz.
The core includes no game-engine headers. A host only has to answer “where is the ground under this point, and what is it made of?”. Everything else lives in the library.
| The test car: Rosser V8 | Measured in the sim |
|---|---|
| 0–100 km/h (Sport preset) | 3.81 s |
| 0–200 km/h | 9.57 s |
| Top speed | ~330 km/h |
| Mass, weight split | 1,480 kg · 42 / 58 |
| Rev limiter, gearbox | 9,000 rpm · 7-speed DCT |