Can't assign joystick axes in DCS World? Fix greyed-out Add, no command available errors, device cells, joy.cpl detection and Saved Games profiles.
DCS World only accepts a joystick axis when you select an analogue command in the correct aircraft or crew-station profile and the cell under that controller’s column. A greyed-out Add button or “No command available for this device” usually means the wrong category, command row, device cell or Windows device identity is selected.
What is stopping the axis assignment?
| Symptom | Likely cause | First check |
|---|---|---|
| The controller has no column | Windows or DCS has not detected it | Test it with joy.cpl, reconnect it and restart DCS |
| Add is greyed out | No eligible command-and-device cell is selected | Select an Axis Commands row and the cell beneath the joystick’s column |
| “No command available for this device” appears | The selected command cannot be assigned in that device column | Check the aircraft, category, row and column |
| The wrong control moves | A noisy axis was captured or duplicate defaults exist | Inspect the entire command row across every controller |
| It works in one aircraft only | DCS uses aircraft-specific control profiles | Repeat the assignment in the intended aircraft and seat |
| The binding disappears after restarting | A Saved Games or device-identity problem is preventing reuse | Check write access and whether the controller’s identity changed |
How do I make DCS accept a joystick axis?
The dependable method is to confirm that Windows sees the hardware, then bind the axis at the intersection of the correct command row and controller column.
- Test the controller in Windows. Press Win+R, enter
joy.cpl, open the controller’s properties and move each axis. If the relevant indicator does not respond, DCS cannot bind that movement. Use our Windows joystick detection and calibration checks before changing simulator profiles. - Start DCS with the device connected. DCS may detect hot-plugged hardware, but restarting with every stick, throttle, pedal set and gamepad already connected gives a cleaner test. Try a direct USB connection if a hub is intermittently dropping the device.
- Select the exact aircraft profile. Open Options, then Controls, and choose the aircraft, variant and crew position you intend to use. General controls or another module’s profile will not configure that cockpit.
- Show Axis Commands. Select the Axis Commands category or axis filter. Pitch, Roll, Rudder and Thrust are analogue commands; commands such as increase, decrease or centre are digital button commands and will not capture stick movement as an axis.
- Choose the correct device cell. Click where the command row meets the column headed with the joystick or throttle’s name. Selecting only the command label, the keyboard column or another controller’s column is not enough.
- Clear an unwanted existing assignment. Select the relevant cell and use Clear. Do not erase the whole category unless you intend to rebuild every assignment in that profile.
- Add the new axis. Double-click the empty cell or select Add, then move the intended control through a substantial part of its travel. Keep other mini-sticks, rotaries and sliders still so a noisy input is not captured first.
- Verify it in Axis Tune. Select the completed binding and open Axis Tune. Its input indicator should move smoothly through the expected range. Use Invert only if the cockpit control moves backwards.
- Save the change. Leave the Controls screen with OK, enter the cockpit and test the control before adjusting curves or adding more bindings.
Once DCS detects the axes correctly, our full aircraft-by-aircraft HOTAS setup process covers practical assignments, duplicate removal and curve settings.
Why does DCS say “No command available for this device”?
This message means the selected DCS command is not assignable in the device cell you chose.
- You may be in the keyboard, mouse or another controller’s column instead of the joystick column.
- The selected row may be a digital command rather than an analogue Axis Commands entry.
- The command may not be available for that aircraft variant or crew station.
- The cell may be deliberately unavailable for that device type.
- DCS may be displaying a different physical or virtual version of the controller from the one you moved.
What is a device cell in DCS?
A device cell is the box where a command row intersects a controller column in the Controls screen. For example, to bind roll, select the Roll row and then the box directly beneath the column carrying your joystick’s detected name.
A mistake we see constantly is selecting the action name on the left without selecting its box under the required controller. DCS needs both pieces of information: what the input controls and which device supplies it.
Why is the Add button greyed out?
Add remains greyed out when DCS does not have an eligible command-and-device cell selected.
- Open Axis Commands rather than a button-only category.
- Select the cell itself, not just the command name.
- Use the physical controller’s column, not the keyboard column.
- Clear any search filter that may be hiding the intended axis command.
- If the controller has no column, resolve its Windows detection problem first.
If the cell already contains an assignment, select and clear that specific entry before adding its replacement. Some cells cannot be assigned by design, so changing to the correct aircraft, seat or command row is preferable to repeatedly pressing Add.
What does Axis Tune do?
Axis Tune adjusts an existing binding; it does not assign movement to a command or transfer an axis to another device.
Use it to inspect the live input and adjust dead zone, curvature, saturation, direction and slider behaviour where appropriate. If its indicator is frozen, jumps wildly or shows the wrong physical control, return to the assignment or Windows test rather than trying to repair the problem with a large dead zone.
A small dead zone can settle minor centre noise. It should not be used to conceal a failing sensor, poor calibration or a second controller constantly feeding the same command.
Why does DCS detect the axis but control the wrong thing?
DCS usually operates the wrong control because another axis moved during capture or automatic defaults assigned several devices to the same command.
Inspect the complete Pitch, Roll, Rudder and Thrust rows across every controller column. A throttle mini-stick, rudder pedal, gamepad or unused rotary may be assigned alongside the main joystick, causing constant input or controls that fight each other. Clear only the unwanted cells.
If the correct physical axis appears in Axis Tune but moves backwards in the cockpit, enable Invert for that binding. If the range is incomplete, check Windows calibration and the controller’s operating mode before changing saturation.
Do joystick bindings apply to every DCS aircraft?
No. DCS stores 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. Multicrew aircraft need particular care because pilot, co-pilot and operator positions can have independent profiles; our helicopter example shows how cyclic, collective and anti-torque assignments change with the selected seat.
Separate USB sticks and throttles also receive separate columns. Switching a device between physical, virtual or combined modes can make DCS treat it as different hardware, leaving the earlier bindings attached to an identity that is no longer active.
Where is the DCS Saved Games folder for control profiles?
DCS normally stores user control profiles under C:\Users\<Windows user>\Saved Games\DCS\Config\Input, not inside the main simulator installation.
The DCS folder name can differ between installations, especially where an older branch name or a custom Saved Games location remains in use. Inside Config\Input, profiles are divided by aircraft and controller, with saved differences commonly represented by .diff.lua files.
Why do axis changes disappear after restarting DCS?
Bindings that survive only for one session usually indicate a write-permission, synchronisation or controller-identity problem.
- Leave the Controls screen using OK rather than cancelling it.
- Confirm that the relevant Saved Games folder is writable and not blocked by protected-folder security.
- Check for cloud synchronisation conflicts or restored copies overwriting newer profiles.
- Avoid changing virtual-controller modes between sessions unless you intend to create a separate device profile.
- Back up the relevant aircraft folder before resetting anything.
If one aircraft’s controls remain damaged, close DCS, back up and rename only that aircraft’s folder beneath Config\Input, then restart DCS so it can create clean defaults. Do not delete the entire Input folder unless you are prepared to rebuild every aircraft’s controls. Repairing the simulator installation normally leaves Saved Games profiles untouched.
Are DCS User Files and the Saved Games folder the same thing?
No. DCS User Files downloads are shared content, while Saved Games is the local Windows location where your settings, bindings and certain user-installed content are stored.
A downloaded control profile is not necessarily universal. Load it for the matching aircraft and controller column, then inspect every axis before flying; different hardware names, device identities and available switches can prevent an imported profile from matching its author’s setup.
Can you play DCS without a joystick or with a controller?
Yes. DCS World can be flown with keyboard controls or a gamepad, although analogue pitch, roll, rudder and throttle inputs provide much finer control than digital key presses.
A gamepad axis is assigned through the same aircraft-specific Axis Commands screen and can suffer the same duplicate defaults as a flight stick. Our gamepad setup guide explains the axis mapping and duplicate-binding checks.
Keyboard commands belong in the normal command list, not Axis Commands. A joystick or HOTAS is therefore not mandatory, but it becomes increasingly useful for formation flying, helicopters, aerial refuelling and aircraft that demand frequent simultaneous control inputs.