Learn how to set up CH Products controls in Windows 11, assign yoke, pedal and throttle axes, and fix duplicate or reversed inputs.
Connect each CH Products controller directly by USB, confirm the yoke, pedals and throttle in Windows 11 with joy.cpl, then create a clean profile in the simulator and assign each axis once. Calibrate only where needed, set small dead zones, and remove automatic duplicate bindings—especially rudder, toe brakes and throttle.
Do CH Products controls need Windows 11 drivers?
USB versions of CH Products yokes, pedals and throttles normally work through Windows’ standard HID and DirectInput support. They do not usually require a separate driver before general PC flight simulators such as Microsoft Flight Simulator, FSX, Prepar3D or X-Plane can detect them.
The older CH Control Manager software is not a prerequisite for normal USB operation. We recommend leaving it out unless an older simulator genuinely requires a single combined virtual controller; its virtual devices and mappings can otherwise create duplicate inputs or hide the physical controllers.
Check the connector before troubleshooting software. Old CH hardware with a 15-pin gameport plug is not the same as the USB version and will not work natively through a passive USB adaptor. It requires a suitable active converter, and not every converter exposes all axes or buttons correctly.
How do I configure a CH yoke, pedals and throttle?
- Connect one device at a time. Start with motherboard USB ports rather than an unpowered hub. Let Windows recognise the yoke, pedals and throttle separately, then keep them in the same ports where practical so simulator profiles are less likely to be reassigned.
- Test every controller in Windows. Press
Windows key + R, enterjoy.cpland open each device’s properties. Move the yoke through pitch and roll, slide the pedals, press both toe brakes and sweep every throttle lever. Our Windows controller testing checklist explains what smooth, full-range input should look like. - Calibrate only when the raw movement is wrong. If the device’s properties offer a calibration wizard, centre the yoke and rudder when requested and leave the toe brakes fully released. Move every axis through its complete travel. Calibration fixes centres and endpoints; it does not repair spikes caused by a noisy potentiometer or unreliable USB connection.
- Create separate simulator profiles. Give each physical controller its own clean profile where the simulator supports profiles. Inspect the default assignments before adding anything because automatic presets often bind the same rudder, throttle or brake command to several devices.
- Assign axes rather than directional buttons. Bind pitch, roll, yaw and analogue levers to commands containing
Axisor their simulator’s equivalent. Commands such as aileron left, aileron right or throttle increase are intended for buttons and will not provide proportional control. - Test from the cockpit. Confirm that the control column, rudder pedals, brakes and engine levers move in the correct direction and remain still when untouched. Test each throttle lever separately on a multi-engine aircraft.
Which axes should each CH controller use?
| Physical control | Typical simulator assignment | Common mistake |
|---|---|---|
| Yoke left and right | Aileron or roll axis | Binding aileron-left and aileron-right buttons |
| Yoke forward and aft | Elevator or pitch axis | Reversing pitch because the cockpit animation looks unfamiliar |
| Pedal movement | Rudder or yaw axis | Leaving another controller bound to rudder |
| Left and right toe brakes | Left brake axis and right brake axis | Using one combined brake command or leaving the axes reversed |
| Single throttle lever | Throttle axis | Binding both the yoke throttle and a separate throttle unit |
| CH Throttle Quadrant levers | Individual throttles, propeller controls or mixture controls | Using one profile for aircraft with different engine layouts |
| Mini-stick or spare analogue axis | Camera control or unassigned | Allowing an automatic preset to bind it to pitch, roll or throttle |
Microsoft Flight Simulator 2020 and 2024 treat the USB units as separate devices, so examine every device profile when removing conflicts. Our MSFS controller-profile workflow covers axis detection, profile creation and binding tests.
FSX and Prepar3D also support separate controllers, but assignments may be divided by device in the controls interface. The same rudder, toe-brake and duplicate-binding principles in our FSX yoke-and-pedal configuration guide apply to CH hardware. In X-Plane, calibrate each recognised device in its joystick settings and mark unused analogue inputs as unassigned.
Why are the brakes, pedals or throttle working backwards?
A reversed axis is normally an assignment setting, not a Windows fault. Use the simulator’s reverse-axis option and verify the result visually: released toe brakes must show no braking, pressing the right pedal must apply the right brake, and advancing a throttle must increase power.
- Brakes remain applied: reverse each toe-brake axis, remove any unwanted combined brake axis and recalibrate with both pedals released.
- Rudder moves without pedal input: clear rudder assignments from the yoke, throttle mini-stick, gamepad and any twist-grip joystick.
- Throttle jumps between positions: remove the duplicate throttle assignment from the yoke’s built-in lever or another controller.
- Several controls move together: disable old CH Control Manager maps or virtual devices and bind the physical USB controllers separately.
What sensitivity and dead-zone settings should I use?
Start with a linear response, minimal dead zone and full axis range. Add only enough dead zone to stop small centre jitter; a large dead zone makes the aircraft unresponsive around neutral and then produces an abrupt control input.
Use Windows calibration to establish the physical centre and endpoints, then use the simulator’s response curves to alter handling. If an axis cannot reach full travel in joy.cpl, fix that before increasing simulator saturation. Severe flickering or sudden jumps usually indicate a connection or ageing hardware problem rather than sensitivity that needs tuning.
Can a CH yoke, pedals and throttle be used together?
Yes. Modern flight simulators can read the CH yoke, pedals and throttle as separate USB controllers, so combining them into one virtual device is unnecessary. A mistake we see constantly is keeping every default binding and then adding another set on top.
Save aircraft-specific throttle profiles where possible. A basic piston single may use throttle, propeller and mixture, while a twin may need separate engine controls. If a separate quadrant is handling the engines, leave the yoke’s built-in throttle axes unassigned or give them deliberate secondary functions.