Game (examples/MissileCommand):
- Trails rewritten as an analytic flight path (pos is a pure function of
distance travelled): paint and erase replay the exact same pixels, so
blinking trails leave zero residue. Smart bombs wiggle (S-curves) with
deterministic paths; erase band widened to a symmetric 7px so the ±1px
Bresenham slope jitter between paint/erase endpoints can never leak
paint ink (verified zero strays across dense frame captures).
- 2600 look: bright steady missile head dot with a flashing trail
(shared blink phase), trails vanish on death/impact; AA rockets stay
moving dots.
- Arcade rules: bomber planes (100x mult) and satellites (250x mult)
cross the sky dropping bombs; max 3 city kills per wave; bonus cities
at every 10k kept in reserve and deployed between waves; battery
silos rebuilt and replenished at each wave start (they no longer stay
dead across levels); center battery fires fast rockets, sides slow.
- Wave-start attack alarm (four falling tones, once); volume U/V/M with
OSD; sound task zeroes the I2S DMA ring when the queue drains so a
finished sound's tail no longer loops forever.
Emulator:
- --wave N flag to skip straight to a wave for quick testing
- --dump-interval N rolling frame captures (seq%05d.bmp)
- shim: uxQueueMessagesWaiting added
- Enemy missile trails now drawn 3px thick via drawThickLine() with a
bright head dot (white) that flashes against the trail color every
couple of frames, like the Atari 2600
- eraseBombTrail() uses a thicker erase band than the draw (5px, 7px for
wigging smart bombs) plus a 2px tip circle, so no trail residue is
left behind when a missile dies or impacts