DEVLOG | May 5, 2026
Double crash smoke diameter and smoke palette fade
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. 25 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 issue, smoke, damage, server.
What moved
implementation moved through enable postgres tls for server, double moving smoke diameter, make smoke rise visibly, lower first person tracer origin, double crash smoke diameter, scale smoke size units, remove smoke diameter multiplier, and restore smoke palette fade.
What I learned
The combat model is becoming less abstract. Hits need to be legible, not just registered, and the visible feedback has to stay tied to the underlying state instead of becoming decorative noise.
Source trail
- Local conversation signal: 67 working sessions.
- implementation f753b91: add wheel touch audio cue
- implementation 0c8d8b6: gate damaged field service
- implementation 0ab1dd1: tune directional contact radius
- implementation 18a8fdc: present damaged hangars
- implementation aed3d99: update phase 5 launch plan
- implementation 3e2686c: tune sky horizon ramp
- implementation 3711da4: add gpu renderer acceleration plan
- implementation 64e441d: add production server health config
- implementation cba5d13: containerize sgfc server
- implementation 7adadac: add headless deployed smoke cert bypass
- implementation edbced5: enable postgres tls for server
- implementation f7b1fa6: double moving smoke diameter
- implementation fa800da: make smoke rise visibly
- implementation efc8797: lower first person tracer origin
- implementation 3c11946: double crash smoke diameter
- implementation 1ed662a: scale smoke size units
- implementation bea1903: remove smoke diameter multiplier
- implementation 2c06657: restore smoke palette fade
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.