Files
spoopyghosty0 d787abb5df Gamepads that appear after the start reach a running 2D app; D-pad buttons in the pad layout (#162)
Agent 85: the game's container gets the host's /dev/input at /dev/fp-input (Lepton's /dev/input holds its own Wayland
input pipes) and the launcher's _gamepad_links worker keeps /dev/input/eventN links to Steam Input's virtual pads in
step while the game runs: controllers switched off and on again (Steam makes a new pad) work without a restart.
Android's EventHub adds and removes the links through inotify (dev Frame, uinput stand-in pad created after boot:
New device, Device removed, added again). Older launchers get the new gamepad line through upgrade_launchers.
The key layout also maps BTN_DPAD_* (a Steam Input layout that sends the D-pad as buttons, e.g. a stick set to
D-pad; the Frame's controllers have no D-pad of their own).
2026-10-12 23:20:29 -04:00
..
2026-10-12 20:33:12 +00:00
2026-10-10 17:18:37 -04:00
2026-10-10 16:34:19 -04:00
2026-10-10 16:34:19 -04:00