Fix YOKO yoke calibration and button assignment problems in FSX with Windows checks, correct axis menus, USB fixes and control resets.
FSX calibrates only the YOKO’s analogue pitch and roll axes; its buttons must be mapped separately under Buttons/Keys. If neither works, first confirm Windows sees the yoke in Game Controllers, then select YOKO in FSX, enable controllers, assign the correct axes, and remove duplicate bindings from other devices.
This applies to boxed Microsoft Flight Simulator X and FSX: Steam Edition. The menu wording differs slightly, but both separate axis assignment, axis calibration and button mapping. A mistake we see constantly is trying to configure a yoke button on the Calibration or Control Axes page.
How do I check whether Windows sees the YOKO?
Windows must report the YOKO’s axes and buttons before FSX can use them.
- Close FSX and connect the YOKO before launching it again. For diagnosis, plug it directly into the computer rather than a hub or extension.
- Open Game Controllers by pressing the Windows key and R, entering
joy.cpl, and selecting the YOKO. Its displayed name may vary slightly by model or Windows device identification. - Open Properties or Test, move the yoke through its full pitch and roll travel, and press every button. The axis indicators should move smoothly and the corresponding button indicators should illuminate.
- Calibrate at the Windows or device level if required. If the YOKO model has its own calibration utility, use that in preference to forcing a generic Windows calibration.
If the YOKO is absent from joy.cpl, or its buttons do not register there, this is a USB, device configuration or hardware problem rather than an FSX assignment problem. Try another direct USB port, restart Windows and avoid changing ports after creating your FSX assignments.
How do I calibrate the YOKO axes in FSX?
Assign the axes first, then use FSX calibration only for sensitivity and null-zone adjustment.
- Enable controllers in FSX’s Controls settings and choose the YOKO from the Controller Type list. Separate pedals and throttles must be selected and configured individually.
- Open Control Axes and 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.
- Remove unwanted assignments from every other connected controller. FSX often automatically assigns pitch, roll and throttle to gamepads, throttles or pedal toe brakes, producing double inputs.
- Open Calibration with the YOKO still selected. Start with high or maximum sensitivity and a very small null zone. Increase the null zone only if the centred yoke produces visible control movement.
- Check direction in a default FSX aircraft. Reverse an axis only if the cockpit control moves in the opposite direction.
FSX’s Calibration page does not redefine the YOKO’s raw hardware range; it mainly changes sensitivity and null zones. For a complete check of device order, controller enabling and duplicate bindings, follow our controller detection and axis-clean-up sequence for FSX.
Why does FSX ignore YOKO button assignments?
FSX usually ignores a YOKO button because the wrong controller is selected, the button is being assigned on the axis page, or another mapping layer has claimed it.
- Open Buttons/Keys and select the YOKO in the controller list.
- Choose the required simulator command, open its assignment control and press the YOKO button once. FSX should display a joystick button number.
- Clear conflicts where the same physical button or command has been assigned on another device. Keyboard assignments can remain unless they cause a genuine conflict.
- Test in a default aircraft. Some complex add-on aircraft use custom systems that do not respond to the standard FSX event, even though the button assignment itself is valid.
If you use separate controller-mapping software, choose one mapping method for each control. Either assign that axis or button directly in FSX, or let the external mapping layer handle it; assigning the same input in both places can create repeated commands, jitter or apparent non-response.
A maintained two-position switch can also behave badly when mapped to a toggle command. Where FSX offers separate on and off events, use those; ordinary momentary push-buttons are normally suitable for toggle commands.
| Symptom | Most likely cause | Next action |
|---|---|---|
YOKO is missing from joy.cpl | USB, Windows or device-level fault | Change to a direct USB port and resolve Windows detection first |
| Windows sees it, but FSX does not | FSX was opened before connection, controllers are disabled or its control profile is damaged | Reconnect before launch, enable controllers and restore default controls if necessary |
| Axes work but buttons do not appear in Windows | Device configuration or hardware issue | Check the YOKO’s device-level configuration before changing FSX |
| Button is accepted but does nothing in one aircraft | The aircraft uses a custom event | Test the same command in a default FSX aircraft |
| Controls jump or move without input | Duplicate axes or competing mapping software | Remove the duplicate assignment rather than adding a large null zone |
What if the assignments disappear after restarting FSX?
Assignments that vanish after restart indicate a controls-profile or write-permission problem, not failed YOKO calibration.
Close FSX normally after making assignments and keep the YOKO in the same USB port. If settings still disappear, back up your mappings before restoring the default controls profile; our steps for repairing FSX controller settings that will not save cover profile corruption, permissions and configuration resets without treating the yoke as faulty.