Apparently Hisa-Chan has challenged...greenspun.com : LUSENET : MARP Editors : One Thread |
My comment - followed by Hisa-Chan's comment...[Claimed 5,310,900 but used autofire/slowdown. Must use MAME 35 TG 3 to reinstate. GB9] I did not use autofire(same as others). Turn to DQ after submitted at once is very unfair. I have nothing to say to make the rule force to use the version which does not apply playstation controller,but if DQed by this reason,you had better DQ all other recordings. if MARP does fair competiton. anysome, I am not interested in poor recordings now... GB9,if you can do,delete all recordings from your site not one but all.
And now the checking procedure.
kod.inp inside 7nt_kod_5310900_m37b4.zip -Clean ---Output from Tool Chad's Analyse Inp(-i -s)--- Analinp Version 2o-------- analinp Report -------- p = 3 f = 4 Bit# frames:on/off Presses BPresses Bursts highVar LowVar Speed% 75 74043/205343 24502 339 103 0.41 0.409 5.0% p = 10 f = 9 Bit# frames:on/off Presses BPresses Bursts highVar LowVar Speed% 75 74043/205343 24502 16770 664 0.61 1.330 52.5% 78 32357/247029 936 10 1 0.69 0.400 12.9% 79 53329/226057 1585 22 2 1.02 1.074 14.3%
C:\ARCADE\INP\CHECKERS\Tmp\kod.inp -------- End Of analinp Report --------
Number of frames in this recording: 279386
-------- InpHisto Report -------- Bit 11, length 5 : 1 (100.00%) 1 (100.00%) 0 ( 0.00%) Bit 11, length 11+ : 2 0 2 Bit 11, all lengths: 3 1 2 Bit 11, average lengths: 5.00 5.00 0.00
Bit 15, length 6 : 1 (100.00%) 1 (100.00%) 0 ( 0.00%) Bit 15, length 11+ : 2 0 2 Bit 15, all lengths: 3 1 2 Bit 15, average lengths: 6.00 6.00 0.00
Bit 74, length 1 : 11 ( 3.01%) 10 ( 2.89%) 1 ( 5.26%) Bit 74, length 2 : 26 ( 7.12%) 26 ( 7.51%) 0 ( 0.00%) Bit 74, length 3 : 88 ( 24.11%) 86 ( 24.86%) 2 ( 10.53%) Bit 74, length 4 : 123 ( 33.70%) 118 ( 34.10%) 5 ( 26.32%) Bit 74, length 5 : 52 ( 14.25%) 49 ( 14.16%) 3 ( 15.79%) Bit 74, length 6 : 38 ( 10.41%) 35 ( 10.12%) 3 ( 15.79%) Bit 74, length 7 : 21 ( 5.75%) 17 ( 4.91%) 4 ( 21.05%) Bit 74, length 8 : 4 ( 1.10%) 3 ( 0.87%) 1 ( 5.26%) Bit 74, length 9 : 2 ( 0.55%) 2 ( 0.58%) 0 ( 0.00%) Bit 74, length 11+ : 524 98 426 Bit 74, all lengths: 889 444 445 Bit 74, average lengths: 4.12 4.07 5.05
Bit 75, length 1 : 6149 ( 13.02%) 1920 ( 7.88%) 4229 ( 18.50%) Bit 75, length 2 : 11905 ( 25.21%) 6192 ( 25.40%) 5713 ( 25.00%) Bit 75, length 3 : 16817 ( 35.61%) 10903 ( 44.73%) 5914 ( 25.88%) Bit 75, length 4 : 8764 ( 18.56%) 4203 ( 17.24%) 4561 ( 19.96%) Bit 75, length 5 : 2004 ( 4.24%) 578 ( 2.37%) 1426 ( 6.24%) Bit 75, length 6 : 703 ( 1.49%) 163 ( 0.67%) 540 ( 2.36%) Bit 75, length 7 : 438 ( 0.93%) 197 ( 0.81%) 241 ( 1.05%) Bit 75, length 8 : 317 ( 0.67%) 186 ( 0.76%) 131 ( 0.57%) Bit 75, length 9 : 81 ( 0.17%) 28 ( 0.11%) 53 ( 0.23%) Bit 75, length 10 : 51 ( 0.11%) 4 ( 0.02%) 47 ( 0.21%) Bit 75, length 11+ : 1776 128 1648 Bit 75, all lengths: 49005 24502 24503 Bit 75, average lengths: 2.89 2.91 2.87
Bit 76, length 1 : 27 ( 3.41%) 26 ( 4.08%) 1 ( 0.65%) Bit 76, length 2 : 44 ( 5.56%) 44 ( 6.91%) 0 ( 0.00%) Bit 76, length 3 : 50 ( 6.32%) 44 ( 6.91%) 6 ( 3.90%) Bit 76, length 4 : 83 ( 10.49%) 72 ( 11.30%) 11 ( 7.14%) Bit 76, length 5 : 136 ( 17.19%) 113 ( 17.74%) 23 ( 14.94%) Bit 76, length 6 : 133 ( 16.81%) 108 ( 16.95%) 25 ( 16.23%) Bit 76, length 7 : 115 ( 14.54%) 86 ( 13.50%) 29 ( 18.83%) Bit 76, length 8 : 77 ( 9.73%) 58 ( 9.11%) 19 ( 12.34%) Bit 76, length 9 : 70 ( 8.85%) 49 ( 7.69%) 21 ( 13.64%) Bit 76, length 10 : 56 ( 7.08%) 37 ( 5.81%) 19 ( 12.34%) Bit 76, length 11+ : 2456 986 1470 Bit 76, all lengths: 3247 1623 1624 Bit 76, average lengths: 5.92 5.69 6.90
Bit 77, length 1 : 26 ( 2.36%) 23 ( 2.93%) 3 ( 0.95%) Bit 77, length 2 : 67 ( 6.09%) 66 ( 8.41%) 1 ( 0.32%) Bit 77, length 3 : 119 ( 10.82%) 110 ( 14.01%) 9 ( 2.86%) Bit 77, length 4 : 156 ( 14.18%) 110 ( 14.01%) 46 ( 14.60%) Bit 77, length 5 : 153 ( 13.91%) 98 ( 12.48%) 55 ( 17.46%) Bit 77, length 6 : 155 ( 14.09%) 97 ( 12.36%) 58 ( 18.41%) Bit 77, length 7 : 160 ( 14.55%) 102 ( 12.99%) 58 ( 18.41%) Bit 77, length 8 : 101 ( 9.18%) 67 ( 8.54%) 34 ( 10.79%) Bit 77, length 9 : 88 ( 8.00%) 58 ( 7.39%) 30 ( 9.52%) Bit 77, length 10 : 75 ( 6.82%) 54 ( 6.88%) 21 ( 6.67%) Bit 77, length 11+ : 2573 1051 1522 Bit 77, all lengths: 3673 1836 1837 Bit 77, average lengths: 5.73 5.49 6.34
Bit 78, length 1 : 29 ( 5.12%) 28 ( 7.98%) 1 ( 0.47%) Bit 78, length 2 : 52 ( 9.19%) 44 ( 12.54%) 8 ( 3.72%) Bit 78, length 3 : 83 ( 14.66%) 69 ( 19.66%) 14 ( 6.51%) Bit 78, length 4 : 119 ( 21.02%) 72 ( 20.51%) 47 ( 21.86%) Bit 78, length 5 : 102 ( 18.02%) 39 ( 11.11%) 63 ( 29.30%) Bit 78, length 6 : 69 ( 12.19%) 27 ( 7.69%) 42 ( 19.53%) Bit 78, length 7 : 46 ( 8.13%) 20 ( 5.70%) 26 ( 12.09%) Bit 78, length 8 : 31 ( 5.48%) 23 ( 6.55%) 8 ( 3.72%) Bit 78, length 9 : 21 ( 3.71%) 16 ( 4.56%) 5 ( 2.33%) Bit 78, length 10 : 14 ( 2.47%) 13 ( 3.70%) 1 ( 0.47%) Bit 78, length 11+ : 1307 585 722 Bit 78, all lengths: 1873 936 937 Bit 78, average lengths: 4.74 4.46 5.19
Bit 79, length 1 : 19 ( 1.93%) 17 ( 2.57%) 2 ( 0.62%) Bit 79, length 2 : 63 ( 6.39%) 57 ( 8.62%) 6 ( 1.85%) Bit 79, length 3 : 130 ( 13.18%) 114 ( 17.25%) 16 ( 4.92%) Bit 79, length 4 : 181 ( 18.36%) 125 ( 18.91%) 56 ( 17.23%) Bit 79, length 5 : 128 ( 12.98%) 67 ( 10.14%) 61 ( 18.77%) Bit 79, length 6 : 155 ( 15.72%) 89 ( 13.46%) 66 ( 20.31%) Bit 79, length 7 : 120 ( 12.17%) 73 ( 11.04%) 47 ( 14.46%) Bit 79, length 8 : 86 ( 8.72%) 60 ( 9.08%) 26 ( 8.00%) Bit 79, length 9 : 60 ( 6.09%) 33 ( 4.99%) 27 ( 8.31%) Bit 79, length 10 : 44 ( 4.46%) 26 ( 3.93%) 18 ( 5.54%) Bit 79, length 11+ : 2185 924 1261 Bit 79, all lengths: 3171 1585 1586 Bit 79, average lengths: 5.41 5.13 5.99
-------- End Of InpHisto Report --------
Don't you dare tell me he isn't using slowdown at least... all in favor of re-disqualifing the score and force the re-instatement by using of MAME 35 TG 3 will signify by saying "aye". All opposed will say "no". Of course, debate as you will :)
I vote aye. GB9
-- Anonymous, April 29, 2001
Oh.. that's what benjos's message was about - well I added a very stern message and re-dqed the score. In addition, I told him to use WIN 37 beta 9 TG 2... it's the best I can do.He's obviously testing my leadership AND my patience... probably the patience of several others as well... GB9
-- Anonymous, April 29, 2001
He may have a point about not being able to use the playstation controller on mame35tg stuff, so i don't want to force him to record a mame35 one. I would say aye to forcing a win37tg2 recording.It's funny he's saying delete all his recordings, where did we hear this before...
I still think if he's so damn good, you think he could use the keyboard for one single game and play lame like the rest of us just to make a m35tg3 recording.
-- Anonymous, April 29, 2001
Well, I just tried playing this and concentrating on trying to deliberately press the fire button as quickly as possible in true track 'n field style. I left the joystick alone and just concentrated on playing the game at 100% speed via frameskip and this was the result:Bit 75, length 1 : 26 ( 5.74%) 17 ( 7.42%) 9 ( 4.02%) Bit 75, length 2 : 82 ( 18.10%) 54 ( 23.58%) 28 ( 12.50%) Bit 75, length 3 : 94 ( 20.75%) 49 ( 21.40%) 45 ( 20.09%) Bit 75, length 4 : 129 ( 28.48%) 65 ( 28.38%) 64 ( 28.57%) Bit 75, length 5 : 74 ( 16.34%) 29 ( 12.66%) 45 ( 20.09%) Bit 75, length 6 : 35 ( 7.73%) 9 ( 3.93%) 26 ( 11.61%) Bit 75, length 7 : 7 ( 1.55%) 3 ( 1.31%) 4 ( 1.79%) Bit 75, length 8 : 2 ( 0.44%) 0 ( 0.00%) 2 ( 0.89%) Bit 75, length 9 : 2 ( 0.44%) 2 ( 0.87%) 0 ( 0.00%) Bit 75, length 10 : 2 ( 0.44%) 1 ( 0.44%) 1 ( 0.45%) Bit 75, length 11+ : 14 4 10 Bit 75, all lengths: 467 233 234 Bit 75, average lengths: 3.69 3.41 3.98
I then tried it again with frameskip = 0 and my machine not freshly rebooted which gave me around 48% of original game speed and this was the result:
Bit 75, length 1 : 220 ( 59.46%) 141 ( 75.81%) 79 ( 42.93%) Bit 75, length 2 : 135 ( 36.49%) 42 ( 22.58%) 93 ( 50.54%) Bit 75, length 3 : 3 ( 0.81%) 1 ( 0.54%) 2 ( 1.09%) Bit 75, length 4 : 5 ( 1.35%) 1 ( 0.54%) 4 ( 2.17%) Bit 75, length 5 : 2 ( 0.54%) 0 ( 0.00%) 2 ( 1.09%) Bit 75, length 6 : 2 ( 0.54%) 0 ( 0.00%) 2 ( 1.09%) Bit 75, length 7 : 2 ( 0.54%) 1 ( 0.54%) 1 ( 0.54%) Bit 75, length 10 : 1 ( 0.27%) 0 ( 0.00%) 1 ( 0.54%) Bit 75, length 11+ : 5 1 4 Bit 75, all lengths: 375 187 188 Bit 75, average lengths: 1.53 1.28 1.77
Then lastly, I tried it with frameskipping set to 80% of original game speed and the results were:
Bit 75, length 1 : 24 ( 6.58%) 20 ( 10.87%) 4 ( 2.21%) Bit 75, length 2 : 90 ( 24.66%) 58 ( 31.52%) 32 ( 17.68%) Bit 75, length 3 : 132 ( 36.16%) 65 ( 35.33%) 67 ( 37.02%) Bit 75, length 4 : 107 ( 29.32%) 38 ( 20.65%) 69 ( 38.12%) Bit 75, length 5 : 6 ( 1.64%) 0 ( 0.00%) 6 ( 3.31%) Bit 75, length 6 : 1 ( 0.27%) 1 ( 0.54%) 0 ( 0.00%) Bit 75, length 8 : 2 ( 0.55%) 0 ( 0.00%) 2 ( 1.10%) Bit 75, length 9 : 2 ( 0.55%) 1 ( 0.54%) 1 ( 0.55%) Bit 75, length 10 : 1 ( 0.27%) 1 ( 0.54%) 0 ( 0.00%) Bit 75, length 11+ : 4 0 4 Bit 75, all lengths: 369 184 185 Bit 75, average lengths: 3.04 2.76 3.31
So, given that I was playing only for a short time to keep my bursts up as much as possible and given the rate I had to fire at to get close to Hisa's speed even at 80% of game rate I do not believe he could have achieved this fire rate for that number of shots over that length of time without either severe slowdown or some form of auto- fire on his joystick.
In my opinion this was a fair cop guv'na - but of course I'm new to this inp analysis stuff.
BeeJay.
PS: My hand's and fingers are still sore from trying to get the maximum possible speed out of my firing finger even for such a short period.
-- Anonymous, May 01, 2001
I was about to go to bed (yes, I know, relatively early for once) when I saw a new upload by Hisa-Chan on kod, this time using win37b9tg2 (7nt_kod_4292100_win37b9.zip). I decided to quickly write a program to do a quick speed check. More analysis is required, because we still want to know if he apparently really can press that fast at the correct speed. That part is easy, though, since I can easily convert his .inp to regular win37b9 format. I really have to go to bed now, so that part will have to wait until tomorrow.Oh, and while writing my little program, I noticed a minor bug in analinp. So tomorrow, I'll also update analinp to version 2p. I had been meaning to put a more detailed speed analysis into analinp (the same as the last part of the analysis that follows), so this is a good time to do that and fix that little bug.
Here's the speed stuff:
Input file: "..\kod.inp" 141 good frames (average speed: 100%) 108 fast frames (average speed: 278%) 576 good frames (average speed: 100%) 12 slow frames (average speed: 81%) 6240 good frames (average speed: 100%) 24 slow frames (average speed: 86%) 14232 good frames (average speed: 100%) 12 slow frames (average speed: 87%) 15156 good frames (average speed: 100%) 24 slow frames (average speed: 85%) 36 good frames (average speed: 100%) 12 slow frames (average speed: 85%) 60 good frames (average speed: 98%) 12 slow frames (average speed: 88%) 72432 good frames (average speed: 100%) 36 slow frames (average speed: 80%) 6048 good frames (average speed: 100%) 12 slow frames (average speed: 67%) 16200 good frames (average speed: 100%) 12 slow frames (average speed: 88%) 19248 good frames (average speed: 100%) 12 slow frames (average speed: 84%) 624 good frames (average speed: 100%) 24 slow frames (average speed: 77%) 36 good frames (average speed: 100%) 12 slow frames (average speed: 88%) 6576 good frames (average speed: 100%) 12 slow frames (average speed: 82%) 17736 good frames (average speed: 100%) 12 slow frames (average speed: 87%) 4560 good frames (average speed: 100%) 36 slow frames (average speed: 72%) 4128 good frames (average speed: 100%) 12 slow frames (average speed: 89%) 252 good frames (average speed: 100%) 12 slow frames (average speed: 89%) 444 good frames (average speed: 100%) 24 slow frames (average speed: 78%) 25848 good frames (average speed: 100%) 12 slow frames (average speed: 88%) 28068 good frames (average speed: 100%) 3432 fast frames (average speed: 274%) 1008 good frames (average speed: 100%) 12 slow frames (average speed: 73%) 136 good frames (average speed: 99%)Good frames : 239785 (average speed: 100%) Slow frames : 336 (average speed: 81%) Fast frames : 3540 (average speed: 274%)
Total frames: 243661 (average speed: 102%)
67%: 24 times 71%: 12 times 73%: 12 times 74%: 12 times 77%: 24 times 78%: 12 times 79%: 24 times 80%: 12 times 81%: 12 times 82%: 36 times 84%: 24 times 85%: 12 times 87%: 48 times 88%: 48 times 89%: 24 times 90%: 24 times 91%: 36 times 92%: 60 times 93%: 72 times 94%: 60 times 95%: 36 times 96%: 84 times 97%: 132 times 98%: 288 times 99%: 600 times 100%: 238393 times 120%: 12 times 123%: 12 times 133%: 12 times 197%: 12 times 241%: 12 times 242%: 12 times 244%: 12 times 249%: 12 times 250%: 12 times 252%: 24 times 253%: 12 times 254%: 48 times 255%: 60 times 256%: 84 times 257%: 84 times 258%: 180 times 259%: 84 times 260%: 192 times 261%: 108 times 262%: 96 times 263%: 48 times 264%: 24 times 265%: 36 times 266%: 24 times 267%: 12 times 268%: 12 times 270%: 24 times 271%: 48 times 272%: 36 times 273%: 36 times 274%: 72 times 275%: 24 times 276%: 60 times 277%: 48 times 278%: 36 times 279%: 84 times 280%: 144 times 281%: 132 times 282%: 48 times 283%: 108 times 284%: 132 times 285%: 120 times 286%: 216 times 287%: 156 times 288%: 204 times 289%: 120 times 290%: 96 times 291%: 96 times 292%: 36 times 293%: 36 times 294%: 48 times 295%: 36 times 296%: 24 times 308%: 12 times 310%: 12 times 312%: 24 times 314%: 24 times 315%: 12 times
Cheers, Ben Jos.
-- Anonymous, May 02, 2001
Thanks for staying awake a few more minutes! Speeds look good and also look unaltered (un evenly distributed), unless he made a recording previously and copied the speed bits to the submited inp. The high speeds seem very strange but win37tg2 might be more acruate than m35tg3 was. Still won't know for sure until mamete but this is pretty convincing. I can't wait till Ben does the speed analyis by adding 37tg2 readabilty to analinp.Another thing in Hisa's favor is that he records many inps in a row quickly, if you are using slow down or pausing your recording time would be much longer than the actuall play time. This of course can be faked too with timestamping but it's consistant with Hisa.
-- Anonymous, May 02, 2001
I see nothing wrong with his speed either. The only thing I noticed is that he does not have any 101%, 102%, 103%, and so on. For quite a while already, for all the recordings I have analysed, I had MarpFE configured to use two programs. The second program shows all the speeds and numbers of occurrences and such a lot more detailedly (is that a word?). Usually, if the speed drops to 99% for a few frames, you'll see those frames immediately followed by a few frames of 101%. 98% is followed by 102%, etc., and this does not happen here. My guess is that his computer has a little bit of trouble with this game, which can also be seen by the occasional speed drops. So the computer tries to catch up but can't. Bottom line: No, there's nothing wrong with the speed.The high speeds, of course, are him using F10 at the start and end of the game. This is interesting, because, assuming he had sound on (wasn't this the game in which he loved the music?), others could do the same thing using the same version of MAME, and that way we could get a pretty accurate estimate of what kind of computer he is using.
As for adding support for win37b9tg2 to analinp (or, rather: to my InpReader class), I am not planning on doing that. Not because I'm stubborn (well, I am, but that's not important right now), but because I don't think I can add support for that format quickly. I'd have to take another look at my InpReader class first to be sure, but, at this point, if I am going to do some non-trivial MAME-related coding, I'd rather spend that time on MAMETE.
Anyway, I've converted Hisa-Chan's .inp to regular win37b9 format and analysed it with "good old 2o". In addition, I've taken the time to look up the meanings of all the bits in this game:
11: P1 start 12: Coin 1 73: P1 B3 74: P1 B2 75: P1 B1 76: P1 U 77: P1 D 78: P1 L 79: P1 RAnd here's the remainder of the analysis of his recording:
Analinp Version 2o-------- analinp Report -------- p = 3 f = 4 Bit# frames:on/off Presses BPresses Bursts highVar LowVar Speed% 73 56643/187018 19660 142 45 0.38 0.369 4.0% 75 56643/187018 19660 142 45 0.38 0.369 4.0% 77 37010/206651 1773 5 1 0.56 0.000 40.0% p = 10 f = 9 Bit# frames:on/off Presses BPresses Bursts highVar LowVar Speed% 73 56643/187018 19660 15025 426 0.44 1.008 53.7% 75 56643/187018 19660 15025 426 0.44 1.008 53.7% 76 38455/205206 1605 10 1 0.44 0.410 18.6% 77 37010/206651 1773 25 2 0.63 0.253 45.7% 79 57918/185743 1426 11 1 0.20 0.331 15.6%
kod.inp
WARNING: there was more than one fire button mapped to the SAME key. -------- End Of analinp Report --------
Number of frames in this recording: 243661
-------- InpHisto Report -------- Bit 11, length 4 : 1 (100.00%) 1 (100.00%) 0 ( 0.00%) Bit 11, length 11+ : 2 0 2 Bit 11, all lengths: 3 1 2 Bit 11, average lengths: 4.00 4.00 0.00
Bit 15, length 6 : 1 (100.00%) 1 (100.00%) 0 ( 0.00%) Bit 15, length 11+ : 2 0 2 Bit 15, all lengths: 3 1 2 Bit 15, average lengths: 6.00 6.00 0.00
Bit 73, length 1 : 3325 ( 8.81%) 1254 ( 6.42%) 2071 ( 11.37%) Bit 73, length 2 : 12055 ( 31.92%) 5973 ( 30.56%) 6082 ( 33.38%) Bit 73, length 3 : 14760 ( 39.09%) 9626 ( 49.25%) 5134 ( 28.18%) Bit 73, length 4 : 5953 ( 15.76%) 2384 ( 12.20%) 3569 ( 19.59%) Bit 73, length 5 : 1212 ( 3.21%) 223 ( 1.14%) 989 ( 5.43%) Bit 73, length 6 : 206 ( 0.55%) 48 ( 0.25%) 158 ( 0.87%) Bit 73, length 7 : 120 ( 0.32%) 18 ( 0.09%) 102 ( 0.56%) Bit 73, length 8 : 65 ( 0.17%) 8 ( 0.04%) 57 ( 0.31%) Bit 73, length 9 : 50 ( 0.13%) 7 ( 0.04%) 43 ( 0.24%) Bit 73, length 10 : 16 ( 0.04%) 3 ( 0.02%) 13 ( 0.07%) Bit 73, length 11+ : 1559 116 1443 Bit 73, all lengths: 39321 19660 19661 Bit 73, average lengths: 2.78 2.73 2.83
Bit 74, length 1 : 10 ( 3.82%) 9 ( 3.60%) 1 ( 8.33%) Bit 74, length 2 : 12 ( 4.58%) 12 ( 4.80%) 0 ( 0.00%) Bit 74, length 3 : 60 ( 22.90%) 60 ( 24.00%) 0 ( 0.00%) Bit 74, length 4 : 56 ( 21.37%) 56 ( 22.40%) 0 ( 0.00%) Bit 74, length 5 : 41 ( 15.65%) 38 ( 15.20%) 3 ( 25.00%) Bit 74, length 6 : 51 ( 19.47%) 47 ( 18.80%) 4 ( 33.33%) Bit 74, length 7 : 19 ( 7.25%) 19 ( 7.60%) 0 ( 0.00%) Bit 74, length 8 : 8 ( 3.05%) 5 ( 2.00%) 3 ( 25.00%) Bit 74, length 9 : 4 ( 1.53%) 3 ( 1.20%) 1 ( 8.33%) Bit 74, length 10 : 1 ( 0.38%) 1 ( 0.40%) 0 ( 0.00%) Bit 74, length 11+ : 411 86 325 Bit 74, all lengths: 673 336 337 Bit 74, average lengths: 4.55 4.48 6.08
Bit 75, length 1 : 3325 ( 8.81%) 1254 ( 6.42%) 2071 ( 11.37%) Bit 75, length 2 : 12055 ( 31.92%) 5973 ( 30.56%) 6082 ( 33.38%) Bit 75, length 3 : 14760 ( 39.09%) 9626 ( 49.25%) 5134 ( 28.18%) Bit 75, length 4 : 5953 ( 15.76%) 2384 ( 12.20%) 3569 ( 19.59%) Bit 75, length 5 : 1212 ( 3.21%) 223 ( 1.14%) 989 ( 5.43%) Bit 75, length 6 : 206 ( 0.55%) 48 ( 0.25%) 158 ( 0.87%) Bit 75, length 7 : 120 ( 0.32%) 18 ( 0.09%) 102 ( 0.56%) Bit 75, length 8 : 65 ( 0.17%) 8 ( 0.04%) 57 ( 0.31%) Bit 75, length 9 : 50 ( 0.13%) 7 ( 0.04%) 43 ( 0.24%) Bit 75, length 10 : 16 ( 0.04%) 3 ( 0.02%) 13 ( 0.07%) Bit 75, length 11+ : 1559 116 1443 Bit 75, all lengths: 39321 19660 19661 Bit 75, average lengths: 2.78 2.73 2.83
Bit 76, length 1 : 25 ( 2.88%) 24 ( 3.67%) 1 ( 0.47%) Bit 76, length 2 : 64 ( 7.37%) 61 ( 9.33%) 3 ( 1.40%) Bit 76, length 3 : 96 ( 11.06%) 91 ( 13.91%) 5 ( 2.34%) Bit 76, length 4 : 96 ( 11.06%) 85 ( 13.00%) 11 ( 5.14%) Bit 76, length 5 : 155 ( 17.86%) 99 ( 15.14%) 56 ( 26.17%) Bit 76, length 6 : 161 ( 18.55%) 111 ( 16.97%) 50 ( 23.36%) Bit 76, length 7 : 90 ( 10.37%) 69 ( 10.55%) 21 ( 9.81%) Bit 76, length 8 : 62 ( 7.14%) 41 ( 6.27%) 21 ( 9.81%) Bit 76, length 9 : 64 ( 7.37%) 41 ( 6.27%) 23 ( 10.75%) Bit 76, length 10 : 55 ( 6.34%) 32 ( 4.89%) 23 ( 10.75%) Bit 76, length 11+ : 2343 951 1392 Bit 76, all lengths: 3211 1605 1606 Bit 76, average lengths: 5.55 5.23 6.53
Bit 77, length 1 : 40 ( 3.66%) 26 ( 3.33%) 14 ( 4.47%) Bit 77, length 2 : 87 ( 7.96%) 85 ( 10.90%) 2 ( 0.64%) Bit 77, length 3 : 105 ( 9.61%) 96 ( 12.31%) 9 ( 2.88%) Bit 77, length 4 : 154 ( 14.09%) 131 ( 16.79%) 23 ( 7.35%) Bit 77, length 5 : 187 ( 17.11%) 132 ( 16.92%) 55 ( 17.57%) Bit 77, length 6 : 168 ( 15.37%) 96 ( 12.31%) 72 ( 23.00%) Bit 77, length 7 : 123 ( 11.25%) 69 ( 8.85%) 54 ( 17.25%) Bit 77, length 8 : 95 ( 8.69%) 62 ( 7.95%) 33 ( 10.54%) Bit 77, length 9 : 68 ( 6.22%) 41 ( 5.26%) 27 ( 8.63%) Bit 77, length 10 : 66 ( 6.04%) 42 ( 5.38%) 24 ( 7.67%) Bit 77, length 11+ : 2454 993 1461 Bit 77, all lengths: 3547 1773 1774 Bit 77, average lengths: 5.47 5.14 6.29
Bit 78, length 1 : 13 ( 2.83%) 13 ( 4.39%) 0 ( 0.00%) Bit 78, length 2 : 29 ( 6.32%) 26 ( 8.78%) 3 ( 1.84%) Bit 78, length 3 : 60 ( 13.07%) 49 ( 16.55%) 11 ( 6.75%) Bit 78, length 4 : 85 ( 18.52%) 50 ( 16.89%) 35 ( 21.47%) Bit 78, length 5 : 100 ( 21.79%) 53 ( 17.91%) 47 ( 28.83%) Bit 78, length 6 : 61 ( 13.29%) 30 ( 10.14%) 31 ( 19.02%) Bit 78, length 7 : 39 ( 8.50%) 25 ( 8.45%) 14 ( 8.59%) Bit 78, length 8 : 24 ( 5.23%) 12 ( 4.05%) 12 ( 7.36%) Bit 78, length 9 : 26 ( 5.66%) 21 ( 7.09%) 5 ( 3.07%) Bit 78, length 10 : 22 ( 4.79%) 17 ( 5.74%) 5 ( 3.07%) Bit 78, length 11+ : 1454 660 794 Bit 78, all lengths: 1913 956 957 Bit 78, average lengths: 5.18 5.02 5.45
Bit 79, length 1 : 18 ( 2.38%) 18 ( 3.27%) 0 ( 0.00%) Bit 79, length 2 : 53 ( 7.02%) 46 ( 8.35%) 7 ( 3.43%) Bit 79, length 3 : 75 ( 9.93%) 62 ( 11.25%) 13 ( 6.37%) Bit 79, length 4 : 105 ( 13.91%) 85 ( 15.43%) 20 ( 9.80%) Bit 79, length 5 : 139 ( 18.41%) 95 ( 17.24%) 44 ( 21.57%) Bit 79, length 6 : 88 ( 11.66%) 61 ( 11.07%) 27 ( 13.24%) Bit 79, length 7 : 76 ( 10.07%) 50 ( 9.07%) 26 ( 12.75%) Bit 79, length 8 : 90 ( 11.92%) 62 ( 11.25%) 28 ( 13.73%) Bit 79, length 9 : 52 ( 6.89%) 37 ( 6.72%) 15 ( 7.35%) Bit 79, length 10 : 59 ( 7.81%) 35 ( 6.35%) 24 ( 11.76%) Bit 79, length 11+ : 2098 875 1223 Bit 79, all lengths: 2853 1426 1427 Bit 79, average lengths: 5.70 5.46 6.35
-------- End Of InpHisto Report --------
Time to get back to work. Just wanted to do this quickly because I was curious myself.
Cheers, Ben Jos.
-- Anonymous, May 02, 2001
Oops... made a typo... "Coin 1" is bit 15, not bit 12.Cheers, Ben Jos.
-- Anonymous, May 02, 2001
Interesting about the P1 B1 and P1 B3 mapped to the same key, This is normally a side effect of certain emulated games. But indeed he shows the same extra ordinary quick frame counts with no reported slow down.There are still two possibliities of cheating besides hisa (0) knowing how to fake a tg recording. (1) Having a variably timed autofirer, rare but possible for people who are really interested in cheating (I don't think Hisa is). (2) japanese computer chips having a different ticks per second so the emulator would record a certain time would have passed when really a multiple of that time had passed, still very unlikely. I wonder what under-clocking the cpu will do to a mamete recording.
i'm sure mamete will be out soon enough that adding win37btg2 support to analinp will be uneccesary, there'll be enough work getting a similar analinp working for mamete i'm sure. I really wish I could help Ben Jos with this. but It's still awfull nice for him to take that responsibility.
-- Anonymous, May 02, 2001
Well, P1 B1 and P1 B3 weren't mapped to the same key in his previous recording. Is button 3 even used in this game? Either way, I think it's the result of remapping only the keys you need. On the games I play with keyboard, I remap up, down, left, right to W, X, A, D. Now, A and D are by default controls for player 2. If I don't take the effort to remap those player 2 controls (I usually do), then analinp would also show that warning on my recordings, even though I don't use player 2. I think it's no big deal when one key is mapped to several controls. In most cases, it would even be disadvantageous to do so. Just imagine playing a game where one key is mapped to both up and right...Cheers, Ben Jos.
-- Anonymous, May 02, 2001
Hmmmm, I remember back on my trusty C=64 having a variable speed autofire joystick. Actually, it was rather nice as it was button operated rather than switch operated so you could use it when required without having to try to get a hard to slide switch moved like most of the Quickshot etc joysticks had. :)BeeJay.
-- Anonymous, May 02, 2001
right, it doesn't help you to map A key to up and down. I think analinp only warns if the buttons pressed in bursts are mapped to the same keys. It could be advantageous to map A key to fire and bomb, these were keys he was firing with. But i don't think there is a bomb or "special weapon" fire in this game. probbaly a side effect of win37 on this game, and his previous recordings had an older mame version.
-- Anonymous, May 02, 2001