Steam Controller

Steam Controller

shadowboy813 Apr 15, 2018 @ 3:27pm
Action sets and action layers
I've observed through some of the more complex setups I've made with my steam controller setup that action sets are prioritized over action layers.

What I mean by this (and a way for you to see what I mean), Let's say you create an action layer for a given action set, and later on, decide you wanted to add a separate action set. An example of this is that I recently added an action layer in witcher 3 to implement a double-press-and-hold-then-press-again-to-toggle-off (so I don't have to double tap then hold a button while galloping). After implementing that, I decided I wanted to set up an Ansel action set by binding ansel to some weird button press configuration on the controller that's never used (say Stick click +A), then switch to an Ansel action set that is kb/m based. Once I added the Ansel action set, it broke my double-click-and-hold binding.

The reason is that the steam configurator seems to bind to action sets/layers by order and it numbers the orders by action set > action layer. This broke my binding because the "apply action layer" binding seems to be relative, rather than absolute. Before adding the Ansel action set, my next "action set" was the double-press-and-hold action layer. Because the configurator puts action sets before action layers, it swapped all references to the double-press-and-hold to the ansel action set, breaking my configuration.

I propose instead of ordering action sets as: Action sets > action layers, it be ordered as action set 1 > action layers for action set 1 > action set 2 > action layers for action set 2, etc. That way any hold/apply/remove bindings for action layers don't mysteriously bind to a random action set when you decide to refine your configuration by adding new action sets.
< >
Showing 1-4 of 4 comments
Mennenth Apr 15, 2018 @ 4:43pm 
I've never encountered the issue so I'm not entirely sure whats going on. That said +1, fixing issues is a good thing.

Though as far as Ansel is concerned, why not put Ansel bindings in the Guide Chord configuration so its more universally accessible and you dont have to rebind Ansel for every game you want to access it with?
shadowboy813 Apr 15, 2018 @ 6:49pm 
Because the inputs for Ansel are decidedly different than what might be for a game, so I want to be able to swap action sets to use one specifically for Ansel, then go back to the game's basic action sets. As far as I know, there is no way to use a Guide chord to change out an action set (and to use guide chord for every input in Ansel would be cumbersome), so I'd have to do it per game.

To explain what is going on with this Witcher 3 specific example: In tweaking my SC config for witcher 3, I had made an action layer that allows Roach to gallop without me having to hold any buttons for ages (It's a big game world, so you sometimes have to travel decently long distances). So I set up an action layer called "Gallop Toggle." A double press on the left paddle will apply this action layer. The action layer basically has two activators on the "always active" keybinding. A "start press" activator hitting A, and a regular press activator on a short delay also pressing A. This means that double tapping the left paddle will switch to this activator, which will tap the A, then Tap A a second time and hold it (which is what you do to gallop when on a horse in Witcher 3). This action layer also binds a regular press A, long press B, or regular press on the left paddle to remove the "gallop toggle" action layer so the bindings return to normal. Some time after making this action layer, I decided to make an Ansel action set as a completely separate action set. As soon as I had done so, every refrence to the "Toggle Gallop" action layer were now instead made to the "Ansel" action set. I had to go back and change the left paddle double press activator back to "apply action layer - Gallup Toggle" and then go into the Gallup Toggle action layer and change all of the "remove action layer" bindings to also refer to Gallup Toggle because they also now referred to the Ansel action set. This is unexpected behavior. If you use the right bumper to cycle through action sets in the configurator, it will go through all action sets, THEN go through all action layers.

Expected: Default > Toggle Gallup > Ansel
What happened: Default > Ansel > Toggle Gallup (an action layer of the default action set).

On complex configurations it can quickly become a mess if you start adding multiple action sets & layers (like the configuration I devised for Far Cry 5).
Last edited by shadowboy813; Apr 15, 2018 @ 7:00pm
Mennenth Apr 15, 2018 @ 7:17pm 
Okay I see. IDK if they did it that way on purpose, from my understanding layers were always supposed to be set specific.

It could very well be a bug, go report it.
lagamemnon Nov 30, 2018 @ 9:07am 
It would also be nice to share an action layer between action sets. For example, a layer that applies to a control that performs the same function (and can take the same modifications) across multiple sets.

A more concrete example would be a layer that applies to a movement control that is the same across sets for ranged vs. melee attacks.
< >
Showing 1-4 of 4 comments
Per page: 1530 50

Date Posted: Apr 15, 2018 @ 3:27pm
Posts: 4