Vaultbreakers’ public Demo currently shows Full Controller Support on Steam, while the unreleased base-game page shows Partial Controller Support. These product labels are not interchangeable and can change before launch. October notes describe expanded controller navigation across onboarding, inventory, storage, crafting, social, and party screens, plus LB/RB navigation and auto-targeting work. Test the exact client and build before publishing a fixed button map.
Establish one clean input baseline
Connect one controller before launching the game. Confirm that Windows and Steam recognize it, then start Vaultbreakers with the default per-game Steam Input setting. Disconnect unused pads and close unnecessary virtual-controller or remapping software. This prevents two devices from sending the same action.
In the title screen or Haven, test movement, camera, confirm, back, menu navigation, interaction, attacks, abilities, healing, and target behavior. Do not remap immediately. First identify what the native baseline does and which layer actually needs change.
Use Steam Input as a controlled variable
If the controller works natively and prompts are correct, keep the baseline. If it is not recognized or remapping is insufficient, test the opposite per-game Steam Input state through Steam’s properties. Relaunch after the change and test the same action. Do not combine that change with new firmware, another USB port, and a community layout at once.
Steam Input can translate devices and provide accessibility customization, but it can also create doubled input or mismatched icons when both native and emulated devices are active. Record controller model, wired or wireless connection, Steam Input state, layout name, and client build with every result.
Verify menus beyond combat
Full Controller Support should cover more than moving and attacking. Navigate onboarding, hero and equipment screens, inventory, storage, crafting, quests, Codex, social, party, settings, and any confirmation dialog available in the Demo. October notes specifically call out improvements across several of these surfaces, so a historical report may already be fixed.
Check focus visibility and whether every action can be completed without reaching for a mouse. Use LB/RB or the prompts shown by the current client to move between tabs. If focus disappears, record the screen, previous control, expected destination, and whether backing out restores it.
Tune camera and auto-targeting together
Adjust horizontal and vertical sensitivity until a single stick movement follows an enemy without repeated overshoot. Test in an ordinary encounter before a Vault. If the client exposes auto-targeting or target-selection behavior, compare it with the same enemy group and camera settings.
Auto-targeting can help an attack connect, but it can also choose a nearby enemy when the player intends to move or hit a priority target. Observe when it activates, whether the right stick or movement changes the selection, and how it behaves around a pack. Keep ranged threats visible even when the system focuses on a close target.
Remap by action role
Defensive movement, camera control, main attacks, hero abilities, Ability Items, healing, interaction, and target control should remain reachable during pressure. A visually tidy layout can still be poor if using a heal removes camera control or if a critical dodge conflicts with another common action.
Change one binding, then test Haven menus and combat. Check hold versus press behavior and any displayed conflict. Share guides using current action names rather than assuming Xbox, PlayStation, Nintendo-style, or generic labels are identical.
Fix wrong prompts and doubled actions
For wrong icons, confirm the physical device, current prompt option if present, and Steam Input state. Prompt family can be incorrect while actions remain functional, so keep icon and behavior reports separate. For doubled movement or menu steps, disconnect other devices and disable duplicate virtual pads or remappers.
If keyboard prompts appear whenever the mouse moves, remove accidental mouse input and retest. If the device vanishes after sleep or reconnect, return to Haven or the title screen, verify Steam still sees it, and relaunch before changing the layout.
Separate latency from frame-time trouble
Input can feel slow when the game is hitching, loading, or missing a stable frame target. Use the same scene and action, lower graphics settings conservatively, and compare a stable frame-rate state. Wired USB can remove wireless interference and battery variables, but a good wireless link can still perform correctly.
Do not install unverified latency tools or injectors. Record whether the problem appears in menus, Haven, ordinary combat, and only during particular effects. The Performance and Crashes guide provides the broader isolation order.
Use accessibility options without invalidating the test
Vibration, sensitivity, hold or toggle behavior, subtitle and audio balance, prompt scale, and remapping can change how information is perceived. Choose the settings that make attack and interface cues readable. Keep them constant when comparing timing.
If an accessibility tool or alternate input is required, document it as part of the setup rather than removing it for a theoretical clean test. Change only the layer under investigation and preserve a known working configuration.
Report a controller issue precisely
Include Demo or base AppID, build, controller model, connection, firmware if relevant, Windows version, Steam Input state, layout, exact screen or encounter, reproduction steps, expected result, actual result, and whether keyboard/mouse or another pad works. Remove account names from screenshots.
Controller support on Windows does not establish a PlayStation or Xbox release, crossplay, or Steam Deck verification. Those remain separate platform questions.