mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 13:02:03 +00:00
[PR #384] [CLOSED] Replace existing controller on re-arrival instead of skipping #435
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#435
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?
📋 Pull Request Information
Original PR: https://github.com/games-on-whales/wolf/pull/384
Author: @kmreisi
Created: 4/5/2026
Status: ❌ Closed
Base:
stable← Head:fix/reconnect-replace-controller📝 Commits (1)
462ee49Replace existing controller on re-arrival instead of skipping📊 Changes
1 file changed (+19 additions, -11 deletions)
View changed files
📝
src/moonlight-server/control/input_handler.cpp(+19 -11)📄 Description
Summary
When a Moonlight client reconnects, it sends CONTROLLER_ARRIVAL for controllers that may already exist in the session (carried over via resume). Previously this was skipped with a TODO comment, leaving stale virtual devices in the container.
Now the old pad is unplugged (UnplugDeviceEvent) and removed from the joypads list before creating a fresh one, ensuring the container always has exactly one device per controller after reconnect.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.