Username:
B
I
U
S
"
url
img
#
code
sup
sub
font
size
color
smiley
embarassed
thumbsup
happy
Huh?
Angry
Roll Eyes
Undecided
Lips Sealed
Kiss
Cry
Grin
Wink
Tongue
Shocked
Cheesy
Smiley
Sad
1 page
--
--
List results:
Search options:
Use \ before commas in usernames
I am indifferent towards YABB
.. I posted over this on the General board, but I guess that was the wrong place for it...

Would it help / make things easier if other people timed the runs?

Already the site has other people verifying runs - why not timing as well if it would help? As long as all the constraints were agreed upon, everyone should come up with (very) similar times.

What about something like the following...

1) When the runner submits a run, he also must submit (what he believes to be) the official time (arrived at using Virtual Dub, and agreed upon start/end points). Which Radix keeps a secret.

2) Somebody volunteers to time the run, and does so using Virtual Dub and the same agreed upon start/end points. 

3) Once reported back, if the times are (nearly) identical, it's a fairly safe bet that that time is accurate.

If the times do NOT match both times are kept secret, and one more person volunteers to time the run with the same criteria as above. 99.9% chance that time will be (nearly) identical to one of the two previous timings - and that one will be taken as accurate.

Only if all three times are significantly different would Radix have to intervene and sort stuff out.

It'd take a little more co-ordination, but seems to me like it would save Radix some stress, as well as help move the queue along quicker. Timing a very long game with many segments just isn't a fun thing to have to do over and over again.

Thoughts?
Thread title:  
Quote:
.. I posted over this on the General board, but I guess that was the wrong place for it...

Would it help / make things easier if other people timed the runs?

Already the site has other people verifying runs - why not timing as well if it would help? As long as all the constraints were agreed upon, everyone should come up with (very) similar times.

What about something like the following...

1) When the runner submits a run, he also must submit (what he believes to be) the official time (arrived at using Virtual Dub, and agreed upon start/end points). Which Radix keeps a secret.

2) Somebody volunteers to time the run, and does so using Virtual Dub and the same agreed upon start/end points.  

3) Once reported back, if the times are (nearly) identical, it's a fairly safe bet that that time is accurate.

If the times do NOT match both times are kept secret, and one more person volunteers to time the run with the same criteria as above. 99.9% chance that time will be (nearly) identical to one of the two previous timings - and that one will be taken as accurate.

Only if all three times are significantly different would Radix have to intervene and sort stuff out.

It'd take a little more co-ordination, but seems to me like it would save Radix some stress, as well as help move the queue along quicker. Timing a very long game with many segments just isn't a fun thing to have to do over and over again.

Thoughts?


Accomplices.

The one word reason why it's probably refused! Tongue
I am indifferent towards YABB
Quote:

Accomplices.

The one word reason why it's probably refused! Tongue


Well sure. But isn't the risk the same for people who verify the runs?

If they can trust a person enough to check whether or not cheating is going on, surely it wouldn't be a leap to let them time it as well.
The main Problem is that those files have to be sent anyway. I remember that when I decided to help Radix (which, looking back at it, probably wasn't much help after all) some time ago, getting the runs to me usually took longer than the verification and timing process.

One thing to note about the timing process is that for pretty much most games, the only things that matter are the starting and ending frames of timing for each segment. If there are clearly set starting/ending points, then the runner himself could submit these frames, and the verficator could do the same, and Radix would only have to further investigate those frames that are not the same. However, I'm not sure how much help this would be after all.