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










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 ♥♥♥♥♥♥♥ 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.