Fix controller mappings with Steam Input per game
Use a separate controller layout for each game, test native support first and change one mapping at a time.
In brief
Steam Input can translate a controller’s buttons and sticks into inputs a game accepts. It is useful for older games or custom layouts, but adding it on top of another mapper can create duplicate presses.
A per-game setting lets you fix one title without disturbing a controller that already works correctly elsewhere.
Start with a clean input path
Close other controller-mapping applications for the test. Use one controller and launch the game through Steam. If the game already has native support, compare the default setting with Steam Input disabled for that game. Keep whichever produces correct input; enabling every option is not a diagnosis.
Build a layout around the actual task
Use the game’s Controller Layout screen to map an awkward action to a reachable button. For a mouse-controlled menu, map only the needed pointer and click actions. Change stick dead zones gradually: too small may reveal drift, while too large removes useful movement. Save the working layout before experimenting further.
Recognize what mapping cannot solve
If the controller disappears from Windows or disconnects from Bluetooth, fix the connection first. If buttons work but the game displays a different brand’s icons, that may be the game’s UI rather than a hardware fault. Do not install unsigned drivers just to replace on-screen button labels.
Before you act
Controller glyphs and advanced features depend on the game, controller and connection. Steam Input does not guarantee the full feature set of a native console connection.
What to do next
- Confirm the controller is detected in Steam Settings → Controller.
- Open the game’s Properties → Controller and check its Steam Input override.
- Test the default layout, then edit only the buttons or sensitivity that need changing.
