Wardogs Flight Sim Fly the sim

Trainer / Controls / Fixes

Wardogs HOTAS, joystick or controller not working: fixes

By the Wardogs Flight Sim team. Published , updated

Most Wardogs input problems come down to a handful of settings. Find your symptom below, apply the fix, then test it in the free browser trainer before you take a helicopter out.

Free browser trainer

Read it, then fly it

Twelve drills in all six Wardogs helicopters, with a replay and a debrief after every run. Free, nothing to install.

Start with the hover drillAll 12 drills

These setups date from the Wardogs playtests and early access (August to September 2026). Menus and defaults change with patches, so check the names against your version. Where a creator only showed a value on screen, it is not listed here: watch the linked video for it.

Quick fixes by symptom

SymptomLikely causeFix
HOTAS or joystick does nothing in the helicopterHOTAS input is off, or the axes are not boundSettings → Gamepad → HOTAS → Enable HOTAS, then bind roll, pitch, yaw and collective one axis at a time (AllThingsHow).
Keyboard flight stopped workingHOTAS is enabled with no stick connectedPlug the stick back in or turn Enable HOTAS off. AllThingsHow and the Steam FAQ both report this.
Axes fight each other or input is erraticAuto-detect bound overlapping axesClear the binds and bind each axis manually, moving only that axis (AllThingsHow).
Aircraft slowly rolls or noses over by itselfStick resting slightly off centre on a rate-based cyclicAdd a small deadzone on pitch and roll only (Sim Controls runs 0.02 on a springless stick) and fly in pulses back to centre.
Helicopter feels sluggish, max roll rate too lowAxis sensitivity below 1.0Set pitch, roll and yaw to 1.0 or higher. Sim Controls found lower values also cap the maximum rotation rate.
Collective hits full before the throttle doesCollective sensitivity at 1.0Lower collective sensitivity (Sim Controls uses 0.6) and calibrate against the on-screen collective bar.
Curve or profile lost after a restartStick software did not save the profileThe game has no stick response curve, so curves live in your stick software. VKB’s software does not auto-save profiles (Sim Controls).
No free-look button on the HOTASNo free-look binding for HOTASMap a throttle button to Left Alt with Joystick Gremlin (IceManIsaac).
PlayStation controller bumpers (yaw) do nothingBumpers not registering on DS4/DualSenseRun DS4Windows so the pad presents as an Xbox controller (IceManIsaac).
Firing on a gamepad also raises the collectiveOn some builds fire and collective up share the right triggerUse paddles or the vJoy + UCR virtual-HOTAS workaround on the controller page (Fallout Plays, AbradantMatthew).
Gamepad flight feels laggy through Steam InputMouse emulation latencyPresent the controller as a virtual joystick with vJoy and UCR, and bind it in the HOTAS settings (AbradantMatthew).

Check the hardware outside the game

If the game sees nothing at all, rule the hardware out first. Open the trainer in your browser and go to the controls cog. The trainer reads any stick, throttle, pedals or controller the browser sees as a gamepad, and a HOTAS made of several USB devices is read as one. If you can bind an axis there, the hardware works and the problem is a game setting. If the browser cannot see the device either, look at the USB connection, driver or stick software before changing anything in Wardogs.

Then set it up properly

Test the fix in the browser

Once it works, fly the hover hold and hover taxi drills. They show immediately whether a deadzone or sensitivity change helped: drift and seesawing appear on the debrief chart after each run.

Fly the hover drill All 12 drills

Sources

Practise as you readFree, no install Fly the sim