You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some config options in Sunshine make sense to be specific to an application instead of global. We could potentially handle this like global prep-commands, and application prep-commands are handled.
A use case for per-app options, with some numbers, in case it helps scope this. The option I'd want first is the gamepad type (what #4863 tried).
I stream a Switch emulator (Eden/Lichii) from Linux with Sunshine v2026.914.233613. Eden binds each player to an exact controller GUID, and with gamepad = auto the virtual pad Sunshine creates depends on the client:
Moonlight on iOS with the on-screen controls: Xbox Series pad, Bus 0005 045e:0b13 v0513, created about 66 s after the app launched.
Moonlight on a Switch: DualSense pad (log says "auto-selected by motion sensor presence"), Bus 0005 054c:0ce6, named "Wireless Controller", created about 4.6 s after launch.
Different VID/PID means a different SDL GUID, so player 1 only works for one kind of client. The app can't adapt at launch either: the pad shows up after the app starts, and SUNSHINE_CLIENT_GCMAP only says that the client has a controller, not which type Sunshine will create. Right now I work around it with a launcher script that waits for the pad and rewrites Eden's config, which is fragile.
A per-app gamepad override would fix it: I'd set the emulator apps to one type (probably ds5, for motion), so every client gets the same pad and the same GUID.
A related thing I hit: Eden still had player 1 pinned to the Xbox One pad an older Sunshine created (045e:02ea v0408), and the current one creates the Xbox Series pad above (045e:0b13 v0513), so the binding broke after the update. A stable identity for the virtual pads across versions would be nice too, even if that's a separate topic.
Activity
[-]Application specific config options (Sunshine)[/-][+]Sunshine: Application specific config options[/+]EnriqueWood commentedon Nov 14, 2026
A use case for per-app options, with some numbers, in case it helps scope this. The option I'd want first is the gamepad type (what #4863 tried).
I stream a Switch emulator (Eden/Lichii) from Linux with Sunshine v2026.914.233613. Eden binds each player to an exact controller GUID, and with
gamepad = autothe virtual pad Sunshine creates depends on the client:Bus 0005 045e:0b13 v0513, created about 66 s after the app launched.Bus 0005 054c:0ce6, named "Wireless Controller", created about 4.6 s after launch.Different VID/PID means a different SDL GUID, so player 1 only works for one kind of client. The app can't adapt at launch either: the pad shows up after the app starts, and
SUNSHINE_CLIENT_GCMAPonly says that the client has a controller, not which type Sunshine will create. Right now I work around it with a launcher script that waits for the pad and rewrites Eden's config, which is fragile.A per-app
gamepadoverride would fix it: I'd set the emulator apps to one type (probablyds5, for motion), so every client gets the same pad and the same GUID.A related thing I hit: Eden still had player 1 pinned to the Xbox One pad an older Sunshine created (
045e:02ea v0408), and the current one creates the Xbox Series pad above (045e:0b13 v0513), so the binding broke after the update. A stable identity for the virtual pads across versions would be nice too, even if that's a separate topic.