Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
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.