安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
The family options are for sharing a library between accounts, not sharing a steam link between accounts.
Steps I would assume would work.
1) sign out of steam
2) install steam to a 2nd drive or partition.
3) download and install sandboxie to the same drive
4) add the new install of steam to your sand box
5) open the new download of steam via the sandboxie menu and sign in.
6) in steam settings point the game directory to your main steam account.
7) open your normal steam exe and sign back in.
8) set up family sharing across the 2 accounts.
In theory this setup will allow you to pair his steam link to his own account and give him access to all of your games with his own achievements but saves may be shared since it's the same install folder.
(I would assume for the initial pairing be signed out of your main account , if it doesn't detect the pc sign into his account with your normal exe and pair then switch and test)
Alternativly you can always use this as an excuse to buy/build yourself a new PC lol.
With family sharing active you can both play games at the same time, just not the same game at the same time.
This problem has been bothering me for a while now and finally I've come up with a workable solution (with batch scripting).
My first attempt was to kill all steam processes using a script and start steam again via command line (e.g. steam -login un pw).
This worked when calling the script on the local PC but was useless via Steam Link.
I then came up with a solution that reboots your PC and logs in the other account.
For this solution you will have to do a couple of things:
1. Make sure steam on your PC does not boot by itself when the PC boots (the script does that for you)
2. Do not check the checkbox "boot into big picture mode" on your PC
3 Add the script below to a batch file and use some tool (e.g. http://www.f2ko.de/en/b2e.php) to convert the batch to exe
4 Once you have the exe, add it as a non-steam game to your library
5 I have made two batch files/exes. When playing via account X you need to be able to go to account Y but off course you also want to be able to go to account X when you are playing via account Y.
Be aware that the script restarts the host PC, so it depends on your PC how long the process will take. At least you don't have to get up and walk to the PC, which off course we all want to avoid because we are lazy af. :D
Copy and paste the following into a script and off course, fill in {PCUSERNAME} and {UN} and {PW}:
@echo off
set filepath="C:\Users\{PCUSERNAME}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\"
IF EXIST %filepath%\startSteam.bat (
del %filepath%\startSteam.bat
goto write
) ELSE (
goto write
)
:write
@echo steam -login {UN} {PW} > %filepath%\startSteam.bat
shutdown -r -t 2
EXIT
Sorry for resurrecting this old thread, but I'd like to understand why this was useless via Steam Link? Is it because the batch/exe process gets terminated as soon as Steam gets killed? Maybe using some other mechanism to run the process that terminates and restarts Steam would work? Something equivalent to nohup on Unix/Linux? E.g. maybe it can be run as a scheduled task?