[img]http://cdn.akamai.steamstatic.com/steamcommunity/public/images/clans/8067875/01c2b4f3f27fa98c6f1093cc7520509c40da8446.png[/img] The latest Steam Beta Client update includes a new feature for the Steam Controller called Activators. Activators sit between inputs (such as a button on the controller) and binding outputs (such as a keypress). They control how the input is turned into output and provide a number of settings to control this. Some simple examples are long press, double press, binding cycling, toggles, and delays. There is no limit to the number of activators that can be placed on a single input, so a button can have a normal press, a long press, and a double tap on a single button, each firing off different actions in a game. Each activator can have its own haptic settings as well. Here's a few simple ways that activators can make your existing configurations better : [list] [*]You can use a Start Press activator and a Release Press activator to turn a toggle crouch into a hold crouch. Conversely, the toggle option will allow you to turn any action, such as a hold crouch, into a toggle. [*]Turbo can be set on Activators, meaning any button can have customized rapid fire. This can be combined with multiple activators, so single press for single fire, while a long press will engage turbo mode. [*]Use a Start Press Activator to switch to a new action set, with a Release Press on the same button to switch back to the original set. Using this technique Action Sets can act like an entire-controller mode shift. Also included in this update is the ability to copy any existing Action Set into the new set, making customization a lot faster. [*]Mode Shifts now also use Activators, so a mode-shift can be toggled on and off without continuously holding a button. [*]Activators can also cycle through a set of bindings. Put Stand, Crouch, and Prone on a single button and cycle through them with each press. [/list] This update also includes better visualizations for settings such as deadzones, with more coming soon. Note that due to the nature of this change, configurations that are altered under the new setup are not backwards compatible, so modified configurations made in the beta client will not be visible to the stable client.