Took quite a few lines of code to achieve this level of minimalism.

First usage of the Pause button AKA "Show-off toggle" - to show off new trajectories with landing points and less hardcoded "empirical constants".

Periapsis for non-elliptic trajectory, calculated for free while `unfoldr`ing momentum over time.

Orbiting 101

Prograde "forward" burn (blue): increase speed, raise/widen orbit and leave.

Retrograde "reverse" burn (red): slow down, lower/tighten orbit and fall on a body.

Burning at periapsis moves apoapsis (opposite point) directly towards/away wrt. planet center.

The orbiter always wants to crash onto something. So your goal is to miss the surface while falling at it.

With a healthy dose of existential quantification and runtime type reflection it is now possible to create delayed actions. And that, other than opening a hells gate into concurrency bugs, enables animation chains. Like this new warp-in effect I've always wanted.

Best of all, this doesn't contain any SpaceMar-specific code. And so it goes straight into apecs-gloss-starter game template.

No game is really complete without a proper intro.

The beta is near, I need just a few more fixes to finish the scene transitions.

The scene loop is complete. Too tired to make a release. 😩

A sound decision! Looks like there's (at least) one callback cleanup bug lurking between transitions.

A stateful concurrent salute to celebrate (somewhat) stable async actions with iterations and cancellation.

This should provide a foundation for all kinds of FX, animations and actors. 🔊🎆🤖

Steam Remote Play makes for a decent Portable testbed.

New control component testing in progress. All personell advised to hide in a secure location.

Experimental sdl2-ttf to gloss bytewrangling.

Meanwhile, on the UI side...

Not my best trading session