Skip to content

Collisions and Rings

inksong edited this page Nov 8, 2026 · 1 revision

Collisions and Rings

Since 0.5 every simulator has a collision volume and course rings are solid.

Body Shape
Aircraft Sphere of radius 0.15 m
Ring Torus with a 0.03 m tube
Ground Plane; crash thresholds 2.5 m/s vertical, 3 m/s horizontal, 60° tilt

All local simulators are stepped together at 250 Hz, and each step is swept against the other simulators, the rings of the active course and the aircraft of LAN peers, so a fast aircraft never passes through another.

Contact rule

Closing speed Result
2 m/s or more Both aircraft crash
Below 2 m/s They bounce with a restitution of 0.4; the off-centre push upsets their attitude, which a pilot or a program can recover
Below 0.2 m/s Resolved silently

A shot-down aircraft keeps its volume while it falls and can still hit others. Two wrecks do not collide.

Rings

A ring pass counts only when the whole aircraft sphere clears the tube. A pass that scrapes the tube still counts and is reported as ring_touch (the ring flashes white). A slow graze bounces off; a fast hit crashes.

What programs and agents see

  • obs.collision: the last contact within 1 s (t_ago, with, v_rel, normal).
  • closing on every entry of obs.contacts.
  • Events collision (a, b, point, v_rel, crashed, kind, remote) and ring_touch; the crashed alert carries reason_code (ground, collision, shot_down), the point and the impact speed.
  • The evaluator writes collision and crash events into replay traces.

Across the LAN

Each terminal judges contacts of its own aircraft only. On a contact it applies the response to its own aircraft and sends COLLIDE to the owner of the other one. The owner checks it again before applying it:

  • the contact is at most 0.3 s old;
  • both aircraft are within 0.6 m on its own view;
  • at most 4 per second per peer aircraft, and once per pair within 0.5 s, unless the later contact is a crash;
  • the peer aircraft has a continuous track: its velocity is held within 1 m/s of the track and capped at 20 m/s; a jump it could not have flown makes it untouchable for 0.5 s.

A rejected COLLIDE changes nothing, so no terminal can crash another terminal's aircraft by claiming a collision.

Visual effects

Shoot-downs, rams and hard ground impacts (6 m/s or more) throw voxel explosions: a white-hot core, then voxels flying out that cool from white to red to grey, and a dust ring on the ground. Light contacts throw white and red sparks, and the chase camera shakes slightly when they are close. The Collision volumes layer (layers menu on the stage) draws every aircraft's sphere. Under reduced motion, effects become still markers.

Clone this wiki locally