Skip to content
General 10 min read 251 views

Can I use CH pedals with a Saitek yoke and throttle?

Ian Stephens
In short

Use CH pedals with a Saitek yoke and throttle on Windows or Bazzite/Linux, with correct USB detection, rudder, toe-brake and axis assignments.

Yes. On Windows, USB CH Pro Pedals can work alongside a Saitek or Logitech G Flight Yoke and throttle quadrant because the simulator reads them as separate controllers. On Bazzite/Linux, the same mixed-brand USB setup may work if Linux and the chosen simulator detect every device, but Windows drivers and instructions do not automatically apply.

This answer covers general PC flight simulation, including Microsoft Flight Simulator 2020 and 2024, FSX, X-Plane and Prepar3D. The brands need not match: assign pitch and roll to the yoke, engine controls to the quadrant, and rudder plus independent toe brakes to the CH pedals.

Older units may carry the Saitek Pro Flight name, while later examples use Logitech G branding. That change does not affect their ability to operate alongside CH hardware.

I am on Bazzite: can I use CH pedals with a Saitek yoke and throttle?

Yes, provided Bazzite detects the physical controllers, the simulator can receive Linux input devices natively or through Proton, and the controls remain available as independent devices.

  • Linux must detect the hardware and its axes. USB enumeration alone is not enough; the rudder and both toe brakes must produce input events.
  • The simulator must support the input path. A native Linux simulator can read Linux devices directly. A Windows simulator running through Proton must also pass those devices to the game correctly.
  • The controllers must remain distinguishable. The CH pedals should appear separately from the yoke. A standalone USB throttle should also be separate, while the quadrant supplied with the classic Saitek yoke normally appears as part of the yoke because it plugs into the yoke itself.

Microsoft Flight Simulator 2020 and 2024 do not have native Linux editions, so running either on Bazzite depends on Proton compatibility. Successfully launching the simulator does not guarantee that every specialist flight-control axis will be exposed.

Bazzite setup checklist

  1. Connect the hardware directly. Plug the yoke and USB CH pedals into direct computer USB ports for initial setup. Connect a bundled Saitek throttle quadrant to the yoke’s dedicated socket; connect a separately sold USB quadrant directly to the computer.
  2. Confirm Linux detection before launching the simulator. Use a Linux or Bazzite controller-test tool in Desktop Mode and move the yoke, throttle, rudder and each toe brake through their full travel. If available, lsusb can confirm that a USB device enumerated, but it does not prove that its axes work. An installed event-testing tool such as evtest can show whether axis events reach Linux.
  3. Check all three pedal axes. The sliding pedal movement should produce one rudder axis, and each toe pedal should produce its own brake axis. If only one combined brake input appears, do not proceed to simulator mapping until the Linux input layer exposes the separate axes.
  4. Inspect Steam Input and other remapping layers. Steam Input or another mapper can create a virtual gamepad in addition to the physical controller, causing duplicate inputs. When the simulator supports raw flight controllers, test with per-game Steam Input disabled. Keep it enabled only when it is the layer required to make the device visible.
  5. Connect the controls before starting the simulator. Some games and Proton configurations enumerate joysticks only during launch. Restart the simulator after changing USB ports or remapping settings.
  6. Assign each device inside the simulator. Map pitch and roll to the yoke, engine controls to the quadrant, rudder to the pedals’ centre axis, and left and right brakes to the separate toe-brake axes.
  7. Save and test a dedicated profile. Check that released brakes show no pressure, full pedal travel reaches both yaw limits, and no virtual gamepad or second controller also owns those axes.

Why does Bazzite see the controllers when the simulator does not?

If a Linux controller tester reads every axis but the simulator does not list the device, the fault is usually in the application, Proton or a remapping layer rather than the USB hardware.

  • Visible in lsusb but absent from controller tests: Linux has enumerated the USB device but is not receiving usable joystick events. Check the physical connection, try a direct port and resolve the Linux input or device-permission problem before opening the simulator.
  • Working in a Linux tester but absent from the game: reconnect the controller before launch, confirm that a sandboxed application has access to input devices, and check whether the simulator or Proton configuration supports raw joysticks rather than only virtual gamepads.
  • Duplicate or oscillating axes: remove one input path. Do not map a physical axis in the simulator while Steam Input or another utility sends a second virtual copy of the same movement.
  • Reversed rudder or brakes: use the simulator’s reverse-axis option for that specific axis. Reverse the two toe brakes separately; do not swap them for a digital brake button.
  • Toe brakes disappear after remapping: a virtual gamepad layer may not preserve all three pedal axes. Prefer direct, raw joystick input when the simulator supports it.
  • Legacy Windows utilities will not install: do not attempt to solve Linux detection by installing old CH or Saitek/Logitech Windows-only drivers and profiling packages through Proton. Windows kernel drivers do not replace Bazzite’s native input handling. Use Linux controller detection and the simulator’s own mappings instead.

Windows-only setup for CH pedals and a Saitek yoke

The following procedure applies to Windows; Bazzite users should use the Linux checklist above rather than joy.cpl or Windows manufacturer software.

  1. Identify the pedal connection. Native USB CH Pro Pedals provide a rudder axis and two toe-brake axes. Older gameport pedals are different, and a passive USB adaptor may not preserve all three axes.
  2. Connect the Saitek throttle correctly. The quadrant supplied with the classic Flight Yoke plugs into the dedicated socket on the yoke and normally appears as part of that controller. Do not connect its plug to a computer’s legacy keyboard or mouse socket. A separately sold USB quadrant connects directly to the PC.
  3. Use direct USB ports initially. Connect the CH pedals and yoke separately. An unpowered or heavily loaded hub, including a hub built into another controller, can cause detection and intermittent disconnection problems.
  4. Test each controller in Windows. Run joy.cpl, open each device’s properties and move every control through its full travel. The pedals should show yaw plus two independently moving toe-brake axes. A bundled throttle may be listed under the yoke rather than under its own name.
  5. Calibrate in Windows where available. Centre the yoke and rudder, release both toe brakes and complete the calibration. Add a small simulator dead zone only if an axis still fails to settle when released.
  6. Inspect every simulator profile. Select the yoke, pedals, throttle, gamepad and any other joystick in turn. Change the controls filter to show all commands if the axis assignments are hidden.
  7. Remove automatic duplicates. Clear rudder, brake, throttle, pitch and roll bindings from devices that should not control them. Gamepad triggers automatically assigned to brakes are a common cause of constant or uneven braking.
  8. Save and flight-test the profile. Test rudder travel and each wheel brake separately. Keeping older controllers in the same USB ports can help FSX and other older simulators retain their device assignments.

For device-specific Windows calibration, see our CH Products yoke and pedal setup instructions.

Which axes should I assign to the rudder pedals?

Assign the pedals’ sliding movement to the rudder or yaw axis, then map each toe pedal to its corresponding proportional brake axis.

ControllerRecommended assignmentsBindings to remove
Saitek or Logitech yokeAileron or roll axis; elevator or pitch axisAny second rudder or brake axis when pedals are fitted
Throttle quadrantThrottle, propeller and mixture axes, or aircraft-specific engine axesConflicting combined and individual engine controls
CH pedalsRudder or yaw axis; left brake axis; right brake axisRudder-left, rudder-right and digital brake buttons used instead of axes

The exact command labels vary between simulators, but choose entries containing axis rather than button-style commands. Pressing only the left toe brake should move only the left brake input; repeat the test on the right.

On twin-tail aircraft, both rudders still respond to one yaw axis. Many light aircraft also link pedal input to nosewheel steering. Larger aircraft may model limited pedal steering and a separate tiller, but a tiller binding is not required for the basic mixed-brand setup.

Microsoft Flight Simulator users can follow our device-by-device guide to mapping a yoke, throttle and independent pedals. For the older simulator’s controls interface, use the FSX axis assignment and Windows calibration procedure.

Why do the rudder and toe brakes work backwards or fight each other?

Reversed brake axes, duplicate assignments and driving assists cause most incorrect pedal behaviour; mixing CH and Saitek hardware is rarely the cause.

  • Brakes remain applied when released: reverse the left and right toe-brake axes individually. Many simulators initially interpret the released position as maximum braking.
  • One pedal applies both brakes: remove any general brake binding and assign the two proportional brake axes separately. Also confirm that the parking brake is released.
  • Rudder jumps fully left or right: bind a continuous rudder axis rather than rudder-left and rudder-right button commands.
  • Rudder drifts around the centre: recalibrate where the operating system supports it, then add only enough central dead zone to stop unwanted movement.
  • Inputs double or oscillate: inspect the yoke, gamepad, joystick and virtual-controller profiles for another rudder or brake assignment. Disable auto-rudder, assisted steering and similar aids after confirming the physical pedals work.
  • Throttle or mixture moves unexpectedly: remove conflicting combined and per-engine axis assignments. Use aircraft-specific profiles when a single-engine and multi-engine aircraft require different layouts.
  • A device disconnects during flight: test it on a direct USB port and remove unnecessary hubs. Power or USB enumeration faults cannot be corrected with sensitivity settings.

A mistake we see often is replacing a reversed toe-brake axis with a general brake button. That may stop the apparent reversal, but it removes proportional and differential braking. Reverse the original axis instead.

If Windows never detects the yoke, quadrant or pedals, work through our USB detection and non-moving-axis checks before changing simulator bindings.

Do CH pedals and a Saitek yoke need matching drivers or software?

No. The controls do not need matching drivers because the pedals and yoke are independent USB input devices.

On Windows, begin with the simulator’s own controller assignments and install manufacturer software only when a supported device feature genuinely requires it. Avoid merging the controls into one virtual device unless a particular older simulator cannot use multiple controllers.

On Bazzite, Windows driver and profiling utilities are not substitutes for native Linux device detection. If you use Steam Input or another mapping layer, assign each axis either there or inside the simulator, not in both places.

Will CH pedals and a Saitek yoke work on Xbox or PlayStation?

Treat this mixed-brand combination as a PC setup. Xbox Series X|S, PlayStation 5 and PS5 Pro recognise only the peripherals supported by the individual simulator and console platform; ordinary Windows or Linux USB detection does not carry across.

Microsoft Flight Simulator 2024 is available on Xbox Series X|S, PS5 and PS5 Pro, but that does not make PC-oriented CH pedals or a Saitek yoke automatically compatible. Microsoft Flight Simulator 2020 remains limited to PC and Xbox. A USB hub adds ports but cannot translate an unsupported controller, so both exact devices must be recognised by the console edition.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members