mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-16 05:22:03 +00:00
[GH-ISSUE #530] gamepad is not recognized by Heroic (Chromium/Electron) until re-attached #323
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#323
Loading…
Add table
Add a link
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 @avgoor on GitHub (Oct 6, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/530
What happens
When the Heroic Games Launcher app is started from the UI with a gamepad already connected, the app does not recognize the gamepad and the navigation in the app doesn't work. However games spawned from the app recognize the gamepad just fine.
How to reproduce
Just launch the Heroic app from the UI having the gamepad already powered on. Navigation in Heroic won't work.
Workarounds
Both methods make Heroic recognize the attached gamepad and navigation starts working.
Why it matters
My remote gaming client normally does not include a keyboard or a mouse so in many cases I use gamepad for all the navigation around. I have no issues running Steam games with gamepads and want to have similar experience with Heroic.
Setup
wolfcontainer built from commitfacb8e0(current HEAD)gow/apps/heroic-games-launchercontainer built from commitbc4bb67(current HEAD)dockerver:29.8.2