Steam client version (build number or date): Current newest version on Beta Stable branch
Please describe your issue in as much detail as possible:
I've set up a control scheme for FTL where, on the Default Action Set, the left pad is bound to a touch menu with 12 commands. On another layer, which I have set to Hold on a grip button, I have the left pad bound to a totally different touch menu with 9 different commands. The configuration UI for this control scheme reflects that just fine--it respects that Default has 12 commands on that touch menu, while the other layer has 9. Including in the drop-down menu where I explicitly set those two amounts--although this behavior still persists if I set both to "Same As Command Count" instead. However, when I actually use this control scheme in-game, the other layer's touch menu displays 12 commands instead of 9, and sets the last 3 to what they're set to on the Default layer.
Steps for reproducing this issue:
Create a control scheme with a touch menu
Add an Action Layer with a different, not inherited, touch menu bound to the same place
Set that 2nd touch menu to have a different amount of commands than the 1st.
Your system information
Please describe your issue in as much detail as possible:
I've set up a control scheme for FTL where, on the Default Action Set, the left pad is bound to a touch menu with 12 commands. On another layer, which I have set to Hold on a grip button, I have the left pad bound to a totally different touch menu with 9 different commands. The configuration UI for this control scheme reflects that just fine--it respects that Default has 12 commands on that touch menu, while the other layer has 9. Including in the drop-down menu where I explicitly set those two amounts--although this behavior still persists if I set both to "Same As Command Count" instead. However, when I actually use this control scheme in-game, the other layer's touch menu displays 12 commands instead of 9, and sets the last 3 to what they're set to on the Default layer.
Steps for reproducing this issue: