Wiki / HUD

HUD

The heads-up display is diegetic - the instruments read the ship's real state - and contextual: elements surface while their situation is live and settle back when it passes, so a quiet cruise has a quiet screen without you managing it.

Screenshot assets/wiki-hud.png The full HUD in flight: velocity sphere, speed + mode chips, the keybind icon dock, a lock reticle and the corner target inset, ideally lightly annotated.

What is on screen, and when

The HUD is CONTEXTUAL: it shows you what the situation calls for and gets out of the way when it does not. Idle cruise keeps a quiet screen - the velocity sphere, your speed, the dock's few live verbs, the always-on ship markers and the status bar - and everything else arrives with its moment.

The situations and what each brings up: an engaged autopilot adds the mode chip and (for GOTO and ORBIT) the destination marker, and grows the speed chip; a combat lock adds the red reticle with its DST/CLS readout and the target viewfinder, and inverts the dock's RADAR chip; a travel lock with no combat lock brings up the target viewfinder on its own; hot weapons raise the ammo gauges and put up a railgun's bore sight; a locked docking target in range puts up the docking sight; a nearly-dry or reloading group forces the gauges up on its own; Cinematic clears the whole contextual HUD.

Show explanation

Autopilot burn - the mode chip comes up, the speed chip grows (it is the number you are flying by), and the dock lights the maneuver you are flying. GOTO and ORBIT also put the destination marker and its readout up; STOP flies without one - there is no destination to mark. GOTO and STOP also draw the predicted path, and GOTO a dim guide to its target.
Combat lock - the red reticle, its DST/CLS readout and the target viewfinder come up, and the RADAR chip inverts because the lock is the thing you would change.
Travel lock - with no combat lock held, the target viewfinder shows your travel target with its name, range and closing speed.
Weapons hot - the ammo gauges appear on your weapons and the lock readout grows. With the trigger down the reticle pulses. A hull carrying a railgun draws its bore sight.
Low ammo or reloading - a nearly-dry group (a quarter magazine or less) pulses amber and forces the gauges up on its own, even with the safety on: a dry magazine is news before you pull the trigger. An active reload holds them up the same way, with its own pulse.
A posted objective - a chip carrying the objective itself pops into the stack at the top of the screen the moment it posts, like a chat notification, and then keeps a slow breath. The chip is a notification: it leaves once you have read it - after a dwell, or the moment you open the interface.
An incoming transmission - the comms card fades in with a soft blip while the earlier transcript stays still.

Grave / tilde (or the gamepad Select button) toggles the whole display between two levels:

On - the contextual HUD above.
Cinematic - a clean screen for captures and quiet flying. Clean, not empty: see the two deliberate exceptions below.

There is no third "minimal" level any more: showing everything all the time is what made a manual detail dial useful, and the contextual rules do that job continuously instead.

Every widget still declares its kind - Instrument (velocity sphere, flight chips, autopilot marker, maneuver instruments, lock crosshairs, allegiance markers), Chrome (the keybind dock, verb cues, the component-lock panel, edge indicators, objective markers, the target inset) or Status (the fps/version bar) - and all of them clear at Cinematic.

Two surfaces carry no kind at all, and so the toggle does not reach them: a cutscene's title card, and its SKIP prompt. Both belong to a scene rather than to your instruments. Hiding the way out of a scene that is still playing would be worse than the clean frame is worth, so a capture taken during a cutscene keeps them.

Flight readouts

The flight instruments sit around the ship, not in a status bar:

Velocity sphere - an orbiting cone and shaded sphere driven by your linear velocity; white and blue in manual flight, cyan when the autopilot is flying, violet while you hold RCS fine adjust (the violet wins over the cyan). A yellow variant shows the local gravity pull, hidden in flat space.
Shell size - both spheres are drawn around your LIVE hull: the white one stands 5 m outside the furthest point your sections reach from your centre of mass, and the yellow one 6 m outside that. Fly a cutter and they hug it; fly a larger patrol gunship and they grow to enclose it. Lose the sections that were reaching furthest and they settle back in over about a fifth of a second, so a hull coming apart is never left standing through its own instruments.
Speed and mode chips - a speed readout (m/s, meters per second; see the glossary) beside the sphere, and a mode chip reading AP GOTO - BURN (verb and phase: STOP/GOTO/ORBIT and ALIGN/BURN/HOLD) only while the autopilot is engaged, NEUTRAL while you are docked and your ship does not fly the pair, or HELM FAULT while the game cannot measure your docked pair and neither ship flies it. Both park just outside the outer shell, so they move out with the hull instead of landing on it.
RCS magazine - ten violet pips one row under the speed chip, one per tenth of the RCS magazine left. The row shows while RCS is pushing, while you hold RCS input, and until a used magazine is full again.
ORBIT ring and radius spoke - while you hold an orbit, a world-space ring marks the orbit plane and a thin spoke runs from the well to your ship with the current radius.
Predicted path, GOTO guide and flip gate - while GOTO or STOP flies, a thin cyan line runs ahead of your ship along the path the autopilot will fly. The game finds it by flying the autopilot's own controls ahead of your ship for up to 30 seconds, with the pull of the dominant gravity well, so the line can curve. It stops where the leg ends or 30 seconds out, whichever comes first. GOTO adds a dim straight guide from the end of that curve to where the target is now, so a long leg still points at its target. The guide is not a forecast: the autopilot does not fly that straight line. It shows as soon as GOTO engages, from your ship, before the first forecast is ready. A ring and a FLIP <n>s countdown stand on the curve where the brake flip starts. They go once you reach the flip or the brake starts. On a GOTO they stay gone for the rest of that order, even if the autopilot plans a new flip; a new GOTO, also to the same target, shows them again. Neither line is a route plan: neither sees collisions, and nothing on them is avoided. The curve hides while the target or a gravity well moves and while you are docked; the guide stays. Both clear when the autopilot lets go.
Keybind dock - a row of icon chips along the bottom of the screen showing the flight verbs you can use RIGHT NOW, drawn from STOP, GOTO, ORBIT, CANCEL, RADAR, COMPONENT, RCS, DOCK and HELM. A verb that would do nothing at this moment is not on the dock at all, so the row grows and shrinks with the situation instead of parking a wall of dead keys under your ship. The one exception is a docked pair you do not fly: the verbs that HELM (H, reading TAKE HELM or RELEASE HELM) would give back stay on the dock, dark, and the mode chip reads NEUTRAL. While the game cannot measure the pair, the HELM chip stays on the dock, dark, and reads HELM FAULT, unless you hold the helm and can still hand it back. HELM cannot give those verbs back then, so they leave the dock until the pair measures. A verb your ship does not have stays off the dock. Each chip shows the real KEYCAP for the key that drives it plus the verb word, in full phosphor - or inverted while that verb is what the ship is doing (an engaged ORBIT keeps its chip even though you can no longer start one). A chip pulses gold when a scenario wants you to use it, and a spotlight will show a chip that has not lit up yet - that is how a tutorial points at a key before you can press it. The anchored verb cues are the same chip parked on the thing you would act on - the ORBIT keycap on a gravity well, the GOTO keycap on your aim lock.

Screenshot assets/wiki-hud-shell.png Both shells around a 360 m development stress hull: the blue velocity sphere enclosing the whole hull, the yellow gravity sphere outside it, and the speed chip parked off the outer edge.

Locks and reticles

Locks are slot-coloured: a white crosshair is your travel (nav) lock, a red reticle is your combat lock. The combat reticle carries a readout riding its right edge - range to the target (DST), closing speed (CLS) and a health bar (measured against the hull the target was BUILT with, so it falls as you take sections off and never refills) - plus a focus meter that fills as a fine-lock dwell accumulates. Lock an asteroid and the bar is simply absent: a rock has no health to draw, and how much of it is left is something you read off the rock itself. While you hold the radar gesture a hollow box shows, coloured by the slot it will land in; a white ring fills clockwise around the target while the lock-on dwell charges, and vanishes with a cue the instant the lock snaps (sweep off before it fills to cancel). Clearing a lock pops a brief "unlatch" ghost. See Targeting & radar.

Bore sight

A hull carrying a railgun has one more instrument, because nothing else on the screen says where a hull is pointing: a thin sight line in the slug's own steel blue, out of the muzzle and ending exactly where the slug would end, with a ring on every section that shot would destroy. It is up whenever your weapons are hot, thickens as a charge runs, and stays up dimmed through the reload so the twelve seconds can be spent aiming.

Screenshot assets/wiki-section-railgun-sight.png The sight line out of the muzzle onto a gunship, with the kill ring at the face the slug would enter.

Docking sight

A hull carrying a docking port gets an instrument of its own once it locks a ship that has one too. Inside 80 m of face gap the sight draws three things in the world: a flat cross over each of the two port faces, a line between them, and a tick on that line for every cell of capture distance still to cross. Fly it in that order - square the two crosses up, stand the line perpendicular to them, then close the gap until the ticks run out.

It is a two-colour readout, and each half answers one question. The crosses turn green when the two ports are facing each other closely enough; the line and its ticks turn green when both the gap and the closing speed are inside the envelope. Cyan means not yet. Three green and the DOCK chip lights.

Nothing on it flies for you, and the roll is not drawn at all - the ports are cylinders, so any twist docks, and lining one up is your business. The sight is up only while you are locked, in range, carrying the verb, and not already docked.

Screenshot assets/wiki-hud-docking-sight.png The two port crosses and the ticked line between them on a final approach.

Pickup sight and canister tags

A hull carrying a cargo intake draws a pickup sight for a canister within 200 m of your ship, with no lock needed: a cross on the intake's face and a line to the canister. A travel-locked canister in range takes the line first; otherwise the canister nearest an intake does. Stand the line perpendicular to the cross, then close the gap. The sight goes with the canister when the intake takes it.

Within 100 m, each canister carries an amber tag that reads what it holds, such as 4 Hull plate, or Mixed cargo for more than one item, with its total mass under it.

Allegiance markers

A small filled triangle floats above every ship in view, pointing down at the hull and coloured by how it stands to YOU: green for your allies (your AI wingmen included), red for hostiles, grey for neutral bystanders. Your own ship shows none - you know where you are. The triangle tracks each ship and hides when it leaves the screen (pointing at off-screen ships is the edge indicators' job); a ship re-aligned mid-scenario flips its marker on the spot, and so does an armed Neutral ship answering your fire - red while it is hitting back at you, grey again once it lets go, even though its side never changed. It reads at a glance so a mixed brawl - wingmen and enemies tangled together - stays legible. See Factions.

Target viewfinder

The corner inset renders a live, magnified 3D view of your locked target through a second (offscreen) camera. Your combat lock owns it; with no combat lock it shows your travel lock, and neither lock changes. Its frame glows hot-red while your weapons are hot and steel while safe, with corner ticks that appear only when hot. A caption names the target over its range (DST) and closing speed (CLS, positive while closing). A combat target adds its relation or NEUTRALIZED in its relation colour; a travel target stays steel. Bodies that cannot be scoped (nav beacons) show a NO-SIGNAL panel instead, and a combat beacon keeps that panel even when your travel target could be framed. When a framed combat target is destroyed the inset freezes the final pose for about two seconds - a kill cam - then shows your travel target or closes. The fine-locked section glows in both the inset and the main view.

Comms and objectives

Scenarios talk to you through a comms stack: broad story cards with a distinct speaker header above larger message text. Each card is drawn in its own accent colour, so you know what kind of voice it is before you read a word. They rise from the bottom-left like a chat transcript. A newly posted objective arrives in the objective stack at the top of the screen - a column of larger amber chips, newest on top. Both are notifications, not standing lists: each leaves once it has been read, so a quiet cockpit stays quiet.

Show explanation

One colour carries the whole card: the frame around it, the speaker header, the placeholder portrait, and the words themselves lifted toward white so the message stays the brightest thing on it. The dark backing and the way a card fades are the same on every line, so the only thing that ever changes is the voice.

Almost everything you hear is the traffic your shift is paid to answer, and that is the HUD's own blue - the colour a line is drawn in when it says nothing else. A line that is NOT that says so in colour: an amber band you merely overheard, a green voice in the cabin beside you, a corporate net in its house colours. Nothing is looked up and nothing is registered, so a scenario or a mod invents as many voices as it has colours.

Several comms cards can stay visible at once; newest sits at the bottom, older lines push upward and fade. Each card has a large speaker icon slot, using authored scenario art when supplied and a cockpit placeholder otherwise - Basic Training gives Range Control its own green CRT portrait, and a mod ships as many faces as it has voices. A card fades in with a soft blip and leaves by timeout or explicit dismiss. A burst larger than the visible stack waits its turn in order; a backlog longer than the panel could ever show (two dozen lines) drops its oldest waiting cue rather than queueing a line that would come up after the scene it belongs to.

An objective chip carries the objective itself behind a diamond; it pops the moment its objective posts and then breathes quietly, and it is read either after its dwell or the instant you open the interface. For the standing list, type objectives in the command shell (or log for the combined comms and objective history); in flight, the larger gold objective markers, diamonds and edge chevrons on the targets themselves are the lasting "go here" cue. A completed objective chimes and its chip goes with it. Everything clears with the scenario rather than lingering over the menu.

The interface

Press Tab (or click the right stick on a gamepad) to open the interface: a full-screen panel with Map, Ship and Inventory panes that pauses the game and frees the cursor. M (or Y on a gamepad) steps to the next pane; Tab or Esc closes it and resumes flight. A posted objective's chip carries a TAB cue while it is up - the in-flight reminder that the interface is there.

The interface has its own page: the map and GOTO, the ship's sections and their repair and rebind actions. Press : for the command shell, which prints the flight log and answers objectives.

The screen substrate

Every projected element - lock brackets, edge arrows, objective markers - rides one shared system that anchors a UI node to a world point or entity, sizes it by fixed pixels or apparent (on-screen) size, and either hides off-screen targets or clamps them to the viewport edge with an arrow pointing back to them.