[doodlewind]

Games had no sound: the engine had no audio, and every app would have had to invent its own. This makes sound a runtime capability, the same everywhere.

Game side — packages/gameplay/src/audio.ts:

audio.preload(["assets/sounds/shot.ogg"]);                       // in setup: decoded ahead
audio.play("assets/sounds/shot.ogg", { at: muzzle, pitch: 1.03, falloff: 8 });
audio.play("assets/sounds/fire.ogg", { at, loop: true, key: "fire" }); audio.move("fire", at); audio.stop("fire", 0.5);

A sound is a file of the game's package; the listener is the frame's camera (nothing to send).

Engine side — renderer/src/audio (feature audio, on by default):

• decoding by Symphonia (WAV, Ogg Vorbis, MP3, FLAC): the same samples on every platform;
• placing (mix.rs): level to falloff, then falloff / distance, fade out 100–120 m; equal-power pan capped at 80 %; a low pass with distance and behind;
• mixing: 48 voices, 8 copies of a file, ramps, fades, soft limiter, app volume, pause;
• the device (out.rs, the only per-platform part): cpal on macOS / iOS / Windows; ALSA (Linux, Steam Deck) and AAudio (Android) loaded at run time, so nothing new is linked there.
• threert-render play plays a game's sound.

Browser — the three.js view plays the same messages on Web Audio with the same numbers (tools/three/audio.ts; tools/three/test/audio.test.ts holds it to mix.rs).

Docs — docs/RUNTIME.md "Sound" is the contract.

Tested: unit tests (mixer, decoder, Audio, gameplay posts, page parity); threert-render play on macOS (Core Audio, 48 kHz); in the ThreeRT clients on an AYN Thor (AAudio stream, usage GAME, released in the background and reopened on return) and a Steam Deck (ALSA → PipeWire stream), and the three.js page in Chrome (both formats fetched and decoded, no errors).

🤖 Generated with Claude Code