Stand-in page for checking only: the real tab bar belongs to the site. Only the section below is the deliverable (hotas-tab.html).
OverviewDownloadDocsHOTAS (experimental)
EXPERIMENTALThis is the HOTAS preview, built on a separate experimental branch (codex/flight-control-hotas). It is not part of the regular Flight Control release, and the regular version works without it. Fate of the Galaxy 2.0.2 only.

HOTAS · EXPERIMENTAL PREVIEW

Your stick, your throttle, your pedals.

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.

The HOTAS tab in the Flight Control Console, showing a joystick with its axes, hat and buttons labelled with the actions assigned to them
The HOTAS tab in the Flight Control Console, showing a joystick with its axes, hat and buttons labelled with the actions assigned to them
  • 01Press to assign. Choose an action, then move the axis, press the button or push the hat on any device. Flight Control listens to all of them at once and ignores jittery axes. You can also click the control in the live picture.
  • 02Several devices. Stick, throttle, pedals, button box. Game controls can use up to four devices, and wheel controls can use as many as you have. A gamepad can stay connected alongside.
  • 03Game controls and wheels. Flying controls, weapons, targeting, throttle, energy, views and squad commands go straight to the game. The command wheels, menus and gamepad-style buttons run through Flight Control, so they keep their tap and hold actions.
  • 04One button, different jobs. Put fire on a button and wheel select on the same button: it fires in flight and confirms inside a wheel. Wheel cancel and the secondary trigger work the same way. Good for a Freedom 2.4 with few buttons, or for choosing without moving your fingers.
  • 05Encoder wheels. Turn a rotary encoder to step round a command wheel one entry at a time, then press to select. Two ordinary buttons work too.
  • 06A picture of your gear. Live bars, buttons and hats you can drag into place, with an optional photo of your own device behind them.
  • 07Back to the gamepad in one click. Gamepad mode removes the HOTAS bindings and restores how the game was set up before. Your HOTAS profile is kept for next time.
  • 08Dead zones, curves and calibration. Open the axes dialog to see each flying axis live, measure it, and tune its dead zone, curve and range. Precision mode (experimental) applies the settings per axis, which the game itself cannot do; the game's own mode can use the measurement to set its one dead zone.
  • 09Careful with your files. Everything is backed up before Apply, with a one-click restore. Shared profiles carry no serial numbers and no file paths from your PC.

Tested so far

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.

What is in the experimental branch

  • HOTAS tab. Find your controllers, assign by pressing or moving a control, live preview you can arrange, several devices at once.
  • Game controls from a HOTAS. Axes, buttons, axis sides as buttons, inverted axes and the first hat's four directions, with about 80 game actions.
  • Wheels from a HOTAS. Wheel D-pad directions, select, cancel and the gamepad-style buttons from any device, with their tap and hold actions.
  • One button, different jobs. Wheel select and cancel act only while a wheel is open; triggers pause while a wheel is open.
  • Encoder wheels. Step clockwise and anticlockwise round an open wheel.
  • Gamepad mode. Switch the game back to the gamepad and return to HOTAS without losing your profile.
  • Profiles. .fchotas files without serial numbers or file paths; a device can be remapped to your own.
  • Axis settings. A flight axes dialog with live pictures, calibration, dead zone, saturation and curve per axis (Precision mode, experimental), or a measured dead zone for the game's own handling.
  • Safer Apply. Backups before every change, a restore button, a warning before anything is removed, and a warning when applying gamepad settings would redirect HOTAS devices.
  • Not yet: Fate of the Galaxy 1.1.x, hats beyond the first for game actions, diagonal hat directions for game actions.

Video tutorial

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.

Chapters

  1. 0:00 Welcome
  2. 0:20 Turn on Advanced
  3. 0:37 Scan your devices
  4. 0:56 Press to assign
  5. 1:20 Game and Flight Control actions
  6. 1:46 One button, different jobs
  7. 2:08 Encoders and dials
  8. 2:26 Flight axes
  9. 2:59 Apply and go back
  10. 3:19 Save and share
  11. 3:41 If something is missing

HOTAS guide

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.

1. What you need

  • Fate of the Galaxy 2.0.2, installed through Flight Control (MyMod). Fate of the Galaxy 1.1.x (classic) does not support HOTAS yet.
  • Windows 64-bit, and the Flight Control Console and launcher from this build.
  • Controls: Advanced. HOTAS is an advanced feature, so its tab is greyed out and cannot be clicked until the Controls switch is set to Advanced.
  • Any joystick, throttle, pedals or button box that the game's own engine can see. If the game cannot see a control, neither can Flight Control (see section 10).
  • Close the game before you press Apply.

2. Quick start

  1. Open the Flight Control Console and set Controls (right end of the tab row) to Advanced. The HOTAS tab is switched off in Simple. Then choose the HOTAS tab. It scans your controllers straight away.
  2. Move a control on each device. Its picture lights up, so you can tell which device is which.
  3. Pick an action on the left, for example Pitch, then move the stick. The assignment is made when the signal is clear.
  4. Repeat for the rest of your controls. Click Control not listed? if something does not show up.
  5. Close the game and press Apply to pilot. Launch the game with the Flight Control launcher.
The HOTAS tab with two controllers and their assignments
The HOTAS tab with two controllers and their assignments

Your work saves itself. You do not need to save a file to keep it.

3. The HOTAS tab

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.

A second controller selected
A second controller selected

Actions. The list has two parts.

  • Game actions are the game's own controls: flight axes, weapons, targeting, throttle and thrust, energy and shields, views, squad and mission commands.
  • Flight Control actions are the command wheels and gamepad-style buttons: wheel D-pad directions, select and cancel, the face buttons, bumpers, stick clicks, triggers and sticks.

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.

Listening for a control
Listening for a control
  • Axes that you want as a button (a throttle lever used as a switch) work: move the axis towards the side you want.
  • Invert axis flips an axis.
  • Clear removes an assignment.

4. Two kinds of action

Game actionsFlight Control actions
What they areThe game's own bindingsThe wheels, gestures and gamepad-style buttons
Where they runIn the gameIn the Flight Control launcher, on a virtual gamepad
LimitsFour joystick devices; axes 1 to 8; buttons 1 to 128; only the first hat, four directionsNone of those
Can share one inputNo, one input has one jobYes

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 game action on a hat direction
A game action on a hat direction

5. One button, different jobs

A gamepad button does one thing in flight and another inside a wheel. You can do the same on a joystick.

  • Wheel: select and Wheel: cancel act only while a wheel is open.
  • Right trigger and Left trigger fire the primary and secondary weapons, and are paused while a wheel is open.

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.

What a Flight Control button does in flight
What a Flight Control button does in flight

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.

Wheel roles
Wheel roles

6. Encoder wheels

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.

7. Several devices

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.

8. The preview

  • Arrange preview lets you drag each control to where it is on your real device.
  • Background image adds a picture of your device behind the controls. The picture stays on your PC and is never saved into a shared profile.
  • Reset layout returns to the automatic arrangement.
Arranging the preview
Arranging the preview

9. Flight axes: dead zones, curves and calibration

Press Axes… (beside Clear) to see and tune your flying axes: pitch, yaw, roll and the throttle. First choose how they are handled.

  • Game. The game handles the axes, with one dead zone and one sensitivity for every axis (the Flight response tab). Nothing per axis is applied. The dialog still shows each axis live, and Calibrate… measures it and can set the game's dead zone for you.
  • Precision (experimental). Flight Control reads the axes itself and steers the ship through the game script. Each axis gets its own dead zone, curve and calibration. Apply clears the game's own axis bindings so the game does not also act on them.

In Precision, for the axis you pick:

SettingWhat it does
Dead zoneThe 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 atHow far you have to move before the axis already counts as full. Lower it if the stick cannot quite reach its end stop.
CurvePositive makes the centre gentler and the ends faster, negative the opposite.
Invert this axisFlips 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.

The flight axes dialog in Precision mode: a live reading against the calibrated range, the dead zone, and the response curve with a live point
The flight axes dialog in Precision mode: a live reading against the calibrated range, the dead zone, and the response curve with a live point
The same dialog in Game mode, showing the game's own single dead zone
The same dialog in Game mode, showing the game's own single dead zone

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.

10. When a control is missing

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.

11. Applying, backups and switching back

Apply to pilot writes your assignments for the selected pilot. Close the game first.

  • Game actions are written to Flight Control's control table, and your devices are set as the game's joysticks.
  • Flight Control actions are written to a small map file that the launcher reads.
  • Before anything is changed, a backup is made. Restore backup puts back exactly what the last Apply changed.
  • If something that was installed is not in your profile any more, Apply tells you before it removes it.

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.

12. Sharing profiles

  • Save profile writes a .fchotas file. It contains your assignments, device names and layout. It does not contain device serial numbers or any picture path.
  • Open profile loads one. Anything personal is stripped, the file is checked, and your own profile is kept as a backup first.
  • A shared profile matches your hardware by device model. For a different model, right-click a device button along the top and choose one of your own devices to use in its place.
  • Wheel layouts, macros and button actions live in the Profiles tab and are shared separately. A HOTAS setup that relies on a button's quick-press action needs that profile too.

13. What is confirmed

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

14. Troubleshooting

What you seeWhat 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 PrecisionOpen Axes…, calibrate that axis and use the recommended dead zone.
A button fires while a wheel is openThat 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 emptyPress Scan controllers. Plug in the device first.
Apply failsThe Console writes the details to console-error.log next to it. Send that with your report.
You want the gamepad backPress Gamepad mode.

15. Reporting a problem

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.

Install the preview

  1. Install Flight Control for Fate of the Galaxy 2 as usual and play once.
  2. Open the Flight Control Console, set Controls to Advanced, and choose the HOTAS tab.
  3. Move your controls to see them light up, then pick an action and use the control to assign it.
  4. Close the game and press Apply to pilot.
  5. Start the game from the Flight Control launcher.

Download

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

Questions

Which games and versions?

Fate of the Galaxy 2.0.2 through Flight Control. Fate of the Galaxy 1.1.x is not supported for HOTAS yet.

Which devices?

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.

Can I keep my gamepad?

Yes. Flight Control actions can run from both at once, and Gamepad mode switches the game's own bindings back in one click.

Does a button really fire and confirm?

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.

Will it overwrite my settings?

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.

Can I share my 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.

Can I set a dead zone per axis?

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.

Is it safe?

The code is open source and the downloads are checked against their SHA-256. The programs are not code-signed yet.

Send a report

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.