Why we started building a driving sim in a browser
Episode 1 of our Seat Time build journal: three cars, a caught slide followed by a spin, and the Physics Lab we built to keep failures visible.
Lab notebook posts about “build-log”.
Episode 1 of our Seat Time build journal: three cars, a caught slide followed by a spin, and the Physics Lab we built to keep failures visible.
Our browser sim needed a definition of ‘sim-grade’. Failing tests and a tyre port gave us better questions—and a score we had to withdraw.
Our browser sim passed its audio checks and still sounded artificial. A same-day detour through synth samples led us to recorded engines.
Seventeen hairpin misses, a 41-byte margin, and kart tracks we traced then reshaped: building Seat Time’s roads in October 2026.
Our rain retained almost all its dry grip on Haruna. We traced three drainage causes, stopped parked-car creep and checked our models against outside data.
We renamed our browser driving game, split racing from the life-sim loop, and found merged work that had never reached main.
A missed release exposed the gap between merged and live. We rebuilt Seat Time’s release checks around real failures.
We asked where our car numbers came from. The answer brought 147 corrections, estimated mass layouts, and stiffer frames that barely changed handling.
Our G923 accepted force commands, but we felt nothing. Building browser wheel support meant tracing pedals, steering ratios and missing force.
Seat Time's first-load cuts: translation text, car models, audio, and the server imports that kept rebuilding the circuits.
Our tyre texture passed its spectrum checks and felt wrong on the wheel. A week of reversals taught us where measurement ends and driving begins.
Our small learned driver passed a drift course on shallow slides. First we repaired the tyre; then its results exposed an open scoring gap.
Our physics checks agreed with themselves. Fairer comparisons exposed reference mistakes, missing wheel reaction and a tyre force bypassing the springs.
Five weeks of our browser driving sim: 516 merged pull requests, delivery failures, decisions at the wheel, and the complete episode index.