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
This game seems to be REALLY good at loading all cores, in-fact it's one of the best ones I've seen when it comes to that, along with BeamNG Drive (a driving / crashing / soft-body physics vehicle simulator).
So yeah, get those extra cores, keep them cool and properly fed with power (good power supply and motherboard), don't run out of RAM, and have a decent enough GPU to handle the effects - and you might come out a few FPS ahead.
Or make slightly less big kabooms. That's a whole lot cheaper.
*My PC is 6 years old next month with a 2~2.5 year old GPU in it, and I've doubled the ram up to it's now current amount. I'm sure you can afford something newer than this, but if you run with at-least these specs you'll have a great experience even with half the cores (real cores not E-cores).
...Unless of-course, you have knocked down an entire 5+ story office complex/building involving millions of voxels. Each one to be processed affects the others in some ways, quickly expanding the computations outside of cache memory on the CPU. Thus, things slow, quite a bit actually. So while your mileage may vary, keep kabooms not-so-big if you don't like slowdowns.
e.g. Don't fire 300 exploding pianos at a structure and wonder why things get slow. That's a given.
What's also a given? This game, and what you can do, is awesome.