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
And yes, I hate when stuff like this happen, in this game or similar other sandbox games. I usually play with autosave disabled so I had my share of this happening when I am in groove and a crash happens after a few hours of work...
That is good practice due to corrupt saves, mistakenly overwritten saves, etc.
Turned out there is a bug. Resume not always resumes your last save but some earlier version.
Happened a few times now.
If you still have depth of field turned on try disabling it since the thing is a buggy pos. My problem is they had to know depth of field was broken and causes all kinds of issues yet they decide to default it to on then compounded that boneheaded decision by defaulting auto save to off...I may have also lost a few hours of time in my city because the default configs were set up by morons.
On the bright side once that's turned off I get my fps stabilized to playable on a 32:9 and it doesn't crash anymore.
Auto save is one of the first features I toggled tho. It's off by default in cs1 too. Missed that for years...
So I noticed that the “Continue” button always defaults to the last Autosave and not the most recent save which is extremely annoying as I initially though I had lost progress as well, but all I had to do was load my latest manual save from the Load menu.