Flight Control: HOTAS guide (preview)

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

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.

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

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.

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

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.

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.

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

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.