[Steam Deck] Triggers in Action Set Layers forget their inheritance

[gwemmie]

Your system information

• Steam client version (build number or date): Current newest version on Beta Stable branch as of today (just updated)

Please describe your issue in as much detail as possible:

Trigger settings in the control schemes for my games will "forget" whatever they've inherited from their parent set, if they are set to inherit from a parent set.

Sometimes they A) completely unbind themselves and just show up as "Trigger" with both Soft and Full press also unbound, and sometimes they B) show up as exact copies of what is bound in the parent set. Either way, they are still in italics as if they were still inheriting, but fully expanded and without "Inherited" anywhere, as if they weren't still inheriting, unless I manually change it back to Inherited myself.

Whether it does A or B is completely random across individual Action Set Layers across individual games, but consistent, i.e. if Action Set Layer # 1 does A, it will continue to always do A, and if Action Set Layer # 2 does B, it will continue to always do B. In the case of A, they really are unbound--they cease to do anything in-game until I reset them myself. B manages to retain the bindings that it had inherited at first. With both A and B, they're definitely not still inheriting, because when I change the binding in the parent set it doesn't reflect on that child.

I noticed that a recent changelog entry from before I even had my Deck mentions fixing this issue--but I've had it since day 1 of ownership, and I still have it now despite being fully up to date. I'm experiencing it on every game, regardless of whether I'm using analog gamepad triggers, triggers bound to keyboard/mouse buttons, or triggers bound to Game Actions like in No Man's Sky. There is no pattern that I can discern to whether each Layer follows behavior A, or B.

Steps for reproducing this issue:

1. Create a control scheme for a game that utilizes Action Set Layers and does not rebind the triggers, leaving them to inherit from the parent set.
2. Steps I've found so far to trigger this bug:

• Restart the Steam client (either by rebooting or switching to desktop mode and back)
• Load any controls profile or template that is configured this way. I'm not sure if it's that they're not loading properly or not saving properly--I can't know that since there is currently no way in the Deck's UI to look at a control profile's bindings without first loading it as your current set profile.

3. Look at the Trigger section of any Action Set Layer that has a parent set.

The only workarounds I've figured out so far are to either keep setting them back to inherited every time they forget, or to just give up and set them manually, especially so that the Layers that behave like A--i.e. become unbound--actually retain their trigger bindings.