driveControls.inputMap

Throttle, steering, brakes, boost, recover and camera zoom for something the player drives.

The map belongs to the vehicle group and stands down player while it is live, so walking and jumping go quiet for exactly as long as somebody is driving. Activate it when a driver takes the wheel and release it when they get out — the vehicle outlives the drive, so awake / onDestroy are the wrong hooks for it.

• throttle: one signed axis: positive drives forward, negative backs up. W / S, the two triggers, or the vertical half of the touch stick.
• steer: one signed axis: positive turns right. D / A, the left stick's horizontal travel, or the horizontal half of the touch stick.
• brake: a button. Space, the south face button, or a lower-right touch button.
• handbrake: a button that locks the rear wheels. Ctrl, the east face button, or a lower-right touch button.
• boost: a button for more drive and a higher top speed. Shift, the north face button, or a lower-right touch button.
• recover: a button that sets a vehicle that rolled over back on its wheels. R, the select button, or a lower-right touch button.
• zoom: how far the camera trails, in wheel notches. The scroll wheel, the shoulder buttons, or a pinch. The walking scheme's own zoom stands down with the rest of the player group while somebody drives, so the vehicle carries it.
• interact: a button. E, the west face button, or a lower-right touch button: the same key that gets a driver in gets them out.

The VehicleController component reads every one of these and drives a car built from WheelColliders; Zin.controllers.vehicle reads them for a driver you write yourself.

Throttle and steer are the two halves of ONE left stick on a phone, so a driver's thumb works both from a single control.

Zin.scheme.live() reports this map's group, what it suppresses, and each live map's suppressedBy — the answer to "the walk controls are live and nothing happens".