If one LB, RB or D-pad press moves the Witcher 3 menu twice, compare the keyboard and a single controller before changing your bindings. An October 11 Steam player reports the problem across several Xbox controllers. That establishes a current symptom, not a confirmed universal Steam Input fix. The reversible comparison below helps identify which input path reproduces it.
Double input is different from a slow dodge
Open a safe settings or inventory menu and press a direction once. Note whether the selection moves two positions, a page switches twice, or prompts flicker between keyboard and controller. Compare a single keyboard press. If both devices double, do not immediately blame the controller hardware.
For one late combat response instead of two menu actions, use dodge delay and frame-generation latency. A second action and a delayed action need different tests.
Try a reversible, per-game comparison
- Record the current game build, controller model, wired/Bluetooth connection and custom layout. Keep a screenshot of the current per-game override.
- Close the game. Leave one controller connected. If an external remapper is running, record it and close it for the comparison; do not delete its profiles.
- For an Xbox controller that the game recognizes directly, open Steam Library → this game → Properties → Controller. Compare the current override with Disable Steam Input for this game only.
- Relaunch and test the same single menu press. Do not change sensitivity, mods and connection type in the same test.
- If input disappears or the test does not help, restore the recorded override/layout and relaunch.
Steam Input can be needed for another controller, accessibility layout or Remote Play. This diagnostic is not an instruction to disable it globally, install a beta driver, or apply an Xbox test to every Steam Deck configuration. A remapper can present a virtual Xbox controller; Valve documents this behavior, but it does not prove your setup has duplicate events.
What each comparison tells you
| Observed result | Interpretation and next step |
|---|---|
| Only the altered input path stops doubling | Keep the working per-game configuration for that setup and record it. This is your comparison result, not proof of a game-wide repair. |
| Controller stops responding | Restore the override. That setup needs an input path the disabled configuration did not provide. |
| Both settings still double | Restore the preferred layout; collect a short menu video and compare another supported connection/controller if available. |
Report a reproducible menu action
Give support the exact menu, button, number of movements, build, Steam client version, controller/connection and remapper state. Include whether keyboard input works and what changed in each test. The October 11 original had no replies when read, so this guide does not claim community agreement or a verified fix. Do not reset Windows controller drivers or erase game saves on this evidence.
Sources and limits
- Reddit: Steam controller UI bug? — Original read October 11, no replies at observation; multiple Xbox controllers and keyboard comparison.
- Valve: Steam Input for players — Input layouts and virtual-controller behavior; not a Witcher-specific repair.
Sources checked October 11, 2026. This is an attributed route or diagnostic checklist, not our firsthand game test. Record your exact platform and build when comparing results.