DEVLOG | April 28, 2026
Engine power and distant hangars
This was a research-and-implementation day: less about ceremony, more about tightening the shape of the thing until it behaved a little more like itself. 6 commits landed or were available locally. There was also a decent amount of local conversation around the work, but the useful part is the trail it leaves: questions asked, decisions narrowed, and a few assumptions made explicit. The center of gravity was terrain, bundle, world, airfield.
What moved
implementation moved through add structural terrain strike probes, clip river overlays to airfields, render rivers from terrain bytes, use baked airfields, fix distant hangar rendering, and recover engine power model.
What I learned
The world work is mostly about boundaries: what can be treated as reference, what needs a replacement contract, and what has to be rebuilt as new implementation truth.
Source trail
- Local conversation signal: 3 working sessions.
- implementation 170c321: add structural terrain strike probes
- implementation c30789f: clip river overlays to airfields
- implementation 28c3325: render rivers from terrain bytes
- implementation a2cd83d: use baked airfields
- implementation a83039d: fix distant hangar rendering
- implementation 8664e71: recover engine power model
The research lane stays research, and the implementation lane stays implementation. This post is a narrative summary of local work, not a publication of raw originals.