Can't assign joystick axes in DCS World? Fix a disabled Add button, wrong device columns, undetected hardware, duplicate bindings and corrupt profiles.
In DCS World, joystick axes can only be bound in the correct aircraft’s Axis Commands category and in that controller’s device column. If Add is disabled or movement is not detected, the usual causes are the wrong profile or cell, Windows not seeing the device, duplicate default bindings, or a damaged saved control profile.
How do I make DCS accept a new axis binding?
The reliable method is to verify the hardware first, then bind it from the correct intersection of command row and controller column.
- Test the joystick in Windows. Press Win+R, run
joy.cpl, open the controller’s properties and move every axis. If the indicators do not respond there, DCS cannot use them. Work through our Windows joystick detection and calibration checks before changing anything in the simulator. - Connect the controller before launching DCS. If it was connected or switched between physical and virtual modes while DCS was open, restart the simulator. A direct USB connection is also a useful test when a hub is causing intermittent detection.
- Select the exact aircraft profile. Open Options, then Controls, and choose the aircraft, variant and crew position you intend to fly. General controls and another aircraft’s profile will not configure that cockpit.
- Open Axis Commands. Use the category selector to show analogue commands such as Pitch, Roll, Rudder and Thrust. Clear any search or filter that is hiding the required row.
- Select the correct device cell. Click the cell where the required command row meets the column headed with your joystick’s name. Selecting only the action name, the keyboard column or another USB controller will not bind movement from the joystick.
- Clear and replace the assignment. If a value is already present, select that cell and use Clear. Double-click the empty cell or select Add, then move the intended axis through a substantial part of its travel. Keep other rotaries and mini-sticks still because a noisy axis can be captured instead.
- Check the input with Axis Tune. Select the completed binding and open Axis Tune. The input indicator should move smoothly across its range. Axis Tune changes curves, saturation, dead zone and direction; it does not assign the axis to a different command.
Once the axes are being detected, our complete DCS HOTAS and axis setup walkthrough covers duplicate removal, curves and practical flight-control assignments.
Why is the Add button greyed out in DCS?
The Add button is normally greyed out because DCS does not have an eligible command-and-device cell selected.
- Select a row under Axis Commands, not a button-only command.
- Click inside the column belonging to the physical joystick or throttle.
- Check that the chosen command is available to the selected aircraft and crew station; unsupported cells may be unavailable.
- If the device has no column at all, close DCS and resolve its Windows detection or driver problem first.
A mistake we see constantly is selecting Pitch on the left-hand action list without selecting the Pitch cell beneath the joystick column. DCS needs both pieces of information: what the axis controls and which device supplies it.
Why does DCS detect the axis but control the wrong thing?
DCS usually captures the wrong axis because another rotary moved during assignment or because automatic defaults placed several controllers on the same command.
Inspect the complete Pitch, Roll, Rudder and Thrust rows across every controller column. A throttle mini-stick, rudder pedal or gamepad may have been assigned alongside the main joystick, producing constant input, poor centring or controls that fight each other. Clear only the unwanted cells rather than erasing the whole category.
If the intended axis moves correctly in Axis Tune but backwards in the cockpit, enable Invert. If it jitters around the centre, calibrate it in Windows before adding a small dead zone; a large dead zone should not be used to hide a hardware or driver fault.
Do joystick axis bindings apply to every DCS aircraft?
No. DCS stores flight-control bindings separately for each aircraft, variant, crew station and detected controller identity. An axis working in one module does not prove it is assigned in another, and changing a device’s virtual or combined mode can make DCS treat it as new hardware.
Multicrew aircraft need particular care because pilot, co-pilot and weapon-operator positions may have independent profiles. Our helicopter control configuration example shows how module and crew-station selection affects axis assignments.
Why do joystick axis changes disappear after restarting DCS?
Bindings that work for one session but vanish later usually indicate a saving, permissions or controller-identity problem rather than a failed axis.
- Leave the Controls screen using OK rather than cancelling the changes.
- Make sure the relevant DCS folder under Saved Games is writable and not being blocked by protected-folder security or conflicting cloud synchronisation.
- Avoid repeatedly changing USB operating modes or virtual-controller configurations, which can create a different device identity and therefore a fresh DCS column.
- Back up the relevant aircraft profile beneath
Saved Games\DCS\Config\Input. The DCS Saved Games directory may have a different name on some installations.
If one aircraft profile remains uneditable, close DCS, back up and rename only that module’s input folder, then restart the simulator so it creates clean defaults. Do not delete the entire Input directory unless you are prepared to rebuild every aircraft’s controls. Reinstalling or repairing the main simulator often leaves this fault untouched because user bindings are stored separately under Saved Games.