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
Step 1) Do not use steam libraries on network or removable drives
Step 2) Look at step 1
Steam does not support network or removable drives for its libraries
If you use them, you do so at your own risk, because the problem is literally the thing you are experiencing, because you're doing something that is unsupported.
Good luck harl windwolf with the advise you will get on these forums.
Satoru is supposedly all knowing here, but even when describing the SWR behaviour in my posts all he came forward with was that my SSD was toast and corrupted and my PC was totally hosed, yet he can freely tell you that what you're experiencing is down to what you're doing by using a networked drive.
If he knew the deleting of SWR happens when a drive (or Library) is not discoverable then wtf didn't he explain this to me? Instead he sat back and watched me posting, describing the behaviour of SCR deleting files each time it updated, when now I know why it's deleted the files if what you say in your post is the actions it takes if a drive is disconnected or undiscoverable.
Thanks Satoru you're a legend keep up the great work, BTW I fixed the problem solved by someone on Discord who had suffered the same issue for weeks, the solution? Delete the DayZ Documents folder, not spend $140.00 on a new SSD or outlay more money on a new PC.
I think Satoru didn't understand the purpose of my post (or didn't read all of it).
My situation is, that a large portion of the games I play are not on the local drive(s) because (when I'm on the laptop) I need the space for other things (mainly work and other hobbies), plus I want to be able to play the same games from either the laptop or the PC.
We also don't always have everything powered, but Steam auto-starts on every machine, so it often happens that I'm on either one without wanting to make sure all the sources/drives are available at that moment. Or even if they were available at first, of course sometimes they'd become unavailable later. Any of this is enough for Steam to consider the games not installed (or removed or whatever) and just delete SCR.
I really can't change much about my current situation, anyway.
In my opinion, this is a very inconvenient behaviour by Steam and could be remedied rather easily with just a few lines of code.
https://help.steampowered.com/en/faqs/view/4578-18A7-C819-8620
the solution to this, is to run in an supported configuration
Steam is not going to fix something that they themselves say is broken and unsupported
SOLUTION: Do not store games or steam libraries or steam on remote or removable drives. Move your Steamworks Common Redisributables back to your local drive.
That is the solution.
The solution is not "here is the myriad of weird things you have to do like hand stands and sacrifices to Gaben in order for things not to break"
If you want to store games on network drives, you're free to do that.
But realize that you will encounter problems and those problems are known by Steam and they outright tell you to not do this.
Note the Steamworks depot is dynamic. It depends on the games you have installed.
So here's how the redisributable depots work
* A game is made up of 'depots' think of them like ingredients
* A specific game that might need say DotNet4.0 will add that 'depot' to their game
* When you install a game, it checks and sees "Ah you need DotNet4.0" and adds that to the Steamworks Common Redistributable
When you delete a game aka, when your network dies and your library dies with it
* Steam checks if any other game needs DotNet4.0
* Steam sees "oh cool no other game needs DotNet4.0"
* Steam deletes DotNet4.0
* Steam might also see your locally installed game X still needs say vcredist2015. so that won't be deleted
Again steam is doing exactly what it was designed to do. You 'delete' your games from your libraries. Steam correctly detects that installed games, no longer need various redistributables, and removes them, because again you don't need them anymore
Solution : Stop installing games on the network
And of course you're free to voice your opinion, that one should just accept Steam as it is when they don't recommend to use external or networked storages, but your "solution" just doesn't seem constructive at all to me, but rather fatalistic / submissive
.
My stance in this matter is different and I think that there's always room for improvement, or methodical changes as long as they involve improvement in one or another form. In my opinion, everything is open to be criticised, discussed or expanded.
I'm not expecting this to be considered on a short-term basis, but the issue remains the same.
https://help.steampowered.com/en/faqs/view/4578-18A7-C819-8620
If you make a problem of your own creation, the solution is to stop doing the thing you know is the problem.
So in your OP you want 'workaround/solutions'
I gave it to you
https://help.steampowered.com/en/faqs/view/4578-18A7-C819-8620