Configure the Saitek X65F HOTAS in MSFS 2024 with correct axis mapping, force-sensor tuning, split throttles and fixes for detection problems.
To configure a Saitek X65F HOTAS in Microsoft Flight Simulator 2024, verify its axes in Windows, create a custom device profile, bind the stick and throttle to analogue axis commands, remove duplicate assignments, then tune the X65F’s hardware force level before changing the simulator’s sensitivity curve. This is a PC-only setup.
Does the Saitek X65F work with MSFS 2024?
The X65F can work with MSFS 2024 on a Windows PC as a legacy DirectInput controller. Basic axes and buttons may operate through Windows’ generic HID support, while the original X65F software may be required for force-sensitivity presets, mode programming and other device-specific functions.
There is no native X65F support on Xbox Series X|S, PS5 or PS5 Pro. A console having USB ports does not make an older PC HOTAS compatible.
Before opening the simulator, press Windows key + R, enter joy.cpl and open the X65F’s properties. Pressure on the fixed stick should move the X and Y indicators, and each throttle axis should cover its expected range. If nothing responds there, the fault is at the Windows, driver, USB or hardware level rather than inside MSFS. Our Saitek and Logitech device-detection checklist covers that initial diagnosis in more detail.
How do I set up the X65F controls in MSFS 2024?
The reliable method is to configure the X65F as a plain analogue HOTAS first and add Saitek programming only after the basic controls work.
- Connect and test the hardware. Seat every connection between the X65F components before attaching USB. Start with a direct PC USB port rather than an unpowered hub, then check all axes and buttons in
joy.cpl. - Unload any programmed SST profile. Saitek Smart Technology profiles can translate buttons into keyboard commands. Running those translations alongside direct MSFS bindings often makes switches fire twice or operate the wrong function.
- Create a custom X65F profile. Open the MSFS 2024 control settings, select the X65F and save a recognisably named custom profile. Clear unwanted default assignments instead of modifying an uncertain preset.
- Bind the primary analogue axes. Assign roll to Ailerons Axis, pitch to Elevator Axis and the throttle to an axis command. Do not use digital commands such as Aileron Left or Throttle Increase for an analogue control.
- Assign essential buttons. Add elevator trim, brakes, landing gear, flaps, spoilers, view controls and autopilot disconnect as required. Leave mode layers and macros until a simple profile has been tested.
- Remove duplicate inputs. Search each assigned axis and confirm that another controller, gamepad or keyboard emulation is not commanding the same function. A mistake we see constantly is a gamepad still controlling pitch or throttle in the background.
- Test in a simple aircraft. Watch the cockpit yoke or control stick, then move each throttle slowly through its range. Confirm direction and full travel before loading a complex airliner.
For a broader button-planning method, use our complete HOTAS axis and button workflow rather than assigning every available command at once.
Which X65F axes should I bind?
Bind analogue axis commands wherever Windows reports a continuously moving input, using separate engine throttles only when the two levers are exposed independently.
| Physical control | MSFS assignment | Setup advice |
|---|---|---|
| Stick left/right pressure | Ailerons Axis | Reverse only if the cockpit control moves opposite to the pressure applied. |
| Stick forward/back pressure | Elevator Axis | Forward pressure should command nose-down elevator. |
| Joined throttle levers | Throttle Axis | Best for single-engine aircraft or when both engines should move together. |
| Independent throttle levers | Throttle 1 Axis and Throttle 2 Axis | Use only if Windows shows two separate axes; do not also bind the combined throttle axis. |
| Rudder pedals | Rudder Axis | The X65F has no conventional twist-rudder axis, so pedals are the practical solution. |
| Mini-stick or rotary | Optional view or cockpit function | Leave it unbound if its mouse emulation causes cursor or camera drift. |
The precise command wording can vary slightly with the control-screen layout, but choose entries containing Axis. For split throttles, test engine one and engine two separately; crossing those assignments is easy to miss when both levers are initially latched together.
What sensitivity settings suit the X65F force-sensing stick?
Start with a linear MSFS response, a minimal dead zone and a moderate X65F hardware force setting. The X65F measures pressure rather than physical stick travel, so heavy simulator curves stacked on top of the hardware response can make the centre vague and the outer range abrupt.
- If the aircraft reacts to tiny unintended pressure, select a hardware setting that requires more force or add only enough dead zone to stop centre noise.
- If full pressure does not produce full control deflection, choose a lighter force range and confirm full axis travel in Windows before altering MSFS curves.
- If pitch feels suitable but roll does not, tune the axes separately rather than applying one curve to both.
- If you calibrate the device, keep your hand off the stick while the neutral point is recorded. Resting pressure during calibration creates a permanent-looking roll or pitch bias.
The X65F is force-sensing, not force-feedback. It reads how hard you push, but it does not reproduce aerodynamic loading, trim forces or buffet from the simulated aircraft.
Why is the X65F not detected or behaving incorrectly?
Most X65F faults can be isolated by checking whether the same problem appears in Windows Game Controllers.
- Missing from MSFS: connect it before launching the simulator, try a direct USB port and verify that Windows lists it. Relaunch MSFS after reconnecting a legacy controller.
- Present but no axes move: the Windows driver or hardware connection is at fault. Use only software intended for the X65F; X52 and X56 packages are not substitutes.
- Aircraft rolls or pitches hands-off: remove duplicate controller bindings, unload keyboard-emulation profiles and add only a small dead zone if Windows shows genuine centre noise.
- Throttle operates backwards: use the axis reversal option for that assignment. Do not replace the axis with Throttle Increase and Throttle Decrease.
- Throttle jumps instead of moving progressively: remove SST bands or keyboard macros and confirm that the lever produces a continuous axis in
joy.cpl. - Buttons trigger twice: choose either a direct MSFS button assignment or an SST-generated keystroke for that action, not both.
If an axis has an offset centre, incomplete travel or inconsistent endpoints in Windows, complete the relevant joystick and throttle calibration checks before compensating inside MSFS. Simulator sensitivity settings cannot repair a driver-level axis that never reaches its proper range.