These recordings I would like to request further review - they're close to autofire or slowdown - but not enough for me to DQ by myself.

phl's exctscca, exctsccr, exctsccb - these have low %'s - but the others have no percentage at all

pz's elim2

nm's exerionb & exerion

ra's elevatob

vaz's eswatbl

djk's espiale

jms's empcity - he's usually a fast shooter, but I'm not sure of him being this fast... average difference on bit 11 of this recording is just over 3 I think.

Just wondering... but did analinp 2o get released? I only have 2N - and I remember seeing an average shooting frame difference for a bit on the chat channel once...

Thanks for reading. GB9

-- Anonymous, August 16, 2000

Answers

First of all, there of course is no general rule on what is a low percentage and what isn't. It depends on a lot of things. I have to admit that I usually give people who have not been caught (yet) on slowdown the benefit of the doubt in case their recording is in this grey area, whereas if this recording (so with the same statistics) had been done by someone who had several recordings disqualified already, I might disqualify it. Biased? Yes. Dangerous? Yes. But I think it's the correct decision most of the time anyway.

> phl's exctscca, exctsccr, exctsccb - these have low %'s - but the others have no percentage at all

Yes, the averages aren't low, but the percentage of frames of length 1 and 2 is a lot higher than those of Renzo and even (gulp!) German. Combined with Phil's "reputition", yes, I'd disqualify these.

> pz's elim2 Here's another good example of why general rules don't apply. This game is a vector game running at 40 fps. His average fire may last for only 3.08 frames, but, translated to a 60 fps game, that would make it 4.62 frames... . It doesn't even take a fast presser to get a figure like that... . I suggest that we always check what the default fps for a game is, because even 53 fps may make some statistics acceptable that would not have been accepted at 60 fps...

> nm's exerionb & exerion

Too much slowdown, IMO.

> ra's elevatob

Grey area. I might have given someone else the benefit of the doubt, but not Ray Atkinson and not on Elevator Action. Slow computers have a lot of trouble with this game as I know from experience from when Deca2000 started and I didn't have my fast machine yet. In addition, I have recently disqualified one of Ray's recordings on another clone of Elevator Action. I'd disqualify this one too.

> vaz's eswatbl I have had some interesting chats with Vaz. At some point he was "bragging" at how fast he fired on one of his recordings. I looked at the statistics and wasn't really impressed. I know several people who are significantly faster. So he may be fast, but he's not that fast. Furthermore, he may have a nice machine, but he also has the habit of listening to MP3s on that same machine while playing games... . In this particular case, I'd say that his game was slowed down too much.

> djk's espiale Way too slow. I have not tried this game myself, but I know that Dave has a 200 MHz Pentium-MMX...

> jms's empcity Here is someone whom I'd give the benefit of the doubt where I might have disqualified the recording if done by someone else. Just to make sure, though, I tried this game myself a few times, and analysed my own recording once I had gotten a bit familiar with the game. Here's my fire button:

Bit  11, length   1:      2 (  0.46%)
Bit  11, length   2:     15 (  3.46%)
Bit  11, length   3:    184 ( 42.40%)
Bit  11, length   4:    220 ( 50.69%)
Bit  11, length   5:     12 (  2.76%)
Bit  11, length   6:      1 (  0.23%)
Bit  11, length >10:     21
Bit  11, average length (in number of frames): 3.53

The game ran at a very solid 100% ALL the time. Bubble's average on this game is 3.28. Very close to my number. If you accept mine, then you should also accept his, IMO.

> Just wondering... but did analinp 2o get released? I only have 2N - and I remember seeing an average shooting frame difference for a bit on the chat channel once...

Yes, I made some slight updates, but I think it was too little to warrant a new release. If you really want it, of course either Chad or I can compile a version and send it to you. There's one more thing I want to add and that's the total number of state changes in InpHisto. That tells us how often a certain button was pressed and released during the recording and when compared to the total number of frames in a recording, or the total number of state changes in other people's recordings, I think this might be useful information.

Cheers, Ben Jos.

-- Anonymous, August 27, 2000

"reputition"? Heh, I meant "reputation", of course.

Cheers, Ben Jos.

-- Anonymous, August 27, 2000