Flight Control 1.2.2 supports Fate of the Galaxy 2.0.2 through MyMod and the final classic FotG 1.1.3. On Windows, create a pilot in FotG, close the game, extract the player ZIP, and run Setup.exe. Select the folder containing Knossos and kn_portable. Launch Hangar Bay.exe from that game folder.
See Help, the preview install guide, and the changelog. The Classic details below describe the established 1.x install path.
Fate of the Galaxy 1.1.3 passed preset generation, isolated installation, and a practice-mission controller test; see the compatibility report. Additional missions and VR remain to be checked.
Development began so the game could be played on a Legion Go 2 at launch, before it had gamepad support. Fate of the Galaxy gained native gamepad bindings along the way; Flight Control covers what individual bindings don't: more cockpit commands than a controller has buttons, and menus that still expect a mouse. The command wheels are inspired by MechWarrior 5 and adapted for FotG (no affiliation). The default layout is a tested starting point, not a rule: switch flight-axis presets, add long-press actions, rearrange the wheels and tinker with the macros.
- Download the player build: https://manictrashpanda.dev/games/FotGFlightControl/ (the ZIP with Setup.exe; this repository's automatic source ZIP does not contain the compiled programs)
- Help: https://manictrashpanda.dev/games/FotGFlightControl/help/
- Report a problem: GitHub issues or [email protected]
- Download safety: SECURITY.md explains the 1.1.1 Defender alert and the changes in 1.1.2.
Tested on a Lenovo Legion Go 2, ROG Ally X, Xbox controllers and generic gamepads, with Fate of the Galaxy 1.1.0 through 1.1.3. The Excoriator tutorial was completed with the 1.1.5 local build. Other campaigns and multiplayer remain unverified. Bugs, awkward interactions and ideas for improvement: [email protected].
Unofficial fan tool. Not affiliated with or endorsed by the Fate of the Galaxy team, the FreeSpace Source Code Project, Lucasfilm or Disney. The game and engine are separate downloads and are not included here.
By Manic Trash Panda, coded with ChatGPT. Questions: [email protected]. See About.html for project and platform attributions.
The original add-on code, companion programs and documentation are released under the MIT License. The original emblem may be used only with this tool under the artwork terms. The game and engine are separate downloads.
Contributions are welcome; see CONTRIBUTING.md. For source builds and release packaging, see docs/RELEASE.md.
An independent, additive controller mod for Fate of the Galaxy 1.1.0, 1.1.1, 1.1.2 or 1.1.3 on Windows with its FSO 26.0.1 engine (the standard SDL2 build, or the FSO 26.0.1-SDL3 package on older installs). The Lua addon draws four in-flight panels; a small XInput bridge supplies raw D-pad and right-stick input and adds menu navigation. Hangar Bay, the Flight Control app, configures wheel layouts and macros, and backs up native pilot settings.
The Flight Response, Macro Deck, Advanced Layouts, Button actions and Custom axes screenshots show the controller preview and configuration pages.
- Install Fate of the Galaxy 1.1.0, 1.1.1, 1.1.2 or 1.1.3 with its FSO 26.0.1 engine. Run the unmodified game once and create a pilot, then exit. Connect the gamepad before running Setup.
- Extract the entire ZIP. Close the game and any older FotG controller companion.
- Double-click Setup.exe. It finds common game locations; otherwise choose the folder that contains
kn_portable(portable Knossos), or your Knossos library folder (full Knossos: the folder that holdsFotG_2andbin, by defaultDocuments\Freespace2-mods; Knossos shows it in Settings) with Browse game. Click Install / Repair. - Open Hangar Bay.exe in the game folder. On Deploy, choose the base game or an installed mission pack, then launch Standard Flight or OpenXR VR. The original game launcher runs without Flight Control.
- Use Hangar Bay Console for flight response, macros, axes, wheel text and button actions; Service for backups, repair and controller selection; and Guide for built-in help. Advanced wheel layouts can be shared as JSON profiles. Save Wheel and restart the game after wheel changes.
To switch controllers, close the game, open Hangar Bay Service → Choose controller (or Console → Flight Response), choose the XInput slot whose preview responds, and press Apply with backup. The console matches that slot to FSO's SDL joystick and saves both choices in the active game profile. Restart the game afterward. If SDL cannot identify which physical pad matches the slot, choose it from the device list. A disconnected saved slot stays disconnected in game instead of silently controlling the ship with another pad.
See the step-by-step installation guide and test checklist. Setup installs by itself and runs no scripts. Advanced users can run the same install from a command prompt. From a command prompt or PowerShell, run Setup.exe --install --game "<folder>", where <folder> is the folder described above, with no backslash at the end. Setup is a Windows program, so the prompt returns at once; the output appears in the same window. To wait for it, use Start-Process .\Setup.exe -ArgumentList '--install','--game','<folder>' -Wait in PowerShell.
The installer checks the game/engine version, copies only its own GamepadMods/FotG_Gamepad_Wheel directory, and creates two launchers. The wheel launcher uses a separate GamepadMods_settings.ini profile; installation identifies the connected controller through the engine's own SDL library (SDL2 or SDL3) and selects it in that profile, together with the order of its stick axes, backing up any prior profile. The Hangar Bay Console edits this active profile. The installer also backs up each existing native v4 pilot before reserving A, B, X, Y, LB, RB, Start, L3, R3 and D-pad joystick bindings; those inputs are delivered to the wheel instead. RT produces the normal mouse-primary-fire input in flight. Existing keyboard bindings, game scripts, engine, campaigns and saves remain in place. Add --skip-pilot-reservation to Setup.exe --install to install files without changing pilots, then press Reserve wheel buttons in the console for each pilot before testing.
| Input | In flight | In menus |
|---|---|---|
| D-pad down | Tap for squad commands; hold to look rear | Next item / Down |
| D-pad up | Tap for ship systems; hold to look up | Previous item / Up |
| D-pad left | Tap for targeting; hold to look left | Previous item / Left |
| D-pad right | Tap for macros and mission commands; hold to look right | Next item / Right |
| Right stick | Select wheel segment | Move pointer |
| A | Confirm selection; target ship in reticle when wheel closed | Activate selection; click after stick movement |
| B | Target closest attacker; cancel an open wheel | Back/Escape |
| RT | Primary fire when wheel closed | Mouse click |
| LT | Secondary fire when wheel closed | No menu action |
| Left stick | Native flight controls | Move pointer |
| X / Y | X cycles the selected target class; hold Y for the B-wing or T-Blade's third gun | Enter / Backspace |
| LB / RB | Tap LB cycles secondary banks; hold LB links torpedoes (Q). Tap RB cycles primary banks; hold RB changes ship mode | Previous / next tab |
| LB + RB | Hold together for hyperspace | No menu action |
| L3 / R3 | Tap L3 matches target speed; hold L3 links guns (E). Tap R3 cycles subsystems; hold R3 toggles mouse movement (N) | No menu action |
| Start / Menu | Tap to pause; hold 500 ms to cycle Cockpit → Chase → External | Enter |
The D-pad Right wheel keeps four configurable macros on its cardinal slots. Its diagonals open responses 1–5, responses 6–0, Dock / nav, and other mission commands. Choose a group and then a command with the right stick and A; B returns to macros. Dock / confirm sends Enter, which is context-sensitive in FotG. Numbered prompts send the actual number keys. The targeting wheel's up-left slot cycles subsystems on the current target without aiming at them. Its down-left slot toggles the targeting computer with FotG's Z key, including the Excoriator tutorial requirement. Subsystem in sight remains available as a custom button action.
The main menu uses discrete D-pad selection with a visible cursor highlight. Other menus receive arrow key taps, while A sends Enter after D-pad navigation. After moving either stick, A clicks at the pointer; RT always clicks. LB/RB send Shift+Tab/Tab. This keeps the game's pointer-only controls accessible without a touchpad or finger mouse.
In the Systems wheel, press Y for Manual Power. Flick the right stick up or down to select the segmented Lasers, Engines, or Shields arc. Move it left/right to adjust the preview immediately; X gives all 12 points to the selected system. A applies the allocation and closes the editor; B or Y discards the preview and closes it. Unsupported ships and multiplayer do not allow manual changes. In Excoriator training, applying a selected arc also sends its required increase/decrease key pair (End, Page Up, or Page Down with Shift) before restoring the chosen allocation.
In the Systems wheel, press X for Shield Allocation. The display shows front/rear for two-section ships, or front/right/rear/left for four-section ships. Use up/down to select a section and left/right to move existing shield strength; X transfers as much shield strength as possible to the selected section (up to 200% of its balanced strength). A applies and closes; B or Y cancels. Shield energy is never created by redistribution. In the Excoriator tutorial, applying a front-shield allocation also sends the Alt+W key that its objective checks.
In flight, a short D-pad release opens its wheel. Holding a direction starts the matching view after the configured delay (250 ms by default), and releasing centers the view. The Macro Deck slider sets the delay from 150 to 600 ms. Disable look around makes every D-pad press open a wheel immediately. Menus retain immediate navigation. Save Wheel and restart the game after changing this setting.
Hold Menu cycles camera is enabled by default and can be turned off on the Macro Deck page. Each hold advances Cockpit → Chase → External → Cockpit; a short press still pauses. Buttons... on the Macro Deck page sets the action of each face button, bumper and stick click: a quick-press action for A, B, X, Y, LB, RB, L3 and R3, and an optional long-press action (250–1000 ms) for all of them except Y. Choices: targeting (reticle, attacker, next in class, nearest enemy or friendly, target's target, newest ship, bombs, subsystems, turrets, clear), match speed, weapon and ship-mode cycling, afterburner and the B-wing/T-Blade third gun (both while held), countermeasures, energy presets, transfers and +/- steps, full or zero throttle, chase and external views, HUD toggle, radar range, nav points, autopilot, and the boarding party task. Actions marked while held repeat as long as the button is down. A and B still confirm and cancel while a wheel is open, and the D-pad, Menu, sticks and triggers keep their roles. R3 hold sends N by default, including in the Excoriator tutorial. Tap RB cycles the primary weapon bank and hold RB changes ship mode. Buttons can disable or override any of these default hold actions. The other quick actions keep the 1.0 layout. The squad command wheel includes Cycle boarding party task during Assault missions, matching the game's keyboard 4 action. It is also available as a custom hold or macro action.
LB cycles the selected secondary bank for LT. Y fires the third primary gun directly on B-wings and T-Blade bombers and restores the previously selected bank afterward; Y has no flight action on other ships. Hold RB changes the ship's available control mode: Falcon gun control, TIE-family burst fire, S-foils on equipped ships, or targeting computer mode on other ships with secondary weapons. The game's mission restrictions still apply. A targets the ship under the reticle, B targets the closest ship attacking you, and X cycles the ship class chosen on the targeting wheel (enemies by default). Choosing a class does not immediately change the target. The targeting wheel also clears the ship target, switches between a subsystem and the hull, toggles the targeting computer, and cycles live turrets on the current ship. Subsystem actions are disabled when the selected ship has no eligible parts; tap R3 cycles subsystems directly.
Flight Axes defaults to Classic direct (tested). It restores the earlier handheld layout using the engine's gamepad axes: right stick yaw/pitch; left stick roll/relative throttle. Choose Classic inverted pitch to reverse only the right stick's vertical steering. The stock 1.1 default instead binds yaw/pitch to the left stick, roll to right stick Y, and no throttle axis. The mod builds two named presets from the installed 1.1 control table and does not edit the game's table. Choose Game's saved setup in the console to stop applying a classic preset. The older profile used sensitivity 5 and deadzone 10%; set those on the Flight Response tab and apply with backup for the closest v1 comparison. The classic presets reserve A, B, X, L3, R3, LB, RB, Y and Start for the mod's context-aware actions. Existing custom button bindings may need to be reapplied after enabling Classic.
The wheel confirms dangerous depart/warp orders twice. The command panel uses mn.CommItems and native selectItem() so mission restrictions and FotG order hooks remain in effect. The targeting subsystem macro checks visibility, team, targetability and remaining subsystem health and is limited to single player. Energy presets are likewise limited to single player. An unavailable action displays a message instead of guessing an order.
Wheel labels now have near-opaque dark backplates, bright text and a clear amber selection border so combat effects do not wash them out. Wheel Text in the console selects the game's existing 20 px or 30 px font and regular or bold weight. The default is 20 px bold. Large text may occupy more of the screen on low resolutions; switch back to Medium if needed.
Choose Custom axes under Flight Axes and press Edit axes... to pick the stick axis (left or right stick, left/right or up/down, or none) for yaw, pitch, roll and relative throttle, each with an invert option. Save Wheel writes a fourth preset, FotG Custom, next to the two Classic presets in the add-on's Controlconfigdefaults.tbl; Install / Repair keeps it. Button actions and the axis map travel in exported profiles (profile version 5; older profiles still load). Game's saved setup leaves everything to the game's own Controls menu.
Setup and the console check https://manictrashpanda.dev/games/FotGFlightControl/update.json when they open. When a newer release exists, Setup shows Update to x.y.z: it downloads the ZIP only from the product site or this repository's GitHub releases, checks its size and SHA-256 against the manifest, extracts it under %LOCALAPPDATA%\Manic Trash Panda\Flight Control\Updates, and shows the new Setup.exe in File Explorer. Close Setup, run the new one and choose Install / Repair; Flight Control never starts a downloaded program itself. The manifest can also list newer game versions checked with a given Flight Control build; Setup then installs for them without the override warning. The check sends only the HTTPS request (with a FlightControl/<version> user agent) and can be turned off with Check for updates in Setup. The builds are not code-signed yet, so Windows may warn about an unknown publisher.
The console's Restore latest backup restores the selected pilot and matching FotG settings INI from a timestamped copy under kn_portable/HardLightProductions/FreeSpaceOpen/ControllerSetupBackups. Restore any pilots whose reserved controls you want back before removing the addon. Then use Service → Remove Tool in Hangar Bay: it removes GamepadMods/FotG_Gamepad_Wheel, the launchers and the Setup copy, and keeps pilots and backups. Hangar Bay can't delete its own file while it is open, so it then shows Hangar Bay.exe in File Explorer; delete it after Hangar Bay closes to finish. The original game's launcher remains available.
Source is included. Build and offline checks passed. On a Legion Go 2, testing confirmed that the repaired Classic direct preset restores right-stick yaw/pitch and left-stick roll/throttle in the practice mission. The prior failure was traced to a stale SDL2 joystick GUID in the wheel profile and a raw SDL3 joystick axis mapping applied to FSO's canonical SDL3 gamepad axes. The installer now detects the connected controller through the engine's own SDL library. Classic inverted pitch is generated and selectable, but has not yet had a physical flight test. Issuing an actual squad order, all four panels, macro effects, broader mission compatibility, and multiplayer behavior still need review. Some mission-specific screens may still require stick pointer control. Fate of the Galaxy 1.1.1 and 1.1.2 are also supported. They use the same packages and launch flags as 1.1.0. Flight Control runs on the FSO 26.0.1 engine Knossos installs for Fate of the Galaxy: the standard SDL2 build (SSE2, AVX or AVX2, whichever this PC runs) on a clean FotG 1.1.1 or 1.1.2 install, or the FSO 26.0.1-SDL3 package where an install from FotG 1.1.0 still has it. On SDL 2.26.5 an Xbox controller reports its sticks as raw axes 0-3 and its triggers as 4-5, the same numbering as the SDL3 build; the installer reads the order from the connected pad and records it in engine-axes.txt. Knossos may install 1.1.2 as one merged data folder instead of one folder per package; the launcher and preset builder handle both layouts. 1.1.2's default controls list the roll axis as unbound, so the builder replaces any axis entries the game already has instead of adding duplicates; the generated Classic presets are identical to 1.1.1's. Install and in-game play have been confirmed on 1.1.1 and 1.1.2. If the game is updated to a version this build doesn't list, Setup shows Unsupported game version and offers Override version check. Ticking it installs for that version anyway, after a warning: compatibility cannot be guaranteed while the override is in use, until Flight Control is updated for that version. Setup still checks the game's control defaults first and changes nothing if they are in a layout it doesn't recognise. From a command prompt, the same is Setup.exe --install --game <folder> --game-version <version> --override-version-check. Tested on a Lenovo Legion Go 2, ROG Ally X, Xbox controllers and generic gamepads, with Fate of the Galaxy 1.1.0, 1.1.1 and 1.1.2. Testing has focused extensively on practice missions, refining how the controls feel while flying. The campaign and multiplayer have not yet been tested. Reports from campaign missions and your own configurations are welcome at [email protected].
