Voxel Space lineage · Python + Numba
A combined-arms combat sim. You can fly helicopters and jets, drive armour, take a warship to sea, or stand a hundred-tonne battlemech up out of a tank, all over terrain you can dig holes in. It is built on the per-column raycaster the Comanche games used, which draws the world one screen column at a time, and its busiest loop is JIT-compiled to machine code and spread across every core.
How it’s built: the engine write-up →
These clips come from the real render path. The terrain, everything in the world and the HUD all
go through the same Session.draw the game runs. Each clip is stepped at a fixed rate over a pinned
world, so every rebuild produces the same clip.
Each class runs its own flight model. No machine is simply a step up from another: each one trades a strength for a weakness, so speed is paid for in armour, payload or reach. The bars are scaled against the fleet’s own range, so a full bar means “the most in the game”.
A battlemech is not a tank with a different skin. Each leg has two segments and a real knee, and the length of the stride is what actually carries the machine forward. A waist lets the torso turn independently of the legs, and limbs come off where you shot them. They are shown walking, because standing still hides all of that.
Damage is worked out from the weapon’s damage type against the target’s armour class, so the best weapon depends on what you are shooting at. A guided round also carries a guidance type, which decides what can defeat it, and a rule about what it will engage at all.
The model a weapon puts in the air is derived from that weapon’s own fields, so an AMRAAM and a Hellfire look different because they are different weapons. A lobbed rack round is small and boxy. A round that must fly a long way cruises on a wing, and an anti-ship round skims the sea. A radar hunter gets long anti-radiation strakes, anything very fast becomes a slim interceptor needle, and the rest are short, fat anti-armour rounds. Each card lists the weapons that fly that shape.
Every enemy unit acts on an intent rather than a script. It closes in, holds a firing position, works round your flank, or breaks contact when it is losing. What the difficulty setting actually changes is how readily it does each of those.
Each mission is a multi-stage operation, briefed in the cockpit rather than on a cutscene screen. A spoken controller calls out each stage as it happens.
Terrain is generated from a set of numeric dials rather than built by hand, so each world is simply one setting of those dials. The streamed presets let the dials drift slowly across the map. That is what lets one continuous world hold badlands, an alpine spine and an atoll without repeating.
Each biome is a single registry entry, with its palette, climate window and planting density stored as fields. That is why adding a new place means editing one table instead of forty. The swatches are that entry’s actual ground, rock and accent colours. The climate window is the band of temperature, moisture and elevation in which the world decides you are standing in that biome.
Every one of these is a voxel model you can shoot, crash into or bring down. Each has one registry entry holding four facts: how much damage it takes, whether an aircraft collides with it, what it is made of, and how it comes apart. The material decides the sound, the colour of the debris and the dust. The tags on each card are those fields. Within a group, every model is rendered at the same camera distance, so the sizes are their real proportions against each other.
The world is not planted with one oak repeated. Each species is a base model plus procedural re-rolls, and each strip shows those rolls side by side at the same camera distance. The variation you can see is the variation the forest has. Which biome plants which species, and how densely, is a field on the biome entry.
The terrain is drawn by casting a ray up each screen column over a heightmap. That loop is JIT-compiled with Numba and runs across every core. The GPU path casts the same height field once per pixel instead, which is what lets you look straight down over a city and see buildings rather than a tilted map. The full story, in plain language, is in the engine write-up.
Every figure here is read out of the game when the data is built. None of it is copied in by hand.
A dozen of those checks, sampled from across the battery: