EPTHow long is a game tick in seconds? - Page 2
| Forum Index > BW General |
|
GroT
Belgium3003 Posts
| ||
|
Taiche
France1963 Posts
On July 16 2005 10:09 exalted wrote: 1 second can't possibly be 23.8 ticks, take for example Terran Infantry Weapons, 266 ticks, would be awesome if it took 11 seconds to complete... The thing is one second is actually equal to around 23.8 ticks. The problem is "time units" in StarEdit aren't ticks  | ||
|
enkera~
Venezuela725 Posts
tick-tick-tick-tick or.. tikcitkicktikvitkivktikcikvitkicktivkcitkitkitkicvkt ?? | ||
|
Never Post
United Kingdom503 Posts
On July 17 2005 12:35 enkera~ wrote: the ticks are like what ? tick-tick-tick-tick or.. tikcitkicktikvitkivktikcikvitkicktivkcitkitkitkicvkt ?? Nah, ticks are those insect things that bite you. | ||
Excalibur_Z
United States12237 Posts
The 24 ticks per second information was gathered from BWChart, which rates actions against the Fastest game speed. Since nobody is capable of performing an action every frame, even with the fastest hotkey cycling in the world, the game speed must be reduced. By bringing the speed down to Slowest and performing massive hotkey cycling, then opening the replay in BWChart (which always assumes 24 ticks per second), the reported APM is greatly inflated, up to a theoretical maximum of 1440 APM. However, in this way, it is possible to view the actions performed on each frame through reading the action log. Unchecking the Seconds box converts all of the time information to ticks, and from there it can be counted that when one second begins, 24 frames appear before the next second. Anyway, tick information is used for cooldowns. Other values, such as build times, are displayed in the editor in seconds. These values assume Normal game speed, which is of course slower than Fastest. That means some calculations must take place to convert a build time as reported in the editor to what actually occurs at Fastest speed. For example, an SCV has a build time of 20 on Normal speed. On Fastest speed, it is closer to 12.5 seconds, thus suggesting that Fastest is approximately 66% faster. So, to summarize: - When discussing cooldowns, divide all values by 24 to determine the actual time in seconds at Fastest speed. - When discussing build times, divide all values by 1.66 to determine the actual time in seconds at Fastest speed. | ||
|
enkera~
Venezuela725 Posts
Excalibur_Z You're GOD | ||
|
Hot77.iEy
Finland1486 Posts
| ||
| ||
