How do I set up a T.Flight HOTAS One in DCS World?

Set the T.Flight HOTAS One to PC mode before connecting it, confirm Windows sees every axis, then bind it separately for each DCS World aircraft under Options > Controls. Clear DCS's automatic duplicate axis assignments first, assign pitch, roll, throttle and one rudder input, tune small deadzones, then save that aircraft profile.

Prepare the HOTAS One before opening DCS World

The HOTAS One must be operating as a Windows controller before DCS World can configure it correctly. Set its selector to PC mode before connecting the USB cable, preferably to a direct USB port while troubleshooting.

Press the Windows and R keys, enter joy.cpl, select the controller and open its properties. Check the stick, throttle, twist grip, throttle rocker, hat and every button. The twist and rocker may appear as separate rudder-capable axes, so note which indicator each one moves.

DCS does not require third-party mapping software for this controller. If Windows misses an axis or button, resolve that first using our Thrustmaster detection and calibration checks.

How do I create the DCS HOTAS One profile?

Create the profile inside the exact aircraft and crew position you intend to fly, because DCS bindings are aircraft-specific.

1. Connect the controller before launching DCS. This avoids device-detection and column-assignment problems.
2. Open Options > Controls. Select the aircraft from the list. If DCS offers separate simulation and simplified control sets, use the simulation set; multi-seat modules may also have separate profiles for each seat.
3. Remove automatic axis assignments. Open the Axis Commands category and clear unwanted entries from the HOTAS One column. Check gamepad, pedal and other joystick columns too. A mistake we see constantly is DCS assigning pitch, roll or throttle to several devices at once, causing jumps or controls that fight each other. Our complete DCS controller setup workflow explains how to clean up a multi-device installation.
4. Assign the main axes. Double-click the required cell in the HOTAS One column, move only the intended control through a clear range, then accept the detected input. Centre every other control while doing this.

1. Tune each axis. Open Axis Tune for the selected command. Use Invert if the cockpit control moves backwards. Leave saturation at 100 unless the hardware cannot reach an endpoint.
2. Bind essential buttons. Assign the trigger, weapon release, trim or view hat, wheel brakes and the most-used aircraft systems. The command names differ between modules.
3. Test in a simple mission. Watch the cockpit stick, pedals and throttle while moving the hardware. Where supported, the controls indicator also makes small unwanted inputs easy to spot.
4. Save a backup. DCS stores changes automatically, but Save Profile As creates a device-specific .diff.lua backup. Select a cell in the HOTAS One column before saving so that you export the correct device.

What axis tuning should I use?

Use the smallest deadzone that removes drift, and add curvature only when the short stick travel makes fine control difficult.

• Pitch and roll: Start with no deadzone if the stick centres cleanly. A deadzone around 1–3 and positive curvature around 15–20 are sensible fixed-wing starting points, not mandatory values.
• Rudder: Twist grips and rockers often benefit from a slightly larger deadzone, commonly around 3–5. Add curvature if taxiing or aiming feels too abrupt near the centre.
• Throttle: Use zero deadzone and a linear response first. Select Invert if idle and full power are reversed. The Slider option is mainly useful when shaping a one-ended axis; it is not required for a linear throttle.

Do not reduce saturation merely to make the aircraft feel less sensitive. That removes control authority at the ends of travel. Tune helicopters and warbirds separately rather than copying a fast-jet curve into every module.

Which HOTAS One buttons should I bind first?

Prioritise controls needed during take-off, combat and landing; infrequent cockpit switches can remain on the keyboard or clickable cockpit.

• Gun trigger and weapon release on separate buttons
• Trim on the hat when using head or eye tracking
• View directions on the hat when no tracking system is fitted
• Target lock or designate, weapon change and sensor selection
• Countermeasures and speed brake
• Wheel brake and nose-wheel steering
• Radio or push-to-talk controls used by the aircraft

The HOTAS One has one hat and fewer controls than many DCS aircraft expect. Add a held button through DCS's Modifiers panel to create a second layer; for example, the hat can control trim normally and views while the modifier is held. Avoid assigning an ordinary cockpit action to the modifier button itself, or both commands may fire together.

Why are the throttle or rudder not working?

Most HOTAS One input failures come from an incorrect aircraft profile, duplicate assignments or a control that has been detected backwards.

• The throttle moves the wrong way: Enable Invert in Axis Tune rather than recalibrating the entire controller.
• The cockpit throttle remains at OFF: Many full-fidelity jets require separate idle-detent or cutoff commands during engine start. Moving the physical lever alone cannot cross a simulated cutoff gate.
• The aircraft rolls or yaws by itself: Inspect every controller column for duplicate axes, then add only enough deadzone to stop genuine hardware drift.
• Twist and rocker interfere: Bind only one to Rudder. If Windows presents them separately, leave the unused axis clear until the basic profile works.
• Buttons work but axes do not: Recheck PC mode, reconnect before starting DCS, and verify the axes in joy.cpl.
• There is no differential braking: The HOTAS One does not provide independent left and right toe-brake pedals. Use the aircraft's button-operated wheel brake command unless separate pedals are connected.

Can one HOTAS One profile work with every DCS aircraft?

No single profile covers every DCS World aircraft because command names, systems, seats and available axes differ between modules. Build a clean base layout, then reproduce its logic—rather than blindly importing the same file—for each aircraft.

A profile made for the similar T.Flight HOTAS X may also use different device identification or button numbering. Imported files therefore need every axis and button checked before flight.

DCS normally keeps live bindings beneath the DCS input folder in Saved Games, while exported files provide a portable backup. Our guide to backing up and restoring DCS device profiles safely covers the per-aircraft and per-controller requirements.