Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Later, between 'Properties' and 'InGame', the base game sets up the city. That is quite unoptimized and uses lots of RAM if your city is large. Most importantly, it does not allow screen refreshing, so you'll see a sudden bump when it is over.
For some people who push their computer too hard, the observed pause may take 10 minutes or more. But the computer is not really pausing, it's setting up the city.
I don't know what causes the connection with buildings you are seeing. Anything custom asset related should show up very rapidly after custom assets are loaded. Also, if you repeat the same steps, starting from the desktop, you should see pretty much the same memory usage every time. Not exactly the same but pretty much the same.
It is worth checking if you have any Exceptions or Errors in your output_log.txt. Those might explain the differences between loads.