WARDOGS HOTAS Support and Binding Problems

WARDOGS has native HOTAS controls in the September 2026 test build. Enable HOTAS in the Gamepad settings, assign the flight axes, then check the aircraft's response before carrying passengers. Player reports show working setups alongside device-specific detection and binding failures; there is no verified all-device compatibility list. ^{[01] [02]}

Establish which device Windows is seeing

Before changing game settings, press Windows + R, enter joy.cpl, select the connected controller and open Properties. Move each axis and press several buttons. Thrustmaster documents this test for its flight hardware; other manufacturers also provide device test utilities. A device that produces no input here needs its connection or manufacturer setup checked before you diagnose WARDOGS. ^[03]

There is one useful exception to a “missing device”: TFRP pedals connected through a compatible Thrustmaster throttle's RJ12 port appear as axes of that throttle, rather than as a separate TFRP entry. Test those pedal axes under the USB-connected device. This naming behavior is documented by Thrustmaster and is not evidence of a WARDOGS detection bug. ^[03]

Enable HOTAS and bind a usable flight layout

Save screenshots of the bindings you already use. The following setup combines the September HOTAS toggle report with players' hands-on binding instructions; it does not depend on downloading a preset or remapping utility. ^{[01] [04]}

1. Open Settings → Gamepad and enable HOTAS. Use the HOTAS binding entries available in your build.
2. Select a flight action, then move only the intended axis or press its button. The August dual-stick setup report describes assigning controls by selecting the binding and supplying the input.
3. Cover pitch, roll, yaw and collective. Choose their physical positions to suit your stick, throttle and pedals; the important check is whether each moves the aircraft in the intended direction.
4. Assign the other actions you need to fly and deliver supplies, including engine control, flares and dropping cargo. Check that your chosen bindings actually register.
5. Test a short takeoff, controlled movement and landing in the Firing Range when it is available. Return to the bindings after restarting the game to check that the layout persisted.

Keep an on-foot escape route: check movement, firing and the parachute binding after changing vehicle controls. Grundy's Beta 02 controls discussion reports that some custom key assignments can clear an existing action in another context. Use separate keys where that conflict occurs, then test both actions. ^[05]

Match the symptom to the next check

What you observe	What to do next
Mouse or keyboard flight controls stopped after enabling HOTAS	Turn HOTAS off when returning to mouse-and-keyboard flight. The reported mode restriction is a different problem from a disconnected stick.
TFRP pedals are absent from the device list	If connected through RJ12, test the parent throttle's pedal axes in Windows.
A physical axis works in Windows but never binds in WARDOGS	Record the exact device and axis. Retest the HOTAS binding once; sensitivity cannot repair an input the game never receives.
The binding is present, but collective does nothing in flight	Check the exact action in-game. A September HOSAS user reported this even with self-centering collective enabled; that toggle is not an established universal repair.
Changing a key erased another action	Reassign the affected action to a separate key and check both infantry and vehicle controls.

The mode and conflicting-key checks come from the Beta 02 controls discussion. The missing-axis reports include Virpil Alphas and an X56 analogue-stick problem; they should not be read as a certification or rejection of either product line. ^{[05] [02]}

Mixed keyboard input and difficult handling

September players specifically reported that keyboard collective inputs stopped working while HOTAS was enabled. Flying with a stick and throttle, returning to keyboard after exiting, and combining keyboard plus stick during flight are three different tests. For the mixed-input problem, use a fully bound HOTAS layout or switch back to keyboard and mouse; the sources do not establish a native setting that enables both simultaneously. ^{[01] [06]}

Once inputs register correctly, adjust one handling setting at a time. Community pilots suggest keeping flight assists enabled while learning, then comparing the response with and without individual assists. There is no one sensitivity value verified across aircraft and devices. ^[05]

If detection or saved bindings still fail, report the build or test date, device models, Windows test result, exact missing axis and whether the setup worked previously through WARDOGS Steam Support. Include binding screenshots. Keep a copy of your working layout and use the game's controls first; these sources do not establish support for third-party virtual-controller workarounds.