CodaCoda

Steam Input alternative: Coda vs Steam Input

Updated

Short answer

Steam Input gives you five stick-response presets. Coda lets you build the response yourself: a custom curve of up to ten points that you feel live while editing, a second curve that takes over while you aim, and deadzone, anti-deadzone and max zone per stick — on a virtual controller every game sees, whichever launcher started it. Steam Input is free, runs on Windows, macOS and Linux, and supports gyro aiming, which Coda does not; if one of its presets already feels right, it is all you need.

Where Coda goes further

At a glance

CodaSteam Input
Stick responseSix built-in curves; custom curve of up to 10 points; separate curve while aimingPresets: Linear, Aggressive, Relaxed, Wide, Extra Wide
DeadzonesDeadzone, Anti-Deadzone, Max Zone; round or per axisDeadzone settings and an output anti-deadzone buffer
Where it appliesAny program: a virtual Xbox 360 or DualShock 4 controller through ViGEmBusGames Steam runs: the overlay hooks the game's input APIs and injects an emulated Xbox controller
GyroNot supportedSupported on the DualSense; gyro to mouse in games with a single local player
DualSense featuresCoda's own adaptive-trigger effects, lightbar in Coda's theme colour, touchpad zones as inputs (triggers and lightbar over USB)LED, trackpad, rumble and gyro; games can set adaptive-trigger effects through the Steam Input API
PriceOne-time licence or monthly subscriptionFree with Steam
PlatformWindows 10 (1607 or newer) and 11, 64-bitWindows, macOS, Linux

How each one reaches the game

Valve describes Steam Input on Windows this way: the Steam Overlay “will hook traditional gamepad input APIs such as XInput, DirectInput, RawInput, and Windows.Gaming.Input and inject an emulated Xbox controller device.” It works inside the game, through the overlay. On macOS and Linux Valve uses a driver instead.

Coda works outside the game. It reads your controller, processes the input, and presents a virtual Xbox 360 or DualShock 4 controller through ViGEmBus (the ViGEmBus guide explains the driver). To Windows that is an ordinary controller, visible to any program whether or not Steam launched it.

When Steam Input is the better fit

If you aim with gyro, play on macOS or Linux, or one of its presets already feels right, Steam Input does the job and costs nothing. It is the sensible place to start for anyone whose games all run through Steam.

Who should choose Coda

Players who have outgrown a preset and want to decide the response themselves — where the deadzone ends, how the curve rises from the centre, what changes down sights — and who play across launchers and want the same feel in all of them.

Using Coda with Steam games

  1. Buy Coda, download the installer from your account page and connect your controller.
  2. For games you launch through Steam, turn Steam Input off so Steam neither grabs the physical controller nor adds its own layer on top of Coda's: right-click the game → Properties → Controller → Disable Steam Input. It can also be switched off for a controller type in Steam's controller settings.
  3. Check in the gamepad tester that only Coda's controller shows up, then start the game.
Coda for Windows

One stick setup, in every game.

Coda's virtual controller is the same in Steam, Battle.net, Epic or a game's own launcher — with your own curve, your aiming curve and your deadzones. For DualSense, DualShock 4 and Xbox controllers on Windows 10 and 11.

Sources

  1. Steamworks — Steam Input gamepad emulation: best practices
  2. Steamworks — Steam Input source modes
  3. Steamworks — ISteamInput API
  4. Steam — DualSense support announcement (November 2020)

Related