How long is a tick?

[Guessmyname]

For a rather time-sensitive script I'm doing.

How long is a tick? If my memory serves me correctly, a sleep [1000]; command in a script would make it wait for an exact second. Is that correct?

[KDR_11k]

NO! [] multiplies the value with 161200 or so, a sleep [1] would take forever to resolve. Sleep 1000 supposedly sleeps for 1000 milliseconds but I'm not sure if that's really accurate. In case it's not you can tell a part to turn by n at speed 1 (remember, <> multiplies by 182) and wait-for-turn.

[jcnossen]

A tick is 1/30 second.

[KDR_11k]

So how long does a sleep 1000 wait, 1000 milliseconds or 1000 ticks?

[Bobcatben]

A tick is 1/30 second.

hasn't seemed that way to me with my experimentation with groupai's

[SinbadEV]

I thoughght it was something like 30/32 seconds per tic (0.9375 seconds a tic)... but I'm not sure either...

[jcnossen]

I thoughght it was something like 30/32 seconds per tic (0.9375 seconds a tic)... but I'm not sure either...

Well I am, it's 1/30 sec in game time.

[AF]

A second ingame is 30 frames. However the slowupdate is every 32 frames, which means some stuff is updated every 32 frames, for example the GUI resource stats, aka thats where caydrs magic number comes from (30/32)

[jcnossen]

Still, sleep doesn't have anything to do with SlowUpdate IIRC.. the cob interpreter is updated every tick.

[Argh]

So, therefore, if you want something to move EXACTLY 1 unit over 5 ticks... then it needs to move 0.2 per tick, and 5 ticks will be almost exactly 0.1666666 seconds. The only problem with this is that if we want things to be exact times, we're going to have to settle for a lot've rounding, but the tiny difference in the end won't be noticable except under very long durations of time, and if everything is kept in strict lockstep... no big deal. The really hard part, as I've been finding lately, is how to keep everything in true lockstep.

[Molloy]

There are 50,000 tics in the Core Calendar year.