The current answer
WARDOGS pre-release builds include HOTAS settings, but support and binding behavior vary by device and build. Start with a recognized device, map pitch, roll, yaw and collective one at a time, and test direction on the ground. There is no universal profile or sensitivity value that this guide can certify for every stick.
Separate device support from a successful flight
A stick appearing in Windows is the first checkpoint. It still needs to be detected by the game, bind to the intended axis and control the aircraft predictably. A usable pitch axis alone does not prove that the throttle, pedals, hat switch or free-look controls work.
Older development replies placed HOTAS further down the roadmap; later pre-release builds and flight setups include a HOTAS menu. Neither the old “not planned for Early Access” statement nor another player’s working hardware should be treated as a complete current compatibility list.
Start with equipment you already own. A purchase recommendation would require testing the exact device, firmware and current game build. This page is a configuration workflow, not a hardware benchmark.
Map the four flight controls deliberately
Collective changes rotor lift demand; it is not the same operation as tilting the aircraft forward. Label controls by their action first, then choose the hardware input. Do not bind two opposite ends of a throttle to unrelated flight jobs merely because the axis is available.
| Flight action | Possible physical input | Ground check |
|---|---|---|
| Pitch | Stick forward/back | Forward input produces the intended nose-down response |
| Roll | Stick left/right | The aircraft banks toward the intended side |
| Yaw | Pedals or stick twist | Heading turns without unexpectedly binding roll |
| Collective | Throttle lever or a pair of buttons | Raise/lower moves in the intended direction through its range |
| Free look / camera | An available hat or reachable keyboard control | Looking around does not steal the primary flight axes |
| Interact / exit / map / voice | Reachable buttons or keyboard | You can stop flying and communicate without losing control |
A repeatable HOTAS setup sequence
- With the game closed, connect the stick, throttle and pedals you intend to use. Use the manufacturer’s normal device test to confirm center, travel and buttons. Leave the aircraft controls untouched while checking neutral readings.
- Start the current WARDOGS build and open its controls/HOTAS settings. Note the selected device and retain a copy or screenshot of the original bindings for your own rollback.
- Bind one flight action at a time. Move only the intended axis while the game is listening; keep pedals and the throttle still so a different device does not capture the binding.
- Check each direction before takeoff. If an axis is reversed, change the matching inversion option only. Do not invert several axes together and then try to diagnose the result in the air.
- Check neutral response, then adjust a small deadzone only if the released control produces movement. Increasing every deadzone can make fine corrections harder.
- Make a short hover and landing test when a playable range or suitable test session is available. Validate the camera, map, voice and exit controls separately before carrying passengers.
Resolve conflicts before changing sensitivity
An input can reach the game directly, through Steam Input, or through a manufacturer’s own mapping. More than one path may produce duplicate commands or expose a virtual gamepad instead of the original stick. Record the existing per-game Steam override before changing it, and compare one input path at a time.
A hardware input test that responds promptly while the aircraft responds slowly points to a different problem from an axis the game cannot detect. Check the assigned flight action, assist settings and frame-rate consistency before treating every delay as joystick hardware failure.
| Problem | Useful check | Avoid |
|---|---|---|
| Wrong axis binds | Move one device/axis while binding | Wiggling every control at once |
| Drift or constant yaw | Neutral readings and the specific deadzone | Copying a large global deadzone |
| Mouse flight stops responding | Current HOTAS/mouse control modes | Assuming both modes can always operate together |
| Aircraft fights a turn | Axis direction, duplicate assignments, flight assists | Changing all assist switches mid-flight |
| Device is ignored | Windows recognition and game device list | Installing unknown remappers or anti-cheat workarounds |
| Cannot use a menu from the cockpit | Reachable keyboard fallback and supported bindings | Taking passengers before the exit/menu test |
Save the layout, then learn the aircraft
Keep a brief configuration record: build date, aircraft, device model, input mode and the four axis assignments. If an update changes the result, this is enough to reproduce the problem without posting private account data or a full system dump.
The next goal is a controlled takeoff, short hover and return to the same clear landing area. Weapon aiming and combat maneuvers come after you can reliably stop and land. A stable basic layout is more useful than a long list of untested advanced bindings.
- Practice takeoff, hover and landing Follow the flight exercises with your chosen input.
- Using a gamepad instead? Compare Steam Input and per-game control coverage.
- Compare helicopter roles and versioned prices Choose an aircraft you can afford to replace.
- Launch and input troubleshooting Distinguish a client error from a binding problem.
Direct answers
Frequently asked questions
Does WARDOGS support every HOTAS device?
No complete universal compatibility list is established here. Device recognition, axis mapping, camera controls and actual flight must be checked separately.
Should I copy someone else’s sensitivity curve?
Use it only as an experiment for the same device and build. First confirm correct axes and neutral response; a curve cannot repair an incorrect binding.
Do I need pedals?
Yaw needs a usable input, but this guide does not establish pedals as mandatory. Stick twist or another supported mapping may fill that role.
Can I use HOTAS and mouse flight together?
Do not assume both input modes remain active together. Check the current mode switches and test the handoff on the ground before relying on it in flight.