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 did have to set the screen to 1920x180x50 Hz to reduce screen tearing. after that the game works just fine,dispite the CPU running at 150% on one core and the GPU pegged at 100%
With this guide, I was able to enjoy building with no lags, and save one of my most advanced city i lost due to some auto-save crash. Thanks.
@Ihetre: I also use Avast but did not have that problem. Possibly something recent. CBA to edit the guide TBH but people using it should be aware that his comment was that Avast aintivirus is flagging the support site link as a threat.
This is not because of the directx api or visual c++ redistributable files, since then almost every game would have this problem.
However in most cases this is because of some roookie mistake. It's basically what you learn in the first few lessons of programming, that you can declare global and local or private and public variables, if you don't use them correctly and keep their values stored the wrong way during the entire game this will end up to grow into a massive amount of ram used, like it does in game. If you use these commands correctly the memory will be flushed when no longer needed, ie the function or subroutine has finished.