Learn how to program a Saitek X45 HOTAS: bind axes and buttons, use SST modes safely, stop duplicate inputs and fix common Windows issues.
To program a Saitek X45 HOTAS, first verify every axis and button in Windows, then create a dedicated profile inside your flight simulator. Bind pitch, roll, throttle and rudder as axes, assign essential buttons, and add dead zones. Use Saitek SST only when you need modes, shifted commands or keyboard macros.
Should you use simulator bindings or Saitek SST?
Use the flight simulator’s own control system for axes and ordinary buttons; reserve Saitek Smart Technology (SST) for functions the simulator cannot handle directly.
| Method | Best used for | Main limitation |
|---|---|---|
| Simulator control profile | Flight axes, throttle, rudder, views and normal button commands | The X45 mode dial may provide little or no extra functionality |
| Saitek SST profile | Mode-dependent commands, pinkie-shift layers, key combinations and specialised macros | Legacy software can be troublesome on modern Windows versions |
If Windows already detects every X45 control, you do not need SST merely to assign ordinary simulator functions. The original profiler becomes useful when one physical button must perform different commands in Modes 1, 2 and 3.
Because the X45 is legacy hardware, do not install software intended for the X52 or newer controllers. Our guidance on connecting and configuring older Saitek controls on Windows 11 covers the driver and compatibility issues separately.
How do I create a Saitek X45 control profile?
- Connect the complete HOTAS. Join the stick and throttle using their supplied interconnect before plugging the unit into USB. Use a direct computer USB port during initial setup rather than an unpowered hub.
- Test it in Windows. Run
joy.cpl, select the X45 and open its properties. Move every axis through its full travel, press every button and check each hat. Follow our Windows joystick testing procedure if anything is missing or stuck. - Create a separate simulator profile. Avoid modifying a working keyboard, gamepad or generic joystick preset. Give the X45 its own profile so unwanted defaults are easier to identify.
- Clear duplicate assignments. Search each main axis and remove any second binding from the mouse, keyboard, gamepad or another controller. A mistake we see constantly is both the throttle lever and a rotary being assigned to throttle.
- Bind analogue controls as axes. Choose commands labelled as an axis, not commands such as increase, decrease, left or right. Move the desired control when the simulator asks for an input.
- Assign essential buttons. Start with trim, brakes, view controls, autopilot disconnect and push-to-talk if used. Add aircraft-specific commands only after the basic profile works.
- Tune the response. Apply the smallest dead zone that stops unwanted movement. Confirm that each axis still reaches its full minimum and maximum, then adjust sensitivity or response curves if the aircraft feels too sharp around the centre.
Microsoft Flight Simulator 2020 and 2024 may require a manually created profile rather than supplying a complete X45 preset. Our MSFS joystick profile instructions show how to expose all commands, remove duplicate inputs and tune the primary axes.
Which X45 controls should be assigned to each axis?
The stick, throttle lever and rudder rocker should operate flight-control axes, while the two rotary controls are optional because older X45 potentiometers can become noisy.
| X45 control | Recommended assignment | Setup advice |
|---|---|---|
| Stick left and right | Aileron or roll axis | Reverse only if the cockpit yoke moves opposite to the stick |
| Stick forward and back | Elevator or pitch axis | Use a small centre dead zone only if the aircraft pitches without input |
| Throttle lever | Throttle axis or all-engine throttle | Enable the simulator’s reverse-axis option if idle and full power are swapped |
| Throttle rudder rocker | Rudder or yaw axis | Do not also assign the stick’s horizontal axis to rudder |
| Rotary controls | Propeller, mixture, zoom or trim axis | Leave an unstable rotary unassigned rather than masking severe jitter with a large dead zone |
| POV hat | Cockpit view or camera pan | Bind it as a hat where possible instead of eight separate keyboard commands |
A worn rotary or throttle can send constant tiny changes that override the autopilot or other controls. Watch the Windows test indicator without touching the controller; calibration can correct range errors, but it cannot repair a physically noisy potentiometer.
How do the X45 mode dial and pinkie switch work?
The mode dial and pinkie switch gain their intended layered behaviour through an SST profile rather than through ordinary axis assignments.
- Create an X45 profile in SST. Leave pitch, roll, throttle and rudder under the simulator’s control.
- Program buttons with the simulator’s existing keyboard commands. Use the exact key or key combination shown in that simulator’s controls menu.
- Assign commands separately for each mode. For example, one hat could control cockpit views in Mode 1 and radio or autopilot functions in Mode 2.
- Use the pinkie switch as a shift layer only if needed. Too many layers make commands difficult to remember and can leave a button apparently inactive when the wrong mode is selected.
- Activate the profile before starting the flight. Run SST and the simulator at the same Windows privilege level, preferably both normally rather than one as administrator.
Remove the corresponding native joystick binding when SST turns that button into a keystroke. Otherwise one press can trigger both the joystick command and the emulated keyboard command. Timed macros are also poor choices for engine starts or automated cockpit sequences because they depend on the aircraft’s state and timing.
Why is the Saitek X45 detected but not working correctly?
- No device in Windows: reseat the HOTAS interconnect and USB cable, try a direct USB port and check whether Windows reports an unknown device. This is a connection or driver problem, not a simulator binding problem.
- Windows works but the simulator does not: select the correct X45 profile, display all available commands and bind the analogue versions of the axes.
- The aircraft turns or changes power by itself: clear duplicate controller assignments and inspect every X45 axis for jitter.
- The throttle operates backwards: toggle the simulator’s reverse-axis setting rather than programming the lever as keyboard commands.
- SST buttons produce nothing: confirm that the profile is active, the simulator window has focus and both applications use the same privilege level.
- A command fires twice: remove either the native joystick assignment or the SST-generated keystroke for that button.
Diagnose the X45 in this order: hardware connection, Windows input test, simulator axis bindings, then SST programming. That separation prevents a driver fault, duplicate binding or worn control from being mistaken for a bad profile.