安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
First you will need to have free space at least the same what game needs when installed. That should be all it needs for steam to use same drive for temp files when updating.
If not you will need to have the game on steam library that is first in the library list. And that library being default.
Or like said above folder junctions.
You can't directly configure the folders steam uses... Therefore junctions are your best option to achieve the outcome you want. I.e. pointing one folder to another.
Plus moving just the download folder to your SSD would not fix it. Steam is patching files. Just because the data with the patch instructions would be on the SSD doesn't mean that there wouldn't be tons of patch work to the files on the HDD(where the game is located).
Re junctions, like seconds later in a google search you'd know what they are ;-).
TLDR Symbolic links... Allows you to redirect one folder to another invisibly to applications.
Helpful in this situation where steam decides to use slower disk for caching. Merely point the slow folder to the fast folder and regardless as to which one steam tries to use... The data will arrive in the destination you decided upon.
I know what folder juctions are, I just don't want to do that.
I know how to do many things in life that I don't want to.
I will just delete the Steam library on the HDD...
doesn't mean that there wouldn't be tons of patch work to the files on the HDD(where the game is located).
Are you sure it's not trying to download another copy of ark to the HDD maybe because of an appmanifest that was not removed? the download would be huge though assuming there isn't a copy of ARK already on the hdd. I guess you could try clearing the download cache on the same downloads setting page.
My original steam location was on a hdd and Ark had a dedicated Nvme, but still Steam was caching to the HDD.
You basically have 2 options, reinstall like i did or do as Zerassar suggests.
I've heard various explanations suggest that it should be the same cache as the library its installed... Others say its the default libraries cache... Others say its the one with the most free space.
However it is supposed to work... You'll find a bunch of people here on the forums after each big patch or DLC launch complaining of slow install speeds. When they subsequently use Resource Monitor to track the disk IO activity its noted that steam is pulling/writing patch info from/to the download cache on the HDD. So its an incredibly common issue.
Clearing of the DL cache just resets the download and it starts to download to the same cache again. No change.
Changing the steam default library also has inconsistent results. Some claim it worked for them... But in my experience it doesnt.
Its why I turned to the junctions as a solution as it then didnt matter what sillyness steam tried it'd still go to the same place. Has worked a treat for me since.
Though the OP for their reasons doesnt wish to do that. Each to their own.
Pretty much just having a library on both an SSD AND a HDD was enough to start the inconsistent behaviour. Which for most games it wasnt noticed. But with how big ark is... and how painfully slow HDD's are with ark patches... Well it gets noticed.
Yes Steam is installed on C: (small SSD with no games, only Windows and Page File)
HDD is D: and had some games where loading wasn't a concern.
And E: is a large 1TB SSD.
All games, despite being installed on D: or E: (never C:) were using D: as the temporary download folder.
After downloading, Steam starts decompressing the downloaded files and installing them. This was ok for the games installed on D:, since they never get large patches.
But for the games installed on E: (like Ark), using D: as the \steamapps\downloading was causing the 360MB download to finish in about 2 minutes, then waiting 2 hours, while applying those 360MB inside a 45GB file inside Ark. This process includes decompressing 45GB from the SSD to the HDD, replacing new files, then re-compressing it back to the SSD.