Fix a YOKO that will not calibrate or assign buttons in FSX, including a greyed-out joy.cpl Calibrate button, missing axes and binding conflicts.
FSX does not calibrate YOKO buttons: it calibrates only analogue axes, while buttons are mapped separately under Buttons/Keys. Confirm that the YOKO responds in Windows Game Controllers (joy.cpl), then select it in FSX, enable controllers, assign pitch and roll under Control Axes, and clear duplicate bindings.
This applies to both the boxed edition of Microsoft Flight Simulator X and FSX: Steam Edition. Their wording differs slightly, but both separate hardware testing, axis assignment, response adjustment and button mapping. Trying to configure a button on the Calibration or Control Axes page will not work.
Where should each YOKO control be configured?
YOKO testing, calibration and assignment take place in different Windows and FSX panels.
| Task | Where to do it |
|---|---|
| Check raw axis and button input | Windows Game Controllers: joy.cpl > Properties > Test |
| Calibrate the hardware range or centre | The YOKO’s supported device procedure, manufacturer utility or Windows calibration wizard when available |
| Assign pitch and roll | FSX Controls > Control Axes |
| Adjust sensitivity and null zones | FSX Controls > Calibration |
| Assign push-buttons or a hat switch | FSX Controls > Buttons/Keys |
How do I check whether Windows detects the YOKO?
Windows must receive the YOKO’s inputs before FSX can assign them.
- Close FSX. Connect the YOKO directly to the computer rather than through a hub or extension, then wait for Windows to recognise it.
- Open Game Controllers. Press Windows key and R, enter
joy.cpl, and select the YOKO. Its displayed name can vary between YOKO generations and Windows installations. - Open Properties or Test. Move the yoke through its complete pitch and roll travel, release it, and press every button. The axis indicators should move smoothly and the button indicators should illuminate.
- Check the hat separately. A hat switch may appear as a POV indicator rather than as numbered buttons; that is normal.
If the YOKO is missing from joy.cpl, change to another direct USB port and restart Windows. If possible, test it on another computer: failure on two machines points towards the device, cable or its hardware configuration rather than FSX.
If an axis or button does not register on the Windows Test page, FSX cannot repair it. Calibration affects analogue axes only; it cannot make a dead button start reporting.
Why is joy.cpl Calibrate greyed out for my YOKO?
A greyed-out joy.cpl Calibrate button usually means that the device does not expose the generic Windows calibration wizard, not that the YOKO has failed.
Use the Test page as the deciding factor. If pitch and roll reach their expected extremes, move smoothly and return close to centre, leave Windows calibration alone and continue with FSX. Small raw fluctuations near the centre are normal; a large offset or restricted travel is not.
If the Test page shows a genuine range or centring problem, use the calibration procedure or utility supplied for that specific YOKO generation. Do not copy a procedure intended for a different model, and do not install an unrelated controller driver simply to enable the Windows button. Reconnect the YOKO and repeat the Test-page check afterwards.
FSX’s Calibration page is separate from the Windows wizard. Its sliders adjust sensitivity and null zones; they do not rewrite the YOKO’s hardware endpoints, and they have no effect on buttons.
How do I calibrate and assign the YOKO axes in FSX?
Assign the YOKO’s analogue axes first, then tune their response with the Calibration sliders.
- Launch FSX with the YOKO already connected. Open Settings and Controls, enable controllers, and select the YOKO from the Controller Type list.
- Open Control Axes. Assign roll to the analogue aileron axis command and pitch to the analogue elevator axis command. Do not use the digital left, right, up or down commands intended for keys and buttons.
- Inspect every other controller. Select any pedals, throttles and gamepads in turn and remove unintended aileron or elevator assignments. FSX commonly creates automatic bindings that cause double inputs.
- Open Calibration with the YOKO selected. Start with high or maximum sensitivity and the smallest practical null zone. Increase the null zone only enough to stop unwanted movement when the yoke is physically centred.
- Verify the direction. Load a default FSX aircraft and compare the cockpit yoke or control surfaces with the hardware. Reverse an axis only when the simulated control moves in the opposite direction.
Judge direction and centring from the cockpit controls, not solely from the aircraft’s flight path. Wind, propeller effects and trim can make an aircraft turn or roll even when the yoke input is centred. If unwanted movement remains, use our sensitivity, null-zone and duplicate-axis checks for an FSX aircraft that pulls to one side.
Why does FSX ignore YOKO button assignments?
FSX normally ignores a YOKO button because the wrong controller or settings tab is selected, the input is not reaching Windows, or another mapping layer is handling the control.
- Open Buttons/Keys. Keep the YOKO selected in the Controller Type list; selecting it on Control Axes does not guarantee that it remains selected on every tab.
- Choose the required FSX command. Open its assignment control and press the YOKO button once. FSX should show a joystick button number, which may not match the label printed on the yoke.
- Check the command type. Assign ordinary momentary buttons to an action or toggle command. Set repeating behaviour low or off for one-shot commands if holding the button causes repeated operation.
- Test during an active flight. Use a default FSX aircraft first. Some complex add-on aircraft use custom events and will not respond to the standard FSX command even though the button is assigned correctly.
If the button illuminates in joy.cpl but FSX does not detect it in the assignment dialogue, confirm that controllers are enabled and restart FSX with the YOKO connected. Temporarily close or bypass any separate controller-mapping software while testing.
With FSUIPC or another external mapping layer, give each axis or button to one system only. Mapping the same physical input in both places can produce duplicate commands, jitter or apparent non-response; our guide to separating FSUIPC and native FSX assignments explains the two workable approaches.
“Det virker stadig ikke” — what if it still does not work?
If it still does not work, identify the first stage at which the input disappears instead of repeatedly changing calibration sliders.
- No YOKO in
joy.cpl: treat this as a USB, Windows or hardware problem. FSX settings are not yet relevant. - Listed in Windows but an input does not react: check the model-specific device configuration and test another USB port or computer. Buttons cannot be fixed through axis calibration.
- Windows works but FSX cannot capture the input: reconnect before launching FSX, enable controllers and verify that the YOKO—not a gamepad or pedals—is selected.
- FSX captures it but the aircraft does not respond: test the same command in a default aircraft. Success there means the add-on aircraft probably expects a custom event.
- Inputs jump, fight or operate twice: disconnect every controller except the YOKO. Reconnect devices one at a time and remove the automatic duplicate assignments FSX creates.
For a broader check covering Windows detection, controller enabling, device selection and duplicate axes, follow our complete FSX controller troubleshooting sequence. Restore default controls only after recording or backing up custom assignments, because a reset removes them.
What if the YOKO assignments disappear after restarting FSX?
Assignments that vanish after a restart indicate a controls-profile, device-identity or write-permission problem rather than failed YOKO calibration.
Keep the YOKO connected to the same USB port or hub path, make the changes while signed into the usual Windows account, and close FSX normally so it can write the configuration. If the settings still disappear, back up existing mappings before resetting anything and use our repair steps for FSX controller settings that will not save.