安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
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.