Set up CH Products controls in Windows 11: drivers, Control Manager, CH Pro Pedals calibration, axis assignments and troubleshooting.
USB CH Products controls normally need no separate Windows 11 driver: connect them directly, verify every axis and button in joy.cpl, then bind each physical device once inside the simulator. Use CH Control Manager only for legacy mappings or software that cannot handle separate controllers, not for ordinary yoke-and-pedal setup.
This is general guidance for Windows PC simulators, including Microsoft Flight Simulator 2024 and 2020, X-Plane 11 and 12, FSX and Prepar3D. Menu names differ, but the detection, calibration and duplicate-binding principles are the same.
Do CH Products controls need Windows 11 drivers?
USB CH Products controls use Windows' built-in HID and DirectInput support, so Windows 11 normally installs everything required automatically. This applies to USB versions of the CH Flight Sim Yoke, Eclipse Yoke, CH Pro Pedals, Pro Throttle, Throttle Quadrant, Fighterstick and Combatstick.
Device Manager may identify the underlying driver as a Microsoft HID-compliant game controller rather than showing a special CH driver. That is expected. The absence of a separately installed CH Pro Pedals driver or CH Products Flight Sim Yoke driver does not mean the device is incomplete.
Check the connector before spending time on software. Older CH controls with a 15-pin gameport plug are not native USB devices and will not work through a passive plug adaptor. They require an active gameport-to-USB converter, and some converters expose only part of the original controller's axes and buttons.
Where should I get official CH Products drivers?
If you need CH Control Manager, use only the support or download area of the CH Products official website. Avoid third-party driver bundles: basic USB operation does not require them, and an unofficial package can add obsolete virtual-device components without improving detection.
Control Manager is a configuration utility with mapping components, not a mandatory driver for every CH control. An installer being available does not mean it is required for Windows 11.
Do CH Pro Pedals work with Windows 11?
USB CH Pro Pedals work in Windows 11 as a three-axis DirectInput controller: one rudder axis and two independent toe-brake axes. The pedals should appear in joy.cpl without a separate CH Pro Pedals driver.
The raw brake indicators may move in the opposite direction from what a simulator expects. That does not indicate a failed pedal set; reverse the left and right brake axes inside the simulator after confirming that both respond smoothly in Windows.
CH Control Manager on Windows 11: should I install it?
Most Windows 11 users should start without CH Control Manager. Modern simulators can read the yoke, pedals and throttle as separate controllers, which is simpler and avoids physical and virtual devices competing for the same commands.
| Configuration | Choose it when | Main consideration |
|---|---|---|
| Native Windows HID | The simulator recognises each USB controller separately | Best first choice for MSFS, X-Plane, FSX and Prepar3D |
| Control Manager Direct Mode | You already use the utility but do not need a loaded map | The controls remain separate; the utility may add no benefit over native operation |
| Control Manager Mapped Mode | Legacy software cannot handle several devices, or you require a specific combined map, macro or remapping | Virtual controls can cause duplicate inputs if the physical controls are also assigned |
If Windows blocks a legacy Control Manager component or Mapped Mode is unreliable, do not weaken Windows security merely to obtain basic yoke-and-pedal operation. Return to the native HID devices instead. Our Windows 10 and 11 Control Manager installation and mode guide covers the extra steps and compatibility limitations for users who genuinely need it.
How do I configure a CH yoke, pedals and throttle?
- Identify the USB versions. Confirm that every controller has a native USB plug rather than an old gameport connector attached to a passive adaptor.
- Connect one controller at a time. Begin with USB ports on the PC rather than an unpowered hub. Let Windows recognise each device, then keep the controls in the same ports where practical because some simulators may create another device profile after a port change.
- Test each device in Windows. Press
Windows key + R, enterjoy.cpl, select a controller and open its properties. Move every axis through its full travel, press every button and check each hat switch. Our step-by-step Windows controller test explains how to distinguish a binding problem from failed USB detection. - Calibrate only if the raw readings are wrong. Calibration is useful when an axis cannot reach its endpoints or has an incorrect centre. It will not repair flickering, sudden spikes or intermittent disconnections.
- Start the simulator after connecting the controls. Some older simulators enumerate controllers only when they launch. Create a separate profile for each device where profiles are supported.
- Remove automatic conflicts before adding assignments. Clear duplicate rudder, throttle and brake bindings from other controls, including gamepads, twist-grip sticks, yoke levers and throttle mini-sticks.
- Bind analogue controls to axis commands. Use commands containing
Axis, such as elevator axis or throttle axis. Aileron-left, throttle-increase and similar commands are digital button functions and do not provide proportional movement. - Test the cockpit animation and aircraft response. Check direction, full travel and neutral position. On a multi-engine aircraft, move one engine lever at a time to confirm that each assignment controls the intended engine.
Which axes should each CH control use?
| Physical CH control | Typical simulator assignment | Common mistake |
|---|---|---|
| Yoke left and right | Aileron or roll axis | Assigning aileron-left and aileron-right button commands |
| Yoke forward and aft | Elevator or pitch axis | Reversing the axis without checking the aircraft's control column |
| CH Pro Pedals main movement | Rudder or yaw axis | Leaving a joystick twist axis bound to rudder |
| Left and right toe brakes | Left brake axis and right brake axis | Using one combined brake command or failing to reverse both axes |
| Flight Sim Yoke levers | Throttle, propeller and mixture axes | Leaving them active when a separate quadrant controls the engines |
| Throttle Quadrant levers | Individual throttle, propeller, mixture or condition axes | Using the same profile for aircraft with different engine layouts |
| Pro Throttle slider | Throttle axis | Binding another throttle lever to the same command |
| Mini-stick or spare analogue axis | Camera control or unassigned | Allowing an automatic preset to bind it to pitch, roll or throttle |
| Hat switches and buttons | View, trim, push-to-talk or aircraft functions | Assigning one button to conflicting simulator functions |
How should I set up CH controls in MSFS, X-Plane 11, FSX or Prepar3D?
Each simulator should receive clean assignments from the physical controllers unless you have deliberately chosen a Control Manager map.
- Microsoft Flight Simulator 2024 and 2020: inspect the profile for every connected device, including controllers that appear to have an empty or unfamiliar preset. Remove duplicated axes, create named profiles and use the simulator's input search to identify unexpected bindings. Our MSFS controller-profile and sensitivity instructions cover the simulator-side process.
- X-Plane 11 and 12: open
Settings > Joystick, calibrate each recognised CH device, then assign pitch, roll, yaw and both toe brakes. Set every unused analogue input to none rather than leaving X-Plane to guess its purpose. - FSX: select each controller in the controls interface and inspect both button and control-axis assignments. FSX can use separate CH devices, so a combined virtual controller is not normally necessary.
- Prepar3D: check assignments for each listed device and remove axes inherited from automatic defaults. If controls work in Windows but not in Prepar3D, confirm that controller input is enabled before changing drivers.
How do I calibrate CH Pro Pedals in Windows 11?
Calibrate CH Pro Pedals only when joy.cpl shows an incorrect centre or incomplete travel; simulator reversal and response curves are separate settings.
- Open the Windows test panel. Run
joy.cpl, choose CH Pro Pedals and open the device properties. - Test before calibrating. Move the rudder from lock to lock and press each toe brake independently. If all three axes move smoothly through their ranges, leave the Windows calibration alone.
- Start the calibration tool if available. Keep the rudder centred and both toe brakes fully released whenever the wizard requests a neutral position.
- Sweep all three axes fully. Move the rudder to both limits, then press and release each toe brake through its complete travel. Finish with the brakes released.
- Verify the result. Return to the test display. The rudder should settle consistently near centre, while both brake axes should return to the same released position.
If the pedals are smooth in Windows but reversed in the simulator, use the simulator's reverse-axis option. Repeating Windows calibration will not correct a simulator assignment running in the wrong direction.
Why are CH pedals, brakes or throttles behaving incorrectly?
| Symptom | Likely cause | What to do |
|---|---|---|
Controller is absent from joy.cpl | USB connection, hub, gameport adaptor or hardware problem | Connect directly to another PC USB port and inspect Device Manager for a warning |
Controller works in joy.cpl but not in the simulator | Simulator profile, input filter or launch-time detection | Connect before launching, select the correct device profile and search for an input by moving it |
| Aircraft control moves twice or will not stay centred | The same axis is bound on several physical or virtual devices | Clear the duplicate and bind either the native controls or the Control Manager virtual controls, not both |
| Toe brakes remain applied when released | Both brake axes need reversing, or calibration ended with the brakes pressed | Reverse the left and right brake axes separately; recalibrate only if Windows also shows a bad released position |
| Throttle jumps between positions | Duplicate throttle assignments or a fluctuating physical axis | Remove other throttle bindings, then watch the suspect axis in joy.cpl |
| Axis never reaches full travel | Incorrect calibration, restricted simulator range or ageing hardware | Check Windows first, reset and recalibrate once, then inspect simulator range settings |
| Random spikes appear in Windows | Unreliable USB connection or a worn internal sensor | Try a direct USB port; sensitivity and dead-zone changes cannot repair severe raw-input spikes |
| Rudder works but toe brakes do not | Brake axes are unassigned, hidden by a profile or not exposed by a gameport converter | Confirm three axes in Windows before changing simulator settings |
What sensitivity and dead-zone settings should I use?
Start with a linear response, full usable axis range and the smallest dead zone that prevents unwanted movement. There is no universal CH sensitivity value because aircraft handling, simulator flight models and physical wear differ.
Use Windows or Control Manager calibration to establish physical centres and endpoints. Use the simulator's response curves only to change how control movement feels. A modest curve may make a short-travel yoke less abrupt near centre, but a large dead zone creates a lifeless centre followed by a sudden control response.
If an untouched axis flickers in joy.cpl, diagnose the USB connection or hardware before adding a large dead zone. If it is stable in Windows but restless only in one simulator, inspect that simulator's assignments and profile settings.
Can a CH yoke, pedals and throttle be used together?
Yes. Windows 11 and modern flight simulators can use a CH yoke, CH Pro Pedals and a separate throttle or quadrant at the same time without combining them into one virtual device.
A mistake we see constantly is leaving the yoke's built-in engine levers assigned after adding a throttle quadrant. Keep only one assignment for each engine axis unless a second control has a deliberate function. For device pairing and practical control choices, see our CH yoke-and-pedals setup guidance.
Save aircraft-specific throttle profiles where the simulator permits it. A piston single may need throttle, propeller and mixture, while a twin or turboprop requires a different set of individual engine and condition-lever assignments.