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

On PC, connect the CH Eclipse Yoke and CH Throttle Quadrant as separate USB devices, verify both in Windows, then create a separate MSFS control profile for each. Bind yoke movement to the aileron and elevator axes, assign the quadrant by engine, clear duplicate mappings, calibrate, and add only enough dead zone to stop jitter.

This procedure applies to Microsoft Flight Simulator 2020 and 2024 on PC. Their control screens differ, but the binding principles are the same. For a closer look at device detection and profile management, see our full MSFS PC controller workflow.

Prepare both CH controllers in Windows

Windows must show clean, full-range input from both devices before MSFS can configure them correctly.

1. Connect both devices before starting MSFS. For initial troubleshooting, plug them directly into the PC rather than an unpowered hub.
2. Open Windows Game Controllers. Press Win+R, enter joy.cpl, and confirm that the Eclipse Yoke and CH Throttle Quadrant appear separately.
3. Test every axis. Move the yoke, paddles and levers through their full travel. Calibrate each device through its Properties panel if the centre or endpoints are wrong.
4. Avoid unnecessary virtual-device software. MSFS can normally use the CH controllers as standard Windows USB devices. An active CH virtual map plus the physical controllers can produce double inputs.

If either controller is absent from joy.cpl, changing MSFS bindings will not fix it. Try another USB port, reconnect the device and restart the simulator after Windows recognises it.

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

Create one editable preset for the Eclipse Yoke and another for the quadrant, then assign only the controls that belong to each device.

1. Select the Eclipse Yoke. Open the MSFS Controls screen, choose the yoke from the device list and duplicate the default preset or create a new empty one.
2. Inspect automatic assignments. Remove any unwanted throttle, propeller, mixture or rudder mappings before adding new ones. Set the filter to show all commands when a required axis is hidden.
3. Bind the primary yoke axes. Assign left-right movement to Ailerons Axis and fore-aft movement to Elevator Axis. Use the axis commands, not the separate left, right, up or down button commands.
4. Select the CH Throttle Quadrant. Create its own preset and assign the six levers according to the aircraft layout you intend to fly.
5. Test each assignment immediately. The on-screen input indicator should move smoothly through its full range and in the correct direction.
6. Save and name the presets clearly. Use separate quadrant presets for single-engine piston, twin-engine piston and jet aircraft rather than rebuilding the same bindings before every flight.

Which CH Throttle Quadrant layout should I use?

Choose generic axes when one lever should move every engine, and engine-specific axes when each engine needs an independent lever.

• Single-engine piston: assign three levers to throttle, propeller and mixture. Leave the other three unassigned or use them for aircraft-compatible functions such as spoilers and flaps.
• Twin-engine piston: use two throttle levers, two propeller levers and two mixture levers, each assigned to the matching engine number.
• Twin-engine jet: assign separate throttle axes to engines 1 and 2. Spare levers can operate spoilers or flaps if that aircraft accepts continuous axis input.
• Single-lever turbine: start with a generic throttle axis. Propeller or condition-lever behaviour varies by aircraft, so a dedicated aircraft preset may be required.

Never bind both a generic throttle axis and Throttle 1 Axis/Throttle 2 Axis to the same physical lever. That common mistake causes mismatched cockpit levers and engines that refuse to remain at idle. Our combined and per-engine throttle guide explains the axis choices and reverse-thrust options in more detail.

What should I do with the Eclipse Yoke's built-in levers?

Leave the Eclipse's built-in throttle, propeller and mixture levers unassigned when the separate CH quadrant is performing those jobs.

They can instead become spare controls for a particular aircraft, but do not map them to the same engine axes as the quadrant. Likewise, assign the Eclipse paddles to rudder only if you have no rudder pedals; otherwise, clear their rudder binding.

If the Eclipse trim wheels are detected as button-like inputs, bind them to incremental elevator-trim commands rather than forcing them onto an analogue axis. Check that each direction operates the correct trim command and that another device is not also controlling trim.

Why are the controls reversed, jittering or moving twice?

Reversed movement usually needs one MSFS axis inversion; jitter and double movement normally indicate calibration trouble or duplicate bindings.

• Axis moves backwards: enable the reverse-axis option for that specific binding. Do not invert it in both Windows software and MSFS.
• Cockpit control moves twice or snaps back: search the assigned controls on every connected device. Clear duplicate axes from the Eclipse's built-in levers, another joystick, a gamepad or an active CH virtual controller. If the preset is heavily auto-mapped, clear or reset the conflicting controller bindings before rebuilding it.
• Yoke jitters around centre: confirm the same movement appears in joy.cpl, recalibrate if necessary, then add the smallest dead zone that produces a stable centre. Our dead-zone and response-curve guidance covers this fine-tuning without making pitch and roll feel numb.
• Lever will not reach idle or full power: recalibrate its Windows endpoints and check the MSFS sensitivity screen. Use a normal zero-to-100-per-cent throttle command when the lever is intended to cover idle through full power only.
• Controls move without input: disable AI piloting or control assistance and check whether the autopilot is commanding the aircraft. These are different from a hardware fault.

How should reverse thrust and quadrant detents be set?

Use the quadrant's normal lever travel for forward thrust and configure its detent or switch input separately when the aircraft requires reverse thrust.

A lower detent does not automatically create a usable negative throttle range in every MSFS aircraft. If it registers as a button, bind it to the aircraft-appropriate reverse-thrust hold, toggle or throttle-decrease command. Add-on aircraft may require calibration through their own cockpit tablet or configuration system, so keep a separate profile when its throttle logic differs from the default aircraft.

Finish by loading a simple aircraft with the engines running and verify roll, pitch, rudder and every lever from full minimum to full maximum. The cockpit controls should follow one device only, move in the expected direction and remain steady when released.