安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
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.