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
https://steamcommunity.com/discussions/forum/1/3951406749565133259/?tscn=1699651594
The tool worked for me when I recently needed it to delete a whole lot of Dirt 3 cloudsaves.
It's just WAY overcomplicated than it should be.
Well; the major problem is that you have to fight Steam's synchronization and have to deal with games that a) might not offer ingame means to delete files; b) might mark files as in use, not actually allowing you to delete them; or c) might just autosave-on-close and recreate anything you deleted before the sync gets to run, putting you back at square one.
Dummy-ing out the actual game executable this way is a path of least resistance with the options that an end-user currently would have. (And if you're on Linux, then certainly you'll know how to cook up the bash equivalent, right?)
I agree that the whole thing is complete insanity and Valve really should offer better tooling for their end-users. But considering their overall laissez-faire attitude towards quality-of-life improvements not just for end-users but even for their own full-time staff, I'm inclined to believe any pining for a solution from their end is a pipe-dream at the very bestest-of-bests.
(Also; I believe that's a decent go at a personal record for most hyphens in a reasonable-sized run-on sentence.
Yup. It actually follows, for all intents and purposes, normal procedures as-if the game itself had actually deleted the files. There's no potentially-fatal wizardry involved in trying to manually manipulate the bookkeeping files that record the state of the sync.
It's annoying; and it makes you jump a hoop; but at least it's safe. At least from the perspective of not tampering with Steam's bookkeeping and leaving the whole thing in an invalid state. (Which, yes, can happen.)
If you delete the wrong files; or don't delete all the files that are internally linked together then the game itself could still break, of course. A good example of that is a console-game style 'system save' that unbeknownst to the user might contain hard references to the files holding the individual game saves themselves. If in such a situation you delete only some of those individual files, you might break the game.
I did edit the files and deleted remotecache.vdf, however upon restart, Steam still manages to download the ones on the cloud back onto my ssd.
This has worked for other games, but strangely not for AoE II HD.
It isn't. But storage quotas are per-game anyway.
So, who cares right?
It's not like these hold personal data or anything.
...
At least, I would hope not.
... but then you have (many) games such as Dirt 3, ported from old GFWL which used to manage its saves but does no longer, and that therefore necesitate a user be able to interfere manually to e.g. delete old "profiles", and I do not believe myself anymore.
It's a frustrating mess and I swear around all of it every time I have to do this ♥♥♥♥ manually. Steam should definitely provide for better tools to manage cloud-saves.