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
You don't need to build anything to affect performance. All checks are run in case you did build something.
CPU isn't affected, stay at about 30-40% on my 4 Core/8 Threads Core i7 @ 4 GHz.
Looks like calculations are limited to one thread, multithreading support would bring a huge performance bump on most systems :-)
More than that, what causes performance problems is the custom pathfinding which is run by the CPU and it's multithreaded. :)
I dont think rendering times are the problem, its most probably pathfinding as you stated. I would expect CPU load going up if pathfinding is the limiting factor and implementation is multithreaded?
That being said, anything that eats CPU will make matters worse; the next T++ release will solve a lot of those issues as it's waaay faster than the current version.