Vantage

There are no maneuver nodes, no apogee or retrograde markers, and no n-body physics anywhere in the game. That is a deliberate boundary, not a missing feature: real orbital mechanics would put the skill in planning a maneuver in advance, and the skill this game is built around is reading a live pass and timing a release inside a moving window. Orbit adjustment runs on an arcade thrust model instead, direct prograde and retrograde control on one axis and plane change on another, so the ship handles like something you fly rather than something you plot.

The shader work goes into the planet, not the ship. The planet is three concentric layers, a PBR surface, scrolling translucent clouds, and an additive fresnel atmosphere shell, with sun shafts, a city-lights pass on the night side, and ocean glint under direct light. The ship beside it is one loaded model on a stock standard material, plus a single emissive sphere at the tail bright enough to clear the bloom threshold. That allocation follows from what the camera actually looks at: the ship is a small silhouette against a planet that fills most of the frame, so the planet is what has to hold up under scrutiny.

The player places drops; the units that come out of them act on their own, running a fixed loop between the landed pod and a worksite. Nothing in the interface selects a unit or gives it an order: the game is about reading the planet and choosing where and when to commit a drop, not about micromanaging what happens after it lands. Resistance is tracked per region rather than behind one global alarm meter, the alternative the design rules out by name, so pushing one region does not raise the temperature everywhere at once. Discovery follows the same regional logic: tracker density scales with how deep into a region you push, with edges left lighter than the interior.

Textures, the region and terrain data maps, the minimap, and surface picking all share one equirectangular coordinate space, latitude and longitude mapped straight to UV. A shader samples the same region-ID and terrain-type texture that CPU code samples for picking and gameplay, so there is one authoritative map instead of a render copy and a logic copy that could drift apart. The minimap is a flat rendering of that same texture with a sinusoidal ground track drawn over it, not a separate asset.

Damage that isn't repaired at a station leads to atmospheric entry and burn-up with no escape pod, so a run ends and stays ended. Texture quality runs through two separate checks, not one. A tier, showpiece, phone, or floor, is chosen before anything initializes, from what the device looks like: pointer type, screen size, memory. That choice decides texture resolution along with tessellation, antialiasing and the post chain, and changing it takes a reload rather than a live toggle. A second check runs after the renderer exists, once the real texture limit is known, and clamps to the smaller texture set when the device can't sample the larger one; skip it and the result isn't a slow planet, it's a black one. The hosted build ships a curated subset of the full baked texture library rather than the whole set: a deployment decision to keep the deployed payload smaller, not a change to how the tiers themselves are chosen.