The current answer
WARDOGS is a PC-first game with incomplete controller coverage during its pre-release tests. Partial support is planned; a controller working for movement does not guarantee that every menu or helicopter action is mapped. Steam Input can translate gamepad inputs into keyboard, mouse or gamepad commands, but cannot add missing game features.
Check four control areas separately
Treat controller support as a set of tasks rather than a single yes/no label. Getting past the title screen, aiming a rifle and using a vehicle may exercise different input paths. A layout that is comfortable for infantry can still be incomplete for buying gear or flying.
Before entering a full match, keep a mouse and keyboard connected and verify the actions in this checklist. This is a setup checklist, not a claim that a particular controller passed every task.
| Area | Actions to check | Why it matters |
|---|---|---|
| Infantry | Move, look, aim, fire, reload, crouch and interact | A missing interaction can stop an otherwise playable session |
| Menus and vendor | Open, select, buy, scroll, back out | Mouse-style menus may need a separate mapping |
| Team communication | Map, squad/proximity voice and push-to-talk | A working weapon layout can still leave you unable to coordinate |
| Vehicles | Enter/exit, seats, camera, flight axes and countermeasures | Infantry mappings do not prove helicopter usability |
Start with one input path
- Connect the controller before launching Steam and confirm that Steam detects its buttons and sticks in Controller settings. Use a wired connection temporarily if the device disconnects during diagnosis.
- Select the correct library entry: WARDOGS Playtest for an active test, or the main WARDOGS entry for the purchased game. Controller overrides and layouts can belong to different entries.
- Open the game’s Properties → Controller and note the current Steam Input override. Begin with the default setting and an uncomplicated layout, so you have a known baseline.
- Launch the game and test movement, aiming and one menu interaction. If an action is absent, compare the current in-game binding with the command your Steam layout sends.
- Try a per-game Steam Input layout only where it addresses a specific missing command. Save your original layout before changing it. Test one change, then return to the game.
- Test a vehicle separately. Keep a reachable exit/interact command and a way to return to the infantry layout before transporting anyone.
What Steam Input can and cannot fix
A keyboard/mouse layout can map a stick to movement and a trigger to a mouse button. The screen may continue to show keyboard prompts, because the game is receiving keyboard input. A different prompt alone does not prove the controller is disconnected.
Steam Input does not create native aim assist, complete a missing helicopter binding system or turn a PC game into a console release. Mixed mouse and gamepad output can also make some games switch prompts or behave inconsistently. If that happens, simplify the layout instead of stacking additional input translators.
Use separate action sets or layers only after the basic configuration works. An aircraft layer should not strand you without infantry controls when you leave the seat.
Controller not working: isolate the symptom
Do not treat a published “best sensitivity” number as calibration for your device. Start from a stable default, adjust one axis at a time and check whether you can stop the camera precisely. Higher sensitivity does not repair an unbound action.
| Symptom | First check | Next decision |
|---|---|---|
| No input in Steam | Connection, device detection and Steam input test | Resolve the device issue before changing the game |
| Works in Steam, not in WARDOGS | Correct library entry and per-game override | Test the default path, then one Steam Input layout |
| Double inputs or moving cursor | Other connected pads, sticks and overlapping mappings | Disconnect unused devices and use one mapping path |
| Menus work, flight does not | Current vehicle bindings and active action set | Use mouse/keyboard flight while mapping limitations remain |
| A stick drifts when released | Steam device test and in-game deadzone options | Increase only the affected deadzone enough to remove drift |
| Prompts flicker between keys and pad | Mixed mouse and gamepad outputs | Try a consistent output type and retest |
Continue with the relevant device guide
- Set up a joystick, throttle or pedals Flight devices need axis and direction checks.
- Learn the flight controls Build a hover and landing routine before taking passengers.
- Steam Deck compatibility Controller support and SteamOS compatibility are separate questions.
- Troubleshoot a launch or access error Use this when the game fails before input can be tested.
Direct answers
Frequently asked questions
Does WARDOGS have full controller support?
Full controller coverage is not established for the pre-release builds. Test menus, infantry and vehicles separately and keep mouse/keyboard access available.
Can I use an Xbox or PlayStation controller through Steam Input?
Steam Input supports common Xbox and PlayStation devices. Device recognition by Steam does not guarantee complete WARDOGS controls; verify your specific model and layout.
Will Steam Input add aim assist?
No. Mapping an input does not create an aim-assist feature. Do not assume a keyboard/mouse layout receives native gamepad behavior.
Why does my Playtest layout not work in the main game?
The Playtest and main game are different library entries. Check the controller override and saved layout for the entry you actually launched.