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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Necessary? No. But if you use workshop, then you could use up more than 64GB of RAM. I loaded someone's city of over 4,000 workshop items and it reached over 50GB. But 90% of it was unused in the game. It was just basically acting as a RAMdisk to hold info in case it needed it. Otherwise, the game was only using a few hundred assets in the game.
But in my game, cities.exe uses 2.5GB of RAM @ 1080p resolution (1920 x 1080), while my main rig uses 4.5GB @ 4k resolution (3840 x 2160). I use no workshop.
http://steamcommunity.com/sharedfiles/filedetails/?id=1089964125
On an average city build though, I use only around 1500 assets and so most of these are disabled and I still have ample RAM available. Unless you're the sort of builder that requires tons and tons of assets and props for intense detailing, then 32GB should be more than adequate and 64GB would be overkill imo.
The only thing that would tempt me to upgrade from 32GB to 64 would not be for gaming purposes but rather as scratch memory space for 3D artwork and rendering.