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've read that and did this:
"If you want to turn Steam cloud saving back on at some point in future then just boot the game, load your save file, undock from the port you're at, and redock in order to save the game. At this point it should be fine to turn cloud saving back on."
Immediately re-corrupts any save.
Still an issue for me
Yes, this is what corrupted saves looks like for me as well
The real corrupted saves as described in the guide in the first post is another issue entirely. If you just have a quarter of your screen filled with sea, your save is not corrupted.
As I said earlier, an easy fix is to not use the "Continue" button, and just load your autosave using the "Load" button and select the file named "Autosave".
No save corrupted or harmed in the process ;)
I see, this makes sense.
Seems like a pretty dumb oversight that the continue button doesn't ignore the .vdf file
According to one of the sticky threads, it was a steam update dating back to December 2020 that added that file during cloud save. Why a simple issue like that hasn't been resolved in several months is beyond me though (either steam changes the way it is done or the game code is altered to load the file named "autosave" and not just the latest file, for example)