Seven Deadly Sins Origin controller not working on Steam

Before changing Origin's controls, check whether Steam detects the controller and receives its buttons and sticks. If Steam receives no input, troubleshoot the connection first. If Steam passes the test, compare the game's response and its per-game layout, changing one setting at a time.

Scope: general diagnostic procedures based on platform documentation, not confirmed Origin workarounds. No game-specific fix has been verified for this guide.

Guide and platform sources reviewed: October 11, 2026. Menu names may vary by device or client version.

First gate: does Steam receive the controller's input?

  1. Close the game. Connect and power the controller, then open Steam → Settings → Controller. Look for the detected device name; a Bluetooth “paired” message alone is not an input test.
  2. Open the controller's input test if available, labeled Test Device Inputs or Test Controller Inputs depending on the client. Press each button, move both sticks and triggers, then release them. Note missing inputs and movement while untouched. If that test is absent, check navigation in Steam's Big Picture UI and record that this was a limited check.
  3. Write down the name Steam reports, the connection type, and the test result before launching Origin. Steam UI input passing confirms reception there; it does not prove compatibility with every game or screen.

Valve documents controller detection in Steam Input: Getting Started for Players. Its screenshots include older client menus. Valve also documents the input test in its Steam Deck input section; that device-specific guide does not establish Origin's Steam Deck compatibility.

Branch A: Steam shows no device or receives no buttons

Leave game layouts unchanged while this gate fails. A game-specific mapping change cannot tell you why Steam itself is receiving no button presses.

  1. Check charge and the manufacturer's PC connection instructions. If the controller supports USB data, try a known data-capable cable directly in the computer; a charge-only cable is not a useful test.
  2. Retry the Steam input test using another port or without an optional hub. For intermittent USB failures, see Valve's USB connection troubleshooting. Reconnect removed accessories one at a time afterward.
  3. If wired input works but Bluetooth does not, record that difference and use the controller/OS vendor's pairing guide. Re-pair only when you have another way to control the computer. Test one connection at a time.
  4. Restart Steam and repeat the UI test once. Apply firmware only through the controller manufacturer's official method when appropriate; do not install a new remapper to make the test pass.

Stop/escalate: if the controller also fails outside Origin or on another available computer, contact its manufacturer. If the OS receives input but Steam does not, contact Steam Support. Report both results rather than claiming the game caused the failure.

Branch B: Steam passes, but Origin ignores the controller

Launch Origin from the Steam Library with the controller connected. Keep a mouse/keyboard available. Focus the game window, close any open overlay, and separately test a menu and ordinary gameplay where available. If you cannot get past login, record that limitation instead of reporting gameplay input as failed.

  1. Temporarily disconnect extra controllers and optional input devices. If you already use a third-party remapper, record its profile and quit it for one comparison, then restore it if needed. Do not uninstall its drivers. A translated device name in Steam is a clue about the input path, not proof of a conflict.
  2. With the game closed, open Library → Origin → Properties → Controller. Screenshot the existing per-game Steam Input override and layout name. Menu wording can vary by client.
  3. If you previously forced an override, test Use default settings first. If that fails and the menu offers them, compare Enable Steam Input and Disable Steam Input as separate tests. Fully exit and relaunch the game between tests; do not change a layout or connection during the same test.
  4. Record whether each tested mode receives input in the same menu/gameplay situation. Restore the original override after an unsuccessful comparison. If a mode works, note the device, build, and screen where it worked before retaining it.

Stop/escalate: neither enabled nor disabled is a universal recommendation. If Steam input remains good but the game's response does not change across the applicable tests, restore the baseline and send the comparison to game support. This page has not verified which mode Origin requires for your controller.

Branch C: wrong buttons, double presses, drift, or only one screen failing

  • Buttons work but labels look different: check the action produced, not just the Xbox/PlayStation-style icon. A prompt mismatch alone is not a detection failure. Record both the physical button and action.
  • One press moves two menu entries: repeat a single press in Steam's test. If it is normal there, compare one input path at a time, including an already-running remapper and the per-game layout. Do not stack a new translation tool on top.
  • Wrong action or mouse-like movement: inspect Origin's Steam controller layout for keyboard/mouse bindings. Save or screenshot the current layout before testing a developer-recommended layout, if one is actually offered. Restore the previous layout if it does not help; a community layout is not an official fix.
  • Stick moves while untouched in Steam's test: use the manufacturer's diagnostic/calibration instructions. Do not assume a game dead-zone change repairs hardware.
  • Only one menu or activity fails: record its exact entry path and compare dated official issue notices via Bugs and Errors. Passing elsewhere is useful evidence; stop changing global bindings to repair a single-screen symptom.

What should a controller support report contain?

For Steam-wide detection failures use Steam Support; for failure confined to Origin use the game's official support contact from Library → Origin → Support. For physical input failures use the controller maker. Collect:

  • Controller model, OS and Steam client version, game build if visible, and firmware version if known.
  • USB/Bluetooth/receiver connection, Steam's detected device name, and button/stick test result.
  • Original layout and per-game override, any existing remapper, and mode → menu result → gameplay result for each comparison.
  • Exact failing screen/action, when it began, whether another game works, and a short video if safe. Avoid showing passwords, tokens, or account details.

No Origin-specific controller log path is verified here. Send screenshots of the input test and configuration first; provide logs privately only when official support identifies what it needs. Stop immediately if a test triggers a crash; use the crash report checklist.

Steam controller FAQ

Should everyone force Steam Input on or off?

No. The correct path depends on the controller, layout, and game's input implementation. Compare per-game modes and revert failed tests; avoid changing the global setting for every game.

Should I download a controller fixer or delete profiles?

No. Keep existing profiles and settings. This guide does not require driver removal, unofficial tools, administrator privileges, or disabling game security. Use official vendor diagnostics when the Steam input gate fails.

Does Big Picture navigation prove the game supports my pad?

No. It only shows Steam is receiving enough input for that UI. Test the specific game screen separately and report partial success accurately.