Tracking some LEO objects with https://hackage.haskell.org/package/orbits

It's a first time I used units to catch errors. Good: converting SDL ticks to SI and "deconverting" kilometers to scene space. Bad: I still managed to put Sun mass instead of Earth's and got wild orbital periods.

A few more 🛰 around a sphere I haven't been able to properly fake in 2D 🌐

This doesn't look right. Those are all 45°-inclined objects at even longitudes. Where are their above-the-equator bits? 🤔

RenderDoc 1 : depth issues 0

linear 1 : geomancy 3

Simple directional lighting makes things look normal

Cubemapping unit spheres is easy

Just one more turn...

https://ldjam.com/events/ludum-dare/47/orboros

You'd think living in a 3-star world would be difficult? How about 4?

https://math.ucr.edu/home/baez/week234.html

Your calendar will get seriously complex in this 28-sun world.

http://tuvalu.santafe.edu/~moore/gallery.html

apecs-shmup vulkan rewrite in progress...

New vulkan-setup example with apecs:

https://gitlab.com/dpwiz/vulkan-setup/-/tree/master/examples/apecs-shmup

Progress has been made

> Reading from MIDI controllers should not be too difficult.

https://gitlab.com/dpwiz/PortMidi-simple

I've got you baby

Carefully-ish balancing the scene

The physics of space war:
how orbital dynamics constrain space-to-space engagements

https://www.gwern.net/docs/radiance/2020-reesman.pdf

> Because the way things move in space is not intuitive to most of us, it is important to take the time to understand what makes the space domain unique if we are to understand the practical constraints on space-to-space engagements. Five key principles have been presented here: satellites move quickly, satellites move predictably, space is big, timing is everything, and satellites maneuver slowly.

Distilled new Vulkan example into a fresh playground to try those fancy setup routines and multithreaded frame recycling.