How do I set up Steam Input with a controller?

To set up Steam Input for a PC simulator, connect the controller, confirm Steam detects it under Settings > Controller, then open the game’s Library page, choose Properties > Controller and enable Steam Input. Edit the controller layout, map its buttons and sticks, and remove conflicting in-game bindings before testing.

What does Steam Input do?

Steam Input translates a physical controller into virtual gamepad, keyboard or mouse commands that a game can understand. It is especially useful for PlayStation, Nintendo and generic controllers, games with limited controller support, and custom layouts with gyro, radial menus or action layers.

It does not replace the simulator’s own controls menu. Steam determines what signals are sent; the simulator still decides which aircraft, train or camera function each gamepad axis controls.

How to set up Steam Input step by step

1. Connect the controller. Use USB or Bluetooth and confirm that Windows recognises it before opening the simulator. If an Xbox pad is missing at this stage, follow our steps for connecting and checking an Xbox controller in Windows.
2. Check detection in Steam. Open Steam > Settings > Controller. The controller should appear by name or type. Use Steam’s input test to check every stick, trigger and button; calibrate only if the raw centre or travel is genuinely wrong.
3. Enable support for the controller type. If Steam displays a support option for Xbox, PlayStation, Nintendo or generic controllers, select the appropriate setting. The wording varies between Steam client interfaces.
4. Set the per-game override. In the Library, open the game’s Properties > Controller page and choose Enable Steam Input. Fully restart a running simulator because many games enumerate controllers only at launch.
5. Choose a layout. Open Controller Layout from the game page or Steam overlay. Start with a Gamepad template when the simulator accepts analogue controller input. Use keyboard-and-mouse emulation only when it lacks proper gamepad support.
6. Map the controls. Assign stick outputs, triggers, buttons and view controls. Keep pitch, roll, steering and other proportional controls as analogue axes rather than keyboard presses.
7. Remove duplicate assignments. Open the simulator’s controls menu and clear any second binding that operates the same axis. Our guide to assigning analogue axes and removing conflicting controls covers this in more detail.
8. Test one function at a time. Check menus first, then camera controls, primary axes, throttle or power, brakes and secondary commands. Save the layout once every input behaves predictably.

Which Steam Input mode should you choose?

Use native controller support when it already works correctly; enable Steam Input when translation or extensive remapping solves a specific limitation.

A mistake we see constantly is running Steam Input alongside another controller remapper. Both layers may create virtual controllers, producing repeated button presses or two competing axis signals. Use one translation system at a time.

How should Steam Input be mapped for simulators?

Simulator layouts should preserve analogue movement and avoid applying response adjustments in several places.

• Flight controls: Map pitch and roll to joystick output, not arrow keys or mouse movement. If the simulator needs one centred rudder axis, do not assume two independent triggers will combine correctly unless the game or layout explicitly supports that arrangement.
• Train controls: Use analogue output where the title supports proportional power and braking; otherwise map the controller to the simulator’s increase, decrease and lap commands.
• Dead zones and curves: Adjust them in Steam or the simulator, not both. Stacked dead zones create a large unresponsive centre, while stacked curves make control response difficult to predict.
• Mixed hardware: Leave a HOTAS, yoke or rudder pedals as direct simulator devices unless Steam Input is genuinely required. Clear any controller axes duplicated on those peripherals.

Microsoft Flight Simulator users can follow our MSFS controller detection, profile and axis setup. For rail simulation, the Steam Input mapping process for Train Simulator Classic explains how to translate controller buttons into the title’s keyboard-driven commands.

Why is Steam Input causing double controls?

Double controls usually mean the simulator is receiving both the physical controller and a translated virtual controller, or the same function is assigned to more than one device.

• Two inputs from one press: Disable any additional remapping software, then choose either native input or Steam Input for that game.
• Aircraft controls fight or snap back: Search the simulator’s bindings by input and remove duplicate pitch, roll, yaw or throttle axes from unused profiles and devices.
• Menus scroll by themselves: Test for stick drift, add only a small dead zone, and check that the stick is not mapped as both a gamepad axis and a mouse.
• Controller works in Steam but not the game: Force the per-game Steam Input override, reconnect the controller and restart the simulator.
• Wrong button symbols appear: Xbox-style prompts are normal when Steam Input presents a PlayStation or generic pad as an XInput controller.
• Buttons work but axes do not: Replace keyboard directions with joystick output in the Steam layout, then bind that virtual axis inside the simulator.

Can Steam Input work with non-Steam games?

Steam Input can work with many non-Steam games when their executable or launcher is added to the Steam Library and always started from that shortcut.

1. Choose Games > Add a Non-Steam Game to My Library.
2. Add the game executable or the launcher that starts it.
3. Open that new Library entry and create its controller layout.
4. Launch the game through Steam rather than its normal desktop shortcut.

If a launcher starts a separate executable, Steam may lose control of the input chain. Adding the actual game executable can help when it is available, while mismatched administrator permissions between Steam and the game should be removed rather than worked around. Some protected or unusual launchers may not accept Steam Input at all.