安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
0.566 is the limit because of two reasons.
0.5 ensures that 30 hz is skipped every second. It skips half the first update then half the second update. This puts the total delay at 0 seconds.
If you use 1, it would normally skip one full update then fire, however now it is skipping one, firing, then skipping another and firing again, putting the delay at 0.5 seconds.
If you use 2, it skips both updates then fires, putting the delay at 1 second.
Etc, etc.
0.066 ensures another 33 ms of time is skipped per update, in case any frame dependent actions are being taken.
So, for example if I want to take a timer with a .1 delay and fix it, then I have to use the following formula:
0.1 * 2 + 0.566 = 0.766.
But the really fucking annoying part is that some things have parent timers, so you have to figure out what the parent timer is. Changes to any timer underneath the parent work normally, the parent is the one that updates per tick.
For AI behaviors, it's the perception timers.
For AI attacks, they use the difficulty scales.
It is very, very complicated.
The jackal leg thing is just because the jackal's legs don't have collision. That's not a bug, it's actually just the case for every character before Reach.