Timer doesn't start immediately!?

[blue626]

I noticed that, when you start a Time Trial, the timer only shows 1 second after showing "Go!", starting at 0:00 and changing to 0:01 only 1 sec. later. Viridian can move immediately after showing "Go!". Because of that, the scores show 1 sec. less (Example: if you do in 1:30, it says you did it in 1:29). This happens in v.2.0 and (I think so) in v.1.2. Was this made on purpose?

[Hilbert]

If you look a most stopwatches with millisec. counters you have to wait until the millisec. count reaches 100 before a second has passed. therfore 129 should be correct
we can lock the thread now.

[blue626]

I don't understand your post. Are you saying that stopwatches say 1:28,034 when they should say 1:29,034? Anyway, I'll try to explain better:
Viridian can move in the sec. before the timer appears at 0:00. So, the timer should say 0:01 when it says 0:00, 0:02 when it says 0:01, ... , 1:30 when it says 1:29.

[Hilbert]

Bad at explaining...
1 second is 100 milliseconds. When 100 milliseconds have passed, a second has passed.    Can move at 1 millisecond. The timer doesn't show milliseconds, though.

[blue626]

I thought 1 sec. were 1000 milliseconds... Were you thinking of a hundredth of a second?
You mean that moves 1 pixel in each 0,01 seconds? Anyway, the timer only appears 1 sec. after Viridian starts moving, so while Viridian has moved 1 sec., the timer says 0:00; while Viridian has moved 1,5 sec., the timer says 0:00; while Viridian has moved 3 sec. the timer says 0:02, and if Viridian has moved 2:16,9 sec. the timer says 2:15. In the last examples, consider that Viridian never stopped. The timer says 1 sec. less (or more, since the timer doesn't have tenths of a sec., in the last example it says less 1,9 secs.) than the time it should say.
Perhaps I didn't understand your post, again.

EDIT: Do you mean that Viridian only moves 0,01 sec. after I press the arrow key? In that case, the timer is right when 1:18,00 secs have passed since "Go!" showed, because it will show 1:17 and has moved for 1:17,99 secs; but, it's right only when  has moved for ... ,99 secs.

[Hilbert]

Uhh... I give on explaining...

[blue626]

I don't understand your last post.
Do you understand what I said on my last post?

[Hilbert]

No.
The timer should include 100ths of a second.

[blue626]

I concord. It is a good idea, but perhaps tenths of a sec. is enough.
I hope that someone understands my posts above .

[FIQ]

What blue626 means is that Viridian starts *before* the timer even show 0:00, i.e. he starts at -0:01. Thus, there are 2s, not just 1, before the timer reaches 0:01.

[blue626]

What blue626 means is that Viridian starts *before* the timer even show 0:00, i.e. he starts at -0:01.

Yes, that's what I tried to say.

Thus, there are 2s, not just 1, before the timer reaches 0:01.

But, the timer should start at 0:00 (and at the same time as "Go!" appears), shouldn't it?