How do I set up a CH Eclipse Yoke and Quadrant in MSFS?

To set up a CH Eclipse Yoke and separate CH Throttle Quadrant in Microsoft Flight Simulator on PC, connect both before launch, verify them in joy.cpl, create one control preset per device, bind the analogue axis commands rather than button directions, remove duplicate assignments, then calibrate and add only enough dead zone to stop jitter.

This applies to Microsoft Flight Simulator 2020 and 2024 on Windows PC. Their control screens differ, but the axis and profile principles are the same; our guide to MSFS device profiles, filters and binding searches explains the broader controls interface. CH USB hardware should not be assumed to work on Xbox or PlayStation simply because the console has a USB socket.

Here, “Eclipse” means the CH Products Eclipse Yoke controller, not an Eclipse aircraft add-on. The Eclipse already has three small engine-control levers; the separate CH Throttle Quadrant adds six larger lever axes and appears as another USB controller.

Does the CH Eclipse Yoke work with Microsoft Flight Simulator?

The CH Eclipse Yoke works in MSFS on PC as a standard Windows USB game controller, normally without virtual-device or mapping software.

MSFS may provide an automatic preset, but it is safer to inspect every assignment or start with a clean custom preset. Automatic mappings can place pitch, roll, rudder or throttle commands on more than one connected device, causing controls to jump or fight each other.

Prepare the CH yoke and throttle in Windows

Both controllers must produce clean, full-range input in Windows before changing any MSFS sensitivity or bindings.

1. Connect both devices before opening MSFS. During troubleshooting, use direct PC USB ports rather than an unpowered hub. Once the controls are stable, a suitable powered hub may be used if needed.
2. Open Windows Game Controllers. Press Win+R, enter joy.cpl and press Enter. The Eclipse Yoke and CH Throttle Quadrant should appear as separate devices; the Eclipse’s built-in levers remain part of the yoke device.
3. Test the Eclipse. Open its Properties panel, centre the yoke without touching it, then check roll, pitch, paddles, built-in levers, trim controls and buttons. Pitch and roll should return to a stable centre.
4. Test all six quadrant levers. Move each from minimum to maximum and through any detent. Check whether movement below a detent registers as additional axis travel or as a button press.
5. Calibrate only when necessary. Use the Windows calibration option if the centre or endpoints are wrong. Do not use an MSFS response curve to conceal an axis that cannot reach its proper Windows endpoints.
6. Check for a virtual controller. If CH mapping software has created a combined or virtual device, avoid feeding both that device and the original physical controllers into MSFS. Choose one arrangement, or duplicate inputs will result.

If an axis is off-centre, reversed or unable to reach its endpoints in Windows, follow our step-by-step CH USB yoke calibration checks before configuring the simulator. If a device is absent from joy.cpl, MSFS bindings cannot repair it; reconnect it, try another USB port and restart the simulator after Windows recognises it.

How do I bind the CH Eclipse Yoke and quadrant in MSFS?

Create an editable preset for each device, clear inappropriate automatic assignments and bind each moving control to an axis command.

1. Open the MSFS Controls screen. Select the Eclipse Yoke from the connected-device list. Duplicate its default preset or create a clean preset, depending on which option your MSFS version presents.
2. Show all assigned commands. Use the assigned-control filter first to find unwanted mappings, then show all commands when searching for a new axis. Clear throttle, propeller, mixture or rudder assignments that another device will handle.
3. Bind roll and pitch. Set left-right yoke movement to Ailerons Axis and fore-aft movement to Elevator Axis. Do not use the separate left, right, up or down button commands for an analogue yoke.
4. Decide how to use the paddles. Bind them to Rudder Axis only when you have no rudder pedals. Otherwise, leave that axis unassigned.
5. Select the CH Throttle Quadrant. Give it a separate preset and assign each lever according to the aircraft’s engine layout. Move only the intended lever when using input detection so that another noisy axis is not captured by mistake.
6. Check direction and range. The on-screen input indicator should move smoothly from end to end. Apply MSFS’s reverse-axis option only to bindings that move backwards.
7. Name and save the presets. Clear names such as “Single piston”, “Twin piston” and “Twin jet” make it harder to load the wrong quadrant layout later.

Should I use a single axis or Throttle 1 Axis?

Use a single generic throttle axis when one lever should command every engine; use Throttle 1 Axis, Throttle 2 Axis and equivalent numbered commands when each engine needs its own lever.

For a twin, bind the first physical lever to engine 1 and the second to engine 2. Do not bind either lever to both a generic throttle axis and an engine-specific axis. That duplicate arrangement is a common cause of cockpit levers moving together, separating unexpectedly or refusing to remain at idle.

Some MSFS versions present both a normal throttle axis and a labelled zero-to-100-per-cent variant. Choose the zero-to-100 option when the physical lever covers forward idle to full power and reverse will be commanded separately. Use a full-range option only when the aircraft supports it and you intend to calibrate part of the lever travel for reverse.

Which CH Throttle Quadrant layout should I use?

The correct CH throttle layout depends on whether the aircraft has one engine, independently controlled engines or specialised condition and reverse ranges.

• Single-engine piston: assign three levers to generic throttle, propeller and mixture axes. Leave the others clear or use them for compatible flap, spoiler or cowl-flap controls.
• Twin-engine piston: assign two throttles, two propeller controls and two mixtures to their matching engine numbers.
• Twin-engine jet: use separate throttle axes for engines 1 and 2. Spare levers may control spoilers or flaps if that aircraft accepts a continuous axis for them.
• Single-lever turboprop or turbine: begin with a generic throttle axis. Propeller, condition-lever and beta-range behaviour varies by aircraft, so keep a dedicated preset when its control logic differs.
• Aircraft with custom throttle calibration: make the basic MSFS bindings first, then perform any calibration required by the aircraft’s own cockpit tablet or configuration panel.

What should I do with the Eclipse Yoke’s built-in levers and trim wheels?

Leave the Eclipse’s built-in throttle, propeller and mixture levers unassigned when the separate CH Throttle Quadrant performs those functions.

Mapping both sets to the same engine controls does not provide a harmless backup. Small electrical movement from an unused lever can override the quadrant, making the cockpit throttle jump or drift.

• Built-in engine levers: clear their engine-axis bindings or repurpose them only for aircraft-specific controls that are not already assigned elsewhere.
• Fingertip paddles: use them for rudder only without pedals. If pedals are fitted, clear the Eclipse rudder binding and confirm that no gamepad is also controlling rudder.
• Trim wheels: identify how each registers before binding it. If it produces button-like pulses, use incremental trim-up and trim-down commands. If it appears as an analogue axis, use a trim axis only when the aircraft handles positional trim correctly.
• Buttons and hat switch: assign views, trim, flaps, landing gear or autopilot functions to taste, checking first that the default preset has not placed the same command on another button.

Separate pedals require another device profile and another duplicate-axis check; our CH yoke-and-pedals setup notes cover rudder and toe-brake assignments.

Why is the CH yoke reversed, jittering or moving twice?

Reversed movement needs one axis inversion, while jitter, snapping and double movement usually point to poor calibration or two devices controlling the same command.

If the signal jitters in joy.cpl, increasing the MSFS dead zone only masks the problem. If Windows is stable but MSFS is not, check the active preset, sensitivity settings and duplicate assignments first.

How should reverse thrust and CH quadrant detents be configured?

Use the main lever travel for forward thrust and configure a below-detent button or reverse range separately according to the aircraft’s throttle system.

A CH quadrant detent does not automatically become analogue reverse thrust. If movement below it registers as a button, bind that input to the reverse-thrust hold, toggle or throttle-decrease command accepted by the aircraft. Test one command at a time because different aircraft do not all interpret reverse commands identically.

Aircraft with custom throttle calibration may expect the full lever and detent positions to be set through an in-cockpit configuration tool. Keep a dedicated aircraft preset rather than changing a working general-purpose jet profile.

How do I test the finished CH Eclipse flight simulator setup?

Test every axis in a simple aircraft with the engines running, control assistance disabled and the autopilot disconnected.

1. Check the yoke. Move roll and pitch slowly through their complete range, release the yoke and confirm that the cockpit control returns to a stable centre.
2. Check rudder input. Verify that only the Eclipse paddles or the pedals move the rudder—not both.
3. Check each engine lever. Move one quadrant lever at a time and watch the matching cockpit control from minimum to maximum.
4. Load a twin-engine aircraft. Confirm that engine 1 and engine 2 can be moved independently and that neither follows an unused generic axis.
5. Test detents last. Verify reverse, cut-off or button actions only after normal forward travel works correctly.

The finished profiles should give each flight control one clear input source, full usable travel and a stable resting position. If changing aircraft breaks that arrangement, create an aircraft-specific quadrant preset rather than altering the known-good general profile.