Devlog — 2026-10-09

A forest clearing now runs at 60 frames per second in the browser, with a creature walking across it. The world is painted in gouache and light; the characters are cel-shaded.
A frame takes 6.2 ms of GPU work at the median, 8.4 ms at worst over a 60-second camera path. 0 of 3,600 frames went over the 16.7 ms budget. The same look rendered as a still took 27–29 ms. In motion, drawn at half resolution and temporally upscaled, it runs more than four times faster.
A planted foot slides 0.53 mm at most. The creature bones keep their lengths within 2.2e-5 m. Rendering the creature costs 0.19 ms.
A small edit appears 57 ms after saving, 87 ms in the browser. A structural edit takes 1.7 s. The runtime is 91.2 KB. No shader code, JavaScript, or unsafe code was written by hand.
The great tree was art-directed with drag edits. The trunk thickened twice, each landing within 0.03 mm of the target. A horn drag was refused because it would have moved the head.
A separate experiment asked how to author whole floors. The author draws a 1 km² map of landmarks, sightlines and an old road. A 900-year simulated history grows around it. An interest check scores the result.
In the first round the history swallowed every opening the map drew. 55.4% of the walkable map was dead: nothing there draws the eye. All five sightlines failed. Every opening needs a keeper still at work when time freezes: grazing, people, bare rock, water, a recent event.
Floors need 2 to 5 km² of authored space, set by how far a place can be seen. The history bakes to 0.6 MB per km². Single-precision coordinates are 1 m wrong after a minute walk at 10 km, so endless floors need tile coordinates.