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
In the process of figuring out why I could connect on Sunshine via moonlight but the sometimes the controls on Steam didn't work, I discovered that the controls only work if and only if Steam is launched via /usr/bin/sunshine-run like /usr/bin/sunshine-run /usr/games/steam steam://open /bigpicture .
This is also the same for Heroic Game Launcher and others. In other words, for control via Moonlight to work, the software must be a child process of Sunshine's /usr/bin/sunshine-run command.
The problem is that docker-steam-headless starts Steam in some places independently of sunshine-run :
and also the session autostart Steam option and the shortcuts on the menu
What is your feature request?
Ensure Steam is started as a child process of /usr/bin/sunshine-run in all parts that maybe start steam automatically or manually, like the Steam entry on the menu and all the autostart scripts
Are there any workarounds?
I replaced the default "Detached Commands" of the Steam Big Picture application configuration inside Sunshine
This is the content of the start_steam_via_sunshine.sh command
#!/bin/bashecho"Stopping Steam"# Check if Steam is running before attempting to stop itif ps h -C steam > /dev/null;then
/usr/games/steam steam://exit
elseecho"Steam is not running."fi# Wait for Steam to stopwhile ps h -C steam > /dev/null;doecho"Waiting for Steam to stop..."
sleep 1
doneecho"Starting Steam Big Picture via Sunshine"
/usr/bin/sunshine-run /usr/games/steam steam://open/bigpicture
Note: The best way to ensure that everything will always work is to force quit Steam even if Steam was launched via sunshine-run, but quitting and starting Steam again is a slow process.
Maybe it would be better to improve my script so as not to force exit if it was started via sunshine-run
Additional Context
No response
The text was updated successfully, but these errors were encountered:
This is interesting. I have not experienced this myself.
One thing i would point out is that by stopping steam and restarting it every time you connect via sunshine, it means I would also always need to select the profile each time. This means steam link would stop working after using a sunshine session.
Is your feature request related to a problem?
Yes.
In the process of figuring out why I could connect on Sunshine via moonlight but the sometimes the controls on Steam didn't work, I discovered that the controls only work if and only if Steam is launched via
/usr/bin/sunshine-run
like/usr/bin/sunshine-run /usr/games/steam steam://open /bigpicture
.This is also the same for Heroic Game Launcher and others. In other words, for control via Moonlight to work, the software must be a child process of Sunshine's
/usr/bin/sunshine-run
command.The problem is that docker-steam-headless starts
Steam
in some places independently ofsunshine-run
:docker-steam-headless/overlay/etc/supervisor.d/steam.ini
Line 13 in 47f6f7a
docker-steam-headless/overlay/etc/cont-init.d/90-configure_steam.sh
Line 10 in 47f6f7a
and also the session autostart Steam option and the shortcuts on the menu
What is your feature request?
Ensure Steam is started as a child process of
/usr/bin/sunshine-run
in all parts that maybe start steam automatically or manually, like the Steam entry on the menu and all the autostart scriptsAre there any workarounds?
I replaced the default "Detached Commands" of the Steam Big Picture application configuration inside Sunshine
from
to
This is the content of the
start_steam_via_sunshine.sh
commandI read https://developer.valvesoftware.com/wiki/Command_line_options#SteamCMD and just tested the commands and discovered that I can make Steam exit and close via
/usr/games/steam steam://exit
Note: The best way to ensure that everything will always work is to force quit Steam even if Steam was launched via sunshine-run, but quitting and starting Steam again is a slow process.
Maybe it would be better to improve my script so as not to force exit if it was started via sunshine-run
Additional Context
No response
The text was updated successfully, but these errors were encountered: