Learn the essential DCS A-10C HOTAS controls, what each hat does, which binds to prioritise and how to fix common mapping problems.
The essential DCS A-10C HOTAS controls are pitch/roll, throttle, rudder, trim, a two-stage trigger, weapon release, TMS, DMS, Coolie Hat, China Hat, Boat Switch, sensor slew with press, CMS, speedbrake, nosewheel steering/autopilot disconnect and Master Mode. Bind these first; together they cover flight, sensor control, targeting, weapons and defence.
Which A-10C controls should I bind first?
Prioritise the controls used while manoeuvring, attacking or reacting to a threat; infrequent cockpit switches can remain clickable or on the keyboard.
| Control | Main purpose in the A-10C |
|---|---|
| Pitch, roll and throttle axes | Primary flight control. Map separate left and right throttles if your hardware supports them; otherwise use one combined throttle axis. |
| Rudder and wheel brakes | Ground handling, crosswind control and coordinated flight. These are not HOTAS functions in the strict aircraft sense, but they need accessible controller assignments. |
| Trim hat | Nose and wing trim. The A-10C requires regular trimming as speed, stores and fuel balance change. |
| Speedbrake switch | Extends, retracts and holds the speedbrakes for formation work, descents and attack spacing. |
| NWS button | Toggles nosewheel steering on the ground and disengages the autopilot in flight. It also supports manual laser operation when the aircraft and targeting systems are configured appropriately. |
| Trigger, first and second detents | The first stage commands PAC-1 gun stabilisation; the second fires the gun and commands the next PAC stage. Both detents need separate bindings. |
| Weapon release | Releases consent-controlled stores such as bombs, missiles and rockets. In many delivery modes it must be held until the release conditions are met. |
| Master Mode Control Button | Changes the aircraft's master mode without reaching into the cockpit. |
| Coolie Hat | Selects the Sensor of Interest, or SOI, and manages multifunction-display pages and swaps. Its exact action depends on direction and whether the press is short or long. |
| TMS | Commands sensor tracks and target designations, and manages the Sensor Point of Interest, or SPI. Functions change with the selected SOI. |
| DMS | Controls sensor zoom, display range and other context-dependent selections such as steerpoints or weapon profiles. |
| China Hat | Slaves sensors and changes sensor field of view according to direction and press length. China Hat Forward Long, which slaves sensors to the SPI, is one of the key A-10C commands. |
| Boat Switch | Changes targeting-pod polarity and related sensor modes, including white-hot, black-hot and television presentation where available. |
| Sensor slew and slew press | Moves cursors and sensor lines of sight. Bind both horizontal and vertical axes plus the push function if your controller provides one. |
| CMS | Operates countermeasure programmes and related defensive functions. Every direction should be reachable without releasing the stick. |
| Microphone switch | Controls radio selection and communications. It becomes especially useful with realistic radios or multiplayer voice communications. |
Our practical DCS controller-mapping guide covers axis assignment, modifiers and the other universal setup work without repeating the A-10C-specific layout here.
How do the TMS, DMS and HOTAS hats work together?
The A-10C HOTAS is context-sensitive: the same direction can perform a different action according to the SOI, sensor state and length of the press.
- Select the SOI with the Coolie Hat. This tells the aircraft whether your commands should affect the HUD, an MFCD sensor page or, in the A-10C II, the helmet-mounted display.
- Move the cursor with sensor slew. Slew the targeting pod, Maverick seeker, TAD cursor or another selected sensor.
- Command the track with TMS. TMS establishes, changes or rejects tracks and designations according to the active sensor.
- Slave other sensors with the China Hat. The most useful example is holding China Hat Forward to bring the appropriate sensors onto the SPI.
- Adjust the presentation with DMS and the Boat Switch. Use them for zoom, range, polarity and other sensor-specific options.
This order—SOI, slew, TMS, slave—explains most A-10C targeting workflows. For the surrounding procedures, including take-off, navigation and weapons employment, see our A-10C flying and combat overview.
How should the controls be mapped in DCS World?
Map the aircraft deliberately rather than assuming DCS's automatic assignments are correct.
- Select the correct aircraft profile. The original A-10C and A-10C II have separate control sets, so changes made under one do not necessarily populate the other.
- Clear unwanted axis assignments. DCS can automatically place pitch, roll, rudder or throttle on several connected devices, causing drifting controls or erratic throttle movement.
- Assign and test the flight axes. Add only enough dead zone to suppress actual noise. Excessive curves or saturation can make formation flying and air-to-air refuelling harder.
- Map every direction of each HOTAS hat. DCS normally distinguishes a tap from a held command through press duration, so both actions use the same physical direction.
- Test both trigger detents separately. Confirm the first stage registers before the second stage; mapping only gun fire omits the PAC-1 command.
- Tune sensor slew last. Use a small dead zone if the cursor creeps, then reduce excessive sensitivity while retaining enough authority to move across a display promptly.
A Thrustmaster Warthog closely matches the real control layout, but its automatic bindings still need checking for duplicated axes and missing functions. We cover those device-specific traps in our Thrustmaster Warthog configuration advice.
What can stay on the keyboard if buttons are limited?
Keep time-critical combat functions on the controller and move infrequent configuration controls elsewhere.
- Keep trim, speedbrake, NWS, both trigger stages, weapon release, CMS, slew, Coolie Hat, TMS and China Hat directly accessible.
- Place DMS, Boat Switch, Master Mode and microphone functions on a controller modifier layer if necessary.
- Leave canopy, landing gear, flaps, master arm, laser arm and cockpit lighting clickable or on convenient keyboard keys.
- Do not place the trigger and weapon release on the same button or behind an easily confused modifier.
A spare joystick hat can serve as either cockpit view control or an A-10C HOTAS hat, but not both simultaneously without a modifier. If buttons are scarce, our DCS keyboard and mouse reference identifies practical fallback inputs.
Why do A-10C HOTAS controls sometimes appear not to work?
Most apparent HOTAS failures come from the wrong control profile, an unselected SOI or a short command being used where a held command is required.
- The sensor will not slew: confirm the required display is SOI, check for duplicate slew assignments and inspect the axis dead zone. A sensor may also refuse commands until it has completed its normal start-up or hand-off process.
- A hat moves the camera: remove the conflicting view assignment, use head tracking, or create a modifier layer for view movement.
- China Hat or TMS gives the wrong result: check the SOI and distinguish a tap from a deliberate hold. The command is interpreted from the sensor context, not from the hat alone.
- The gun fires without expected stabilisation: verify that the first trigger detent registers before the second and that the aircraft's required stability systems are configured.
- A bomb or missile does not release: hold weapon release long enough for consent, then check master arm, the selected profile and valid launch or release conditions. Rebinding the button will not fix an aircraft-state problem.
- Controls work in one A-10C but not the other: repeat or transfer the assignments under the correct A-10C or A-10C II profile and check the added HMCS-related commands in the latter.
The original A-10C and A-10C II share the same core HOTAS logic. The A-10C II adds helmet-mounted-display interactions and associated context, but it does not remove the need to master SOI selection, slew, TMS designation and sensor slaving.