HOTAS · EXPERIMENTAL PREVIEW
The HOTAS tab finds every joystick, throttle and pedal set the game can see and lets you assign them by using them. Pick an action, move the control, and it is assigned. It works across several devices at once, so a stick and a set of pedals can fly together, and the command wheels work from them too.

HOTAS support is a preview. It has been flown with a Logitech Freedom 2.4 and a handheld gamepad on Fate of the Galaxy 2.0.2: joystick axes and buttons as game controls, several devices at once, and the command wheels driven from the joystick. Hat directions as game controls, axes used as buttons, inverted axes, rotary encoders, Precision flight axes and some of the extra game actions have not been tried on many devices yet. Fate of the Galaxy 1.1.x does not support HOTAS yet. If you have a HOTAS, I would love to hear how it goes: dev@manictrashpanda.dev.
.fchotas files without serial numbers or file paths; a device can be remapped to your own.About four minutes, with captions: scanning, assigning, wheels, encoders, flight axes, backups and sharing.
The video loads from YouTube only when you press play. Open it on YouTube.
The manual for the experimental HOTAS preview. It is separate from the regular Flight Control documentation.
Fly Fate of the Galaxy 2 with a joystick, throttle and pedals, and keep Flight Control's command wheels. This guide covers the HOTAS tab in the Flight Control Console.
Preview. HOTAS support is new and has been tested with a Logitech Freedom 2.4 and a handheld gamepad. Hats, axes used as buttons, rotary encoders and some of the extra game actions have not been tried on many devices yet. Section 13 lists exactly what is and is not confirmed.

Your work saves itself. You do not need to save a file to keep it.
Controllers. Each connected device has a button along the top, with a dot that is filled while the device is connected. The picture below it shows live values: bars for axes, circles for buttons and a dial for each hat. A device you unplug stays in your profile and comes back when you plug it in again.

Actions. The list has two parts.
Type in the box above the list to filter it.
Assigning. Choose an action, then press the button, move the axis or push the hat on any device. Flight Control listens to all your devices at once and ignores axes that jitter on their own. You can also click a control in the picture to assign it without touching the hardware.

| Game actions | Flight Control actions | |
|---|---|---|
| What they are | The game's own bindings | The wheels, gestures and gamepad-style buttons |
| Where they run | In the game | In the Flight Control launcher, on a virtual gamepad |
| Limits | Four joystick devices; axes 1 to 8; buttons 1 to 128; only the first hat, four directions | None of those |
| Can share one input | No, one input has one job | Yes |
Use game actions for the ship's flying controls and for anything that always does the same thing. Use Flight Control actions for the wheels, and for any button that must do different things at different times.

A gamepad button does one thing in flight and another inside a wheel. You can do the same on a joystick.
Assign one physical button to Right trigger and Wheel: select. In flight it fires. In a wheel it confirms and does not fire. Do the same with another button for Left trigger and Wheel: cancel.
A button that you hold through a selection is ignored in flight until you let go, so choosing an entry does not fire a shot as the wheel closes.
The face buttons, bumpers and stick clicks keep their flight action from the Buttons tab, shown under the list when you select one.

Why not a game action? The game does not pause its own bindings while a wheel is open, so a button bound to Fire primary in the game would fire while you used the wheel. The HOTAS tab warns you when one input drives both a game action and a Flight Control action.

A rotary encoder usually shows up as two buttons, one pulse per click in each direction. Assign Wheel: step clockwise and Wheel: step anticlockwise, turning the encoder in each direction when asked. While a wheel is open, each click moves the highlight one entry round the wheel and wraps at the ends. Wheel: select confirms.
Fast turning is queued, up to 16 steps, and played back one at a time. Two ordinary buttons work in place of an encoder.
Use as many devices as you have: a stick, a throttle, pedals, a button box. Each device is a button along the top of the preview. Identical devices without serial numbers (two of the same pedals) are told apart by the order Windows lists them. Game actions can use up to four devices. Flight Control actions can use any number.
You can use a gamepad and a HOTAS at the same time. The HOTAS is layered over the gamepad in the launcher.

Press Axes… (beside Clear) to see and tune your flying axes: pitch, yaw, roll and the throttle. First choose how they are handled.
In Precision, for the axis you pick:
| Setting | What it does |
|---|---|
| Dead zone | The part of the travel around the centre that counts as zero. The rest is stretched to full, so there is no jump when the stick leaves it. A lever has its dead zone at both ends. |
| Full deflection at | How far you have to move before the axis already counts as full. Lower it if the stick cannot quite reach its end stop. |
| Curve | Positive makes the centre gentler and the ends faster, negative the opposite. |
| Invert this axis | Flips the direction. |
The picture shows the reading against the calibrated range, the dead zone in red, and the response curve with a live dot on it.


Calibrate… measures the axis in two steps. Leave it alone for two seconds, so Flight Control learns where it rests and how much it wobbles. Then move it through its whole range, to every end, for six seconds. A throttle lever needs only the sweep. The result recentres a worn stick, stretches a short one to full travel, and recommends a dead zone from the wobble. Use recommended dead zone applies it, and Reset calibration goes back to the full range.
Precision needs the Flight Control launcher and applies only while the game window is in front. If the launcher's data stops, the game goes back to its own handling, which has no axis bindings in Precision, so the ship stops steering until the data returns. Keyboard throttle keys, match speed and the afterburner keep working. Because Precision replaces the game's axis handling, the global dead zone and sensitivity on the Flight response tab no longer apply to these axes.
Press Control not listed? and use the control. If it lights up, it is listed and ready to assign. If nothing happens, the game cannot see it either. Try another mode on the device, or set the control to a button in the manufacturer's software, then press Scan controllers.
Apply to pilot writes your assignments for the selected pilot. Close the game first.
Gamepad mode switches the game back to the gamepad: it removes the HOTAS bindings and the map, and puts the pilot's preset and joystick selection back as they were before you first applied HOTAS. Your HOTAS profile is kept, so Apply to pilot brings it straight back.
If you apply gamepad settings on the Flight response tab while HOTAS is applied, you are warned first, because that points the game's first joystick at the gamepad. If it happens, the HOTAS tab tells you the slots no longer match and Apply re-syncs them.
Applying only Flight Control actions never touches the pilot's preset, the control table or the game's joysticks, so a gamepad setup keeps working beside a HOTAS used only for wheels and buttons.
.fchotas file. It contains your assignments, device names and layout. It does not contain device serial numbers or any picture path.Confirmed in the game: joystick axes and buttons as game actions, several devices at once, Flight Control wheels driven from a joystick, one button with different jobs by state.
Not yet confirmed on many devices: game actions on a hat, axes used as buttons, inverted axes, the extra game actions beyond fire, targeting and weapons, rotary encoders, and Precision flight axes (calibration, dead zones and curves). If one of these misbehaves, please report it (see below).
Not available: Fate of the Galaxy 1.1.x, hats other than the first for game actions, and diagonal hat directions for game actions (they work for Flight Control actions).
| What you see | What to do |
|---|---|
| "Select your FotG 2 installation first" | Use Game / pilot at the bottom and pick the game folder and a pilot. |
| The ship drifts or twitches at rest in Precision | Open Axes…, calibrate that axis and use the recommended dead zone. |
| A button fires while a wheel is open | That button is bound to a game action. Use Right trigger and Wheel: select instead (section 5). |
| "The game's joystick slots no longer match" | Press Apply to pilot again, with the game closed. |
| The picture is empty | Press Scan controllers. Plug in the device first. |
| Apply fails | The Console writes the details to console-error.log next to it. Send that with your report. |
| You want the gamepad back | Press Gamepad mode. |
Tell us which device, which control, what you assigned, and what happened. Include console-error.log if Apply failed. Send reports to dev@manictrashpanda.dev.
[FotG-Flight-Control-HOTAS-experimental.zip] · version [1.3.0-hotas-experimental] · [date] · size [size] · SHA-256 [sha256]
This download is separate from the regular Flight Control download and does not replace it. It changes the Console, the launcher and the wheel script. Setup backs up your pilot before it changes anything, and the HOTAS tab backs up again before each Apply. The programs are not code-signed, like the regular release; the usual security notes on this page apply. Source: github.com/wray2064/FotGFlightControl, branch codex/flight-control-hotas. MIT for the code.
Fate of the Galaxy 2.0.2 through Flight Control. Fate of the Galaxy 1.1.x is not supported for HOTAS yet.
Any joystick, throttle, pedals or button box that the game's own engine can see. If the game cannot see a control, Flight Control cannot either, and the Console tells you.
Yes. Flight Control actions can run from both at once, and Gamepad mode switches the game's own bindings back in one click.
Yes. Bind one button to the Right trigger and to Wheel select. In flight it fires, in a wheel it confirms and does not fire.
Apply backs up the pilot, the game's settings and the control table first, and Restore backup puts them back. Applying only wheel actions never touches your gamepad's flight setup.
Yes. Save profile writes a .fchotas file. It has no serial numbers and no paths. Someone with a different device can pick one of theirs to take its place.
In Precision mode (experimental), yes: each flying axis has its own dead zone, curve and calibration. In the game's own mode there is one dead zone for every axis, and the axes dialog can measure your axes and set it.
The code is open source and the downloads are checked against their SHA-256. The programs are not code-signed yet.
Tell me what your hardware does: dev@manictrashpanda.dev. A saved .fchotas profile contains no serial numbers and no file paths, so it is safe to attach.