mirror of
https://github.com/safijari/openpuck.git
synced 2026-11-03 22:30:22 +00:00
[GH-ISSUE #258] Back buttons can remain stuck in Steam Input after switching USB modes (0.9.51) #116
Labels
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
safijari/openpuck#116
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @J-A-McCrae on GitHub (Aug 29, 2026).
Original GitHub issue: https://github.com/safijari/openpuck/issues/258
Back buttons can remain "stuck" in Steam Input after switching USB modes (0.9.51)
I'm running OpenPuck firmware 0.9.51 (tested previously on 0.9.31) on Windows 11.
I realise 0.9.28 included a fix for "stuck inputs when changing modes", but I appear to have found a remaining case where the four back buttons used for the mode-switch shortcut can become stuck from Steam Input's perspective.
What happens
My Steam Input Desktop Layout uses the controller's back buttons to activate different action layers.
If I:
Start in Steam Controller mode.
Hold all four back buttons + X to switch OpenPuck to Xbox 360 mode.
Hold all four back buttons + A to switch back to Steam Controller mode.
Steam Input behaves as though one or more of the four back buttons are still being held down after returning to Steam mode, even though I have physically released them.
This causes the action layers assigned to those buttons to remain active. Initially I thought this was a right-trackpad problem because my normal Desktop Layout has the right trackpad configured as a mouse, and the mouse functionality stopped working after switching back to Steam mode. I then realised other controls were also behaving according to the action layers assigned to the back buttons.
Reproduction / workaround
After returning to Steam mode, pressing and releasing each of the four back buttons individually immediately clears the problem and restores the Desktop Layout to normal.
Restarting Steam also clears it.
Turning the controller off and back on does NOT clear it.
Physically unplugging and reconnecting the OpenPuck does NOT clear it.
Steam's controller input/test screen also continues to show all controller inputs, including the right trackpad, correctly while the problem is present.
Possible cause
I wonder if Steam Input is seeing the four back buttons being pressed for the mode-switch shortcut, but OpenPuck changes/re-enumerates its USB mode while those buttons are still held.
If Steam does not receive button-release events before the Steam Controller interface disappears, it may retain those buttons internally as being held down. When OpenPuck returns to Steam Controller mode, those stale button states then continue activating my Steam Input action layers.
Pressing and releasing the back buttons individually appears to provide the missing release events and immediately fixes the issue.
Would it be possible for OpenPuck to send a neutral/all-buttons-released controller report before switching away from Steam Controller mode, so that Steam Input has a chance to clear the state of the four back buttons before the USB interface disappears?
.hexfirmware artifacts in CI release outputs #208