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'll check back in with this game after the first patch.
I've had a save file corrupt already, but looking at the memory log from that time-stamp, I can see what caused it, and it wasn't something easily replicated, but otherwise... the file still exists..
Crash simulator
Not everyone wants autosaves enabled, in heavy sandbox games like this I always play with them disabled.
Not just due to performance issues - lag spikes - but also freezes, and occasionally, crashes and even save corruption, depending on what you were doing when the game decided to autosave.
I agree.
The first thing I ALWAYS do before starting to play any game, is addressing the settings.
Not only to check the save settings, but all other possible "good to know" settings.
Particular with graphics settings regarding motion blur, etc.
I run through all available things in there as a service to myself to not get annoyed from
the get go, because I know that I will have to go in there eventually.
I don't know, it's just an automatic thing my brain requires me to do.