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
Bummer.
if you are worried about unity engine then don't buy any more games that use it but don't preclude common problem solving by immediately cutting to the placement of blame.
And please, don't tell me Unity supports multithreading. On the technical sense, yes it does, but the load distribution is non existent. One core is still sitting at 80% use.
I really wish this engine would stop being used.
"But but no multithreading in Unity!" you might say. Well guess what? It's 2015, and majority of video games are STILL not properly using multi-core support, not just any made in Unity. And it should be obvious why, but with the new generation of consoles out this might start changing soon.
The core issue of the performance in this game is the amount of processing required for the AI. The civilian "traffic" could do with a lot more work, since reducing that has a pretty big impact on the game's performance, where you would think that this would have been an area that was optimized into the ground before game release. Unfortunately looks like game got shipped without having had enough budget for enough spit and polish.
However it's still a problem on large missions with many guards, and you can't lower that.