Codex
Steam Input
Introduction
First you should understand what Steam Input is and is not, the only real place to do so is via Valve's documentation and videos on the feature.
Steam Input (Steamworks Documentation)
In-Game Action file
In-Game Actions File (Steamworks Documentation)
This is how you define what action sets, layers and actions your game has and how they are used (loosely). Using this Steam's controller binding system can be used to map various controls to your actions and your game can thus be blissfully unaware of what IO device is actually driving the game.
An action set is simply a container of layers and actions. For example you might have 1 set of actions you use in your menu and another you use in gameplay so you might have an action set
menuActions and another gameActions .An action set layer is a mask laid over top of an action set. They are defined as a member of the action set and simply modify the set of actions activated by the set. An example might be a layer that adds extra mappings such as a sniper mode when a valid weapon is equipped or vehicle type specific actions such as gas, brea, throttle up/down, etc.
An action is ... well the action the player has requested such as jump, walk, shoot, etc. These are defined as members of an action set or action set layer and can specify what kind of action they are e.g. analog or digital and if analog what mode e.g. stick, absolute mouse, etc.
To Create
Analog vs Digital Actions
You can toggle your Action types by simply clicking the AI/DI button
AI represents an "Analog Input"
DI represents a "Digital Input"
Last modified 4mo ago