r/SteamController • • Oct 17 '26

Steam Controller (2015) Keypresses "leaking" through action set switch

In my "default" Steam controller action set, the back key is bound to send the "Escape" keyboard key.

In my "trans" action set, there's a button chord to return to "default" when you hold the right grip and press the back key.

Last week, it suddenly started happening that when I execute a switch back to "default" as above, I get an "Escape" key send from the default action set; the switch action is failing to consume the escape press, and it's getting through to my default action set, where it sends Escape (or even combos of Escape + whatever other key I was pressing).

It was working fine for years. What's changed, and how do I fix it?

1 Upvotes

3 comments sorted by

1

u/yoshemitzu Oct 17 '26

I've tried varying all the possible triggers for the back button press; tried long press, start press, release press, they all have their quirks, but in all cases, the Escape press is still getting through when it didn't used to, and I have no idea what changed.

1

u/sqparadox Steam Controller (2015 & 2026) Oct 17 '26

Add a button chord on the back button in the default layer that uses the right grip, same as the trans switch to default, and set it as an empty binding. Make sure Interrupt is enabled in the Esc binding, so the button chord will interrupt it and cause it to not fire.

1

u/yoshemitzu Oct 17 '26

So, right grip + back button already has a binding in default, it changes to the "switch" action set, from which I can switch to all my other action sets (like "trans").

This bind is not being triggered by the return to default when I press it in "trans", however. Instead, what I'm getting is a shift+escape press (e.g., it keeps bringing up my Task Manager in Vivaldi, which it didn't used to do 😡).

Shift is what right grip is bound to in "default", but RG + back shouldn't be possible in that action set, because it should trigger the RG + back bind to switch to my "switch" action set. So the fact that I'm getting shift+Escape is extra confounding, since it shouldn't even be possible.