Official media referenceDirect answer
Official footage shows a controller-focused interface, but the current Steam feature panel does not confirm a Full Controller Support badge; remapping and device-specific glyph behavior still need current-build checks.
How to use this page
For a tactics game, support quality depends on more than movement. Cursor speed, tooltips, camera control, target cycling and text entry all matter.
What is verified
- Test Xbox, PlayStation and Steam Input separately.
- Verify whether prompts switch automatically when input changes.
- Check tactical combat and the 3D base, not only menus.
- Document unmappable actions instead of assuming every key can be rebound.
Evidence scope
Verified against sources on August 14, 2026Official footage demonstrates a controller-oriented interface and the developer says controls were adapted for Steam Deck. The cited Steam feature panel did not yet establish a Full Controller Support badge, and exact remapping, glyph and device behavior remains a current-build test question.
What is confirmed—and what is not
A June 2026 official video shows controller UI and discusses play beyond desktop PC. A separate developer reply says Steam Deck controls are adapted. This supports real controller work, but it does not by itself prove every screen is usable without a keyboard, every action is remappable, or Xbox and PlayStation pads show the correct glyphs in the launch build.
- Official footage: controller-oriented interface is visible.
- Developer statement: Steam Deck controls adapted.
- Still needs testing: full-menu coverage, remapping and device glyphs.
How to test support properly
Test more than tactical movement. Verify the title screen, save management, squad deployment, target cycling, ability tooltips, camera rotation and zoom, the 3D ship base, recruitment and any text entry. Switch between mouse and controller to see whether prompts update, then repeat with Steam Input enabled and disabled so native behavior is not confused with a community layout.
- Test combat and the base separately.
- Verify every menu can back out safely.
- Check prompt switching after changing input.
- Record controller model and Steam Input state.
Troubleshooting without overclaiming
If inputs are duplicated or prompts are wrong, first close competing remapping software and test one input layer at a time. In Steam, compare the developer layout with Steam Input rather than stacking both with another mapper. If one action cannot be rebound, document that exact action and screen; do not assume the whole game lacks support or that every key can be remapped.
- Use one mapper at a time.
- Restart the game after changing Steam Input mode.
- Capture the screen, controller model and build for reproducible reports.
Controller verification checklist
- Identify controller model and connection type.
- Test once with native input and once with Steam Input.
- Check combat, deployment, base, menus, saves and tooltips.
- Verify glyph switching and target cycling.
- Record every unmappable or keyboard-only action with the build number.
Frequently asked questions
Does Warhounds have Full Controller Support?
Official footage shows substantial controller UI, but the cited Steam feature panel did not confirm the Full Controller Support badge. Treat full coverage as unverified until the live store or a complete current-build test confirms it.
Will a PlayStation controller work?
It may work through Steam Input, but native PlayStation glyphs and device-specific behavior are not confirmed by the evidence used here. Test the exact controller and record whether Steam Input is active.
Can every action be remapped?
That is not yet verified. Check tactical controls, camera, base navigation and menu actions separately, and report exact unmappable actions rather than a blanket yes or no.
Sources and verification
Official facts are separated from developer estimates and unverified community claims.