Voxel Space lineage · Python + Numba

VoxelStrike

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.

Flyable machines
Battlemechs
Weapons
Missions
Voxel models
Destructible props
Biomes
World presets
Trailer Real gameplay, filmed on the same GPU render path the game ships with. Every shot is a live session, cut to its own score.

In motion

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.

The fleet machines

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”.

RotorcraftFlown on collective and cyclic, with a real rotor model behind them: spool-up, ground effect, retreating blade stall, and a power curve with a minimum-power speed in the middle of it.

Fixed wingEach wing is a 3-DOF point-mass model. Banking tilts the lift, so you pull back to turn. A V-n limit, the envelope of speed against load, means a slow aeroplane cannot pull the g a fast one can.

GroundEach body rides on springs over four wheel stations. A track bridges a hollow rather than dropping into it, and the hull steers while the turret turns independently.

SeaShips float by displacement, and the rudder only works while water is flowing past it. You look out from the bridge, over your own bow.

Battlemechs machines

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.

Every silhouette, one camera distanceEach machine turns at the same distance from the same camera, so the sizes are their real proportions against each other rather than each fitted to its own frame.

Arsenal weapons

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.

Ordnance round models

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.

Opposition unit types

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.

Campaign missions

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.

Worlds presets

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.

Every preset, from aboveThe generator’s own colour map for each world, resampled so a 4096² landform fits in one picture. A pinned seed means the same preset always shows the same world. The counts are what the generator reports it actually placed.

Biomes places

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.

The world’s objects models

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.

City blocksThese are the building styles a city is stamped from. They are baked into the terrain itself, so the raycaster draws them in true 3-D and a bomb can take the corner off one.

Settlement & landmarksThe landmarks you navigate by and the buildings a village is made of: a church tower, a windmill, a water tower, a radio telescope. Every one of them can be brought down.

Street & yardWhat fills the space between the buildings: parked traffic, the trains on the line, signs, machinery, boulders that roll, and farm clutter. These objects are small and numerous, and none of them is invulnerable.

PeopleCrowds stand in a settlement’s streets, at the street level of the building they belong to. Each person is dressed from a palette, so one model and the module behind it give the whole crowd.

PickupsCrates left at gas stations, depots and buildings, collected by driving or walking over them. They hold fuel for speed, armour plate, a field kit, ammunition, a weapon, or a flare that calls in two friendly machines.

Flora species

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.

Engine

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.

Destructible terrain
Every explosion digs a real crater into the heightmap and exposes the rock layers underneath. The digging runs as one fused, parallel step, so a bomb costs about half a millisecond instead of a cost that grows with the square of its radius.
Damage down to the voxel
A hit is recorded in the model’s own frame, so the mark stays on the plate it struck while the machine yaws, banks and walks. It leaves a charred hole with a molten rim, and on a battlemech the limb itself comes off.
One firing solution
The HUD’s aiming mark (the lead pip), the gun convergence and the regression tests all read the same solver. The predicted impact therefore cannot disagree with where the rounds land.
Guidance you can beat
Missiles lose energy in a hard turn. They can be pulled past what their seeker’s gimbal can follow, lose lock behind terrain, and chase flares or chaff. The same rules apply to what you fire and to what is fired at you.
Procedural audio
There are no sound files. Every engine, weapon, impact and collapse is synthesized: a voice for each vehicle, a footfall for each machine, and a hit sound that tells you whether your round went through the armour or bounced off it.
Streaming worlds
The world is endless, generated in worker processes that run ahead of where you are flying. Its settlements, forests and destructible buildings depend only on their position, never on the route you took to reach them.

The numbersread from the source at build time

Every figure here is read out of the game when the data is built. None of it is copied in by hand.

Voxel modelsevery model the game can build
Destructible propsone registry entry each
Flyable machineshelicopters, jets, armour, ships
Battlemechseach a distinct rig
Weaponsbalanced on damage rate, range and utility
Enemy typeswith their own sensors and intent
Missionsplus free flight and sandbox
Biomespalette, climate and planting per entry
World presetsstreamed or authored
Engine modulesin game/
Lines of enginePython, JIT-compiled where it is hot

How it is kept honestCorrectness is gated by a battery of headless checks that drive the real game session, rather than by unit tests wrapped around it.

A dozen of those checks, sampled from across the battery:

What was done lastTaken straight from the commit log. The subject lines in this repository are written as statements about the game, so the log doubles as a changelog that nobody has to keep by hand.