After looking at Game Guru's detatwin recording, it showed up that he had both fire buttons mapped to one key. Personally, I don't think it would give him any particular unfair advantage, although it certainly would seem to be intentional.

Here's the partial output:

detatwin.inp inside db_detatwin_840600_m37b8.zip -Clean
---Output from Tool Analyse Inp---
Analinp Version 2q



--------  analinp Report  --------
p = 3  f = 4 
Bit#   frames:on/off Presses BPresses Bursts highVar LowVar Speed%
p = 10 f = 9 
Bit#   frames:on/off Presses BPresses Bursts highVar LowVar Speed%
  10   20971/32248      2762      381     24    0.42  0.380   9.1%
  11   20971/32248      2762      381     24    0.42  0.380   9.1%



C:\MAME\INP\Tmp\detatwin.inp



WARNING: there was more than one fire button mapped to the SAME key.
--------  End Of analinp Report  --------




Number of frames in this recording:   53219




--------  InpHisto Report  --------
Bit  10, length  1  :      6 (  0.12%)      5 (  0.19%)      1 (  0.04%)
Bit  10, length  2  :     48 (  0.94%)     40 (  1.52%)      8 (  0.33%)
Bit  10, length  3  :    422 (  8.27%)    356 ( 13.48%)     66 (  2.68%)
Bit  10, length  4  :   1642 ( 32.20%)   1223 ( 46.33%)    419 ( 17.03%)
Bit  10, length  5  :   1638 ( 32.12%)    740 ( 28.03%)    898 ( 36.50%)
Bit  10, length  6  :    951 ( 18.65%)    196 (  7.42%)    755 ( 30.69%)
Bit  10, length  7  :    305 (  5.98%)     59 (  2.23%)    246 ( 10.00%)
Bit  10, length  8  :     66 (  1.29%)     13 (  0.49%)     53 (  2.15%)
Bit  10, length  9  :     12 (  0.24%)      5 (  0.19%)      7 (  0.28%)
Bit  10, length 10  :     10 (  0.20%)      3 (  0.11%)      7 (  0.28%)
Bit  10, length 11+ :    425              122              303
Bit  10, all lengths:   5525             2762             2763
Bit  10, average lengths:       4.84             4.36             5.36



Bit  11, length  1  :      6 (  0.12%)      5 (  0.19%)      1 (  0.04%)
Bit  11, length  2  :     48 (  0.94%)     40 (  1.52%)      8 (  0.33%)
Bit  11, length  3  :    422 (  8.27%)    356 ( 13.48%)     66 (  2.68%)
Bit  11, length  4  :   1642 ( 32.20%)   1223 ( 46.33%)    419 ( 17.03%)
Bit  11, length  5  :   1638 ( 32.12%)    740 ( 28.03%)    898 ( 36.50%)
Bit  11, length  6  :    951 ( 18.65%)    196 (  7.42%)    755 ( 30.69%)
Bit  11, length  7  :    305 (  5.98%)     59 (  2.23%)    246 ( 10.00%)
Bit  11, length  8  :     66 (  1.29%)     13 (  0.49%)     53 (  2.15%)
Bit  11, length  9  :     12 (  0.24%)      5 (  0.19%)      7 (  0.28%)
Bit  11, length 10  :     10 (  0.20%)      3 (  0.11%)      7 (  0.28%)
Bit  11, length 11+ :    425              122              303
Bit  11, all lengths:   5525             2762             2763
Bit  11, average lengths:       4.84             4.36             5.36

-- snip --

Upon checking the MAME source, bits 10 and 11 correspond to Button 1 and Button 2.

Anyway, does any other editor have a problem with this? Worthy of DQ? Or not? I tend to think not, but I'm sorta sitting on the fence on this one.

-- Anonymous, August 04, 2001

Answers

I personally would dq it, but it is required to check the mame version guru used to record it and do a test recording to check if the same thing happens to the inp when recording normally. sometimes mame mapps the keys automatically to each other for certain games...

-- Anonymous, August 04, 2001