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








If you got couple of them active near you (about 200 tiles around you) - you will have an additional CPU load. So, if you feel unacceptable lag for you - reduce an amount of turrets, make the game lighter by lower your display settings such as texture resolution, upgrade your PC or just stop using them for now until PZ will receive a global performance optimization.
I noticed you call getGameTime():getRealworldSecondsSinceLastUpdate() a few times in AT_TurretUpdate function.
I'd like to recommend setting this at the top of AT_AngryTurretsServerUpdate:
local gameTime
local timeSinceLastUpdate = 0
Events.OnGameTimeLoaded.Add(function()
gameTime = GameTime.getInstance()
end)
Then in DoZTurretJob() you could just add
timeSinceLastUpdate = gameTime:getMultipliedSecondsSinceLastUpdate()
And in AT_TurretUpdate() you could update reloadtime and aimingtime according to that value instead :)
That way you you will not only call the java function only once, but even the time will be reused during the tick, all the turrets will go through timeSinceLastUpdate each tick anyway so it will not get "out of date" during runtime.
Also MultipliedSeconds takes into accound game-speed!
Thank you for your time and I hope you get this.