Learn how CH Products controllers work with modern flight simulators, including PC compatibility, setup steps and fixes for common control issues.
Yes. USB CH Products controllers generally work with modern PC flight simulators, including Microsoft Flight Simulator 2020 and 2024, X-Plane, Prepar3D and DCS. Windows recognises them as standard game controllers, though most users must assign axes and buttons manually. Older gameport models are not directly compatible.
Which modern flight simulators support CH Products controllers?
The USB versions of CH yokes, joysticks, pedals and throttles work with the main desktop flight simulators through standard USB HID or DirectInput support.
| Simulator or platform | What to expect |
|---|---|
| Microsoft Flight Simulator 2020 and 2024 on PC | Compatible, but the default preset may be empty or incomplete. Manual axis and button assignments are often required. |
| X-Plane on desktop | USB models can normally be calibrated and assigned directly. CH Control Manager features are unavailable outside Windows. |
| Prepar3D and DCS on Windows | Compatible as separate input devices. Check for automatic assignments that duplicate pitch, roll, yaw or throttle controls. |
| Xbox and PlayStation console releases | Not natively supported as generic PC USB controllers. Use hardware explicitly supported by the console and simulator. |
Microsoft Flight Simulator 2024 being available on Xbox Series X|S and PlayStation 5 does not make CH's PC controllers console-compatible. The shop or launcher used for a PC simulator makes no difference because controller detection occurs at operating-system and simulator level.
USB is the dividing line. Older CH hardware with a 15-pin gameport connector cannot be plugged directly into a modern PC. A simple passive plug adaptor usually cannot convert its analogue signals and buttons into a usable USB controller; an active conversion solution or replacement USB model is required.
Do I need CH Control Manager?
No. Modern Windows flight simulators can use USB CH controllers in their native mode without CH Control Manager.
The utility is useful when you need a combined virtual controller, shifted button layers or custom mappings. Because it is legacy software, native USB operation is the safer starting point on modern Windows. Our CH Control Manager setup and operating-mode guide explains when installing it is helpful and when it is better avoided.
A mistake we see constantly is binding both the physical CH devices and a Control Manager virtual device. That produces doubled axes, unexpected button presses or controls that appear to fight each other. Choose either native devices or the mapped virtual controller for a given profile, not both.
How do I set up a CH yoke, pedals or throttle?
Set up each controller separately at Windows level first, then bind it inside the simulator.
- Connect directly to the PC. Avoid an unpowered hub during initial setup, and keep each controller in the same USB port once profiles have been created.
- Test it in Windows. Run
joy.cpl, select each CH device and open its properties. Confirm that every axis moves through its range and that the buttons respond. If it fails here, changing simulator settings will not fix it. - Bind one device at a time. Assign pitch and roll to the yoke or stick, yaw to the pedals, each toe brake to its own axis, and the required engine controls to the throttle. Clear unwanted automatic assignments as you work.
- Check direction and sensitivity. Reverse any axis that moves the wrong way. CH toe-brake axes commonly need reversing, and older potentiometers may benefit from a small dead zone.
- Save aircraft-specific profiles. A single-engine throttle arrangement will not necessarily suit a twin-engine aircraft, helicopter or fighter. Separate profiles prevent later assignments from overwriting a working layout.
Microsoft Flight Simulator users can follow our detailed MSFS joystick detection, calibration and binding walkthrough for the simulator-specific steps.
Why isn't my CH controller working properly?
Diagnose CH controller faults at the Windows input layer before changing simulator profiles.
- Not detected: try a direct USB port, reconnect the device and check
joy.cpl. If Windows cannot see it, neither can the simulator. - Controls move twice or fight each other: remove duplicate assignments and check whether both native and Control Manager virtual devices are active.
- Toe brakes remain applied: bind them as analogue brake axes rather than buttons, then reverse their direction in the simulator if necessary.
- Throttle or mixture moves backwards: use the simulator's reverse-axis option rather than physically recalibrating an otherwise correct controller.
- Axis jitters or spikes: test the movement in
joy.cpl. A small dead zone can hide minor centre noise, but spikes visible in Windows usually indicate a USB, wiring or worn-potentiometer problem. - A saved profile disappears after moving USB ports: Windows may register the controller as a new device instance. Return it to its previous port or create and save a fresh binding profile.
- It works in Windows but not in the simulator: create a clean controller profile and assign one essential axis manually. This distinguishes a bad preset from a hardware problem.
There is no need to replace working CH equipment merely because it is old. Keep it if every axis moves smoothly and the device stays connected; consider repair or replacement when spikes persist in joy.cpl, disconnects continue on a direct USB port, or you require console support or force feedback. No software profile can repair a worn potentiometer.