Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I could, but that still does not solve the Problem of the Steam-Client randomly picking another Drive.
Today it was even worse as i tried to block patch Files to be cached on it by unplugging it.
The Download was no longer working until i completly uninstalled the Game from the SSD and initiated an entire new Download.
Also, there are some other Files on that USB Drive too, some back-up files and notes. (basicly everything that does not require that much of speed).
And it would be annoying to unplug and plug a Drive all the time. Would prefer it to be able to set the Location of the Cache-Files to a specific Drive (would even prefer it to download the cache on the 1. one instead of anywhere else.
And what exactly is a Symlink and how would that work with Steam?
What symlink does it redirects where the app to read, and write to so example if usb drive is F drive, and 2nd drive is D, you made symlink for one folder on F to D drive, it will think it writing or reading on F drive but actually doing it on D drive.
And how need that to be set up in order to work with only the Steam-Cache-File-Downloads?
You open command prompt then do the following.
mklink <Option> <Link> <Target>
mklink <--- mean you want to symlink.
Option <--- mean what kind of symlink in your case you want /d as it means soft symlink, there hard link, and junkion link, but soft link all you need really easy, and simple.
Link <--- mean what it from.
Target <--- mean what it want to go to.
Let say want a folder from D drive to be done at C drive that
d:/Steam/Steamapp/downloads
C:/program/Steam/Steamapp/downloads
So you write it like this.
Mklink /d d:/Steam/Steamapp/downloads C:/program/Steam/Steamapp/downloads
As you notice /d is your soft link, then got link you want the folder to be redirected to your target link you put.
But would that not still run over the Connection of the Drive from D:?
(Cause if its just some sort of transfer command, it would still be slowed down by the USB Connection)
And also would Steam be able to read those Files correctly then when it needs to unpack them for installation/update or would it simply think that the Download failed cause it cant find it in the Location Steam expected them to be?
That why I suggest just link to folder that need it to write, or read from example as your download folder, and target to your download folder on other drive. So any files it writes, and read that include unpacking, and all that done within the download folder, will be done at the target folder, and game you target to install, or apply patch to on your usb drive will still be applied as you would normally just that download, and unpack be done else where in said folder.
Thanks for the Information and Explanation.
I will try that and see how the Steam-Client behaves next time it tries to store Cache-Files on the USB again.
Still weird, that Steam even does this; random picking where it stores cache-files.
Worst part of the slow read and write of files process on an USB is,... that the Download tends to wait on that too, so an already slow download gets paused from time to time and without knowing about what is actually happening, looks like the Download is bugged or something.
Steam lets users choose which location the Install happens, but somehow does not put up an option for where the Cache Location should be.
I read about that. But my Drives have enough Space. Its the USB that is actually the fullest one (for keeping the Games i am not currently playing stored) while the others contain only the ones i do play.
And the Main Drive has even more Space available, cause i dont store any Games on that one.
From what i have seen, the Client really seems to decide randomly which Drive it uses for Cache Files, no matter how much Space there is and no matter where the actual Game is installed.
I once expected it to be the result of; the Last activity on Steam-Folders on specific Drive.
But the way it kept behaving did not support that as i had multiple Games in the Download-List and 2 of those Games (from the middle of the List) had it again with Files getting sent to USB for some reason.
I tried that now.
But sadly it did not work on my PC as i hoped it to work. Things i tried to Download, that seemed to try to use the USB again, got an Error message and no matter how much i click on *retry* it just keeps showing the red *Failed* Text.
Seems like that my Steam-Client does not like to be redirected to somewhere else.
But i got another Idea on how i could solve the Problem based on;
Seems you where right in some sense here.
Even with enough Space (shown to me at least), Steam still thought that there was not.
According to the Answer i also got from the Support, it takes double the Amount of Space it shows that it requires for the Downloaded Files themselfs.
I am not sure why it then does not like the free Space that still exist on the other Drives, but it gave me an idea;
- I put more Stuff on the USB now to fill up the Space there so that Steam has no other Choice than to use one of the internal ones for the Cache-Download. -
(not the optimal solution, but the USB was meant to keep Games stored anyway)
Thanks again to all the Informations i got here from you Guys.
You could also deactivate it, making Steam think that its unplugged when you start your downloads.