Autofire....

dskys · Post by **dskys** » Thu Jul 10, 2003 3:01 pm

Another post!

Al informed me that according to ANALINP I used autofire on the Inp of Hyper Sports I submitted.

I didn't use it, in fact, I wouldn't know where to start.

I don't know what the little analysing program does, but somehow it decided that autofire had been used...

This is my set up, and while I don't know what happened, being nbew to the site, I'm not ready to be called a cheat yet (I know you didn't Al btw

)

I use a combo of Wingman Action pad and keyboard for Hyper Sports (and others like track and field etc)

On the speed events, I use Ctrl and Shift for the run keys and, if required, a button on the joypad for jump/shoot whatever.

BUT

I do use a cordless keyboard (that's the reason for the joypad - it allows accurate timing - pressing say, Alt, on hyper swimming rarely works when I'm bashing the other two keys like mad).

Rather than pressing the 'run' buttons, I 'wipe' them from side to side. I'm not particularly good at the games but I do get enough speed that way - eg i can easily lift 260kg in WL without too much effort... But its just a technique, and indeed is the one i used back on the real thing 15 or 16 years ago.

Does anyone know a) how to enable autofire (cos I really don't), b) if their cordless stuff causes problems with this auditing software or c) if there's any way to prove i'm not using it?

Cheers

Adi

Chad · Post by **Chad** » Thu Jul 10, 2003 3:06 pm

this is really an autofire/slowdown detection thingy, it means that out of thousands of regualr recordings of human presses yours (along with others that have been provenly detected to use slowdown or autofire techniques) stands out as using something out of the normal. No matter what you say that you did not cheat (everyone says this of course) your recording shows it's not normal, and no you're not superman, people with much faster button presses than yours come clean from this detective process because theire presses are at normal recording speeds and they are not autofiring.

I think really this is only just a speed issue on your machine. Use F11 on wolfmame or tgmame recordings and you can check out the speeds of your own and other's recordings, if yours drop below 90%, you proly need to use auto frameskiping and/or no sound (or get a new computer if they drop below 80%) to speed things up and keep it fair.

Basically all the things that make it easier to play multipleCredits/pausing/extralives/autfoire/slowingDown the game, we frown upon at marp. Even though a lot of players "like" to play this way cause they can get more points or not die as often, that's great for them, but if you want to fairly compare score for score, we have to all play the same.

dskys · Post by **dskys** » Thu Jul 10, 2003 3:11 pm

Thanks for that

will give them a go

Would pausing cause the error?

Chad · Post by **Chad** » Thu Jul 10, 2003 3:14 pm

no, i'm fairly certain pausing wouldn't cause this detection, but thanks for verifying :) we want your INP business but as a competor yourself i'm sure you'll understand that an even playing ground is a good thing.

dskys · Post by **dskys** » Thu Jul 10, 2003 3:22 pm

I agree - but then again, if a piece of software is saying i used a feature i didnt (because i have a lowly athlon 1400 with just 768mb ram) that's a bit bleak tbh

Chad · Post by **Chad** » Thu Jul 10, 2003 4:16 pm

the detection is always up for being proved wrong

, record in wolf/alphamame and we'll see.

dskys · Post by **dskys** » Thu Jul 10, 2003 4:17 pm

i've just d/l a version of alphamame, and once i figure how to get it to record

i'll submit another score

dskys · Post by **dskys** » Thu Jul 10, 2003 4:20 pm

and sound screws up on my pc, cos the psu cant handle the graphics card and my soundcard at once, so i use the onboard sound - if i pause for a split second then unpause it fixes the prob (and pause is working in alphamame

)

help

Chad · Post by **Chad** » Thu Jul 10, 2003 4:41 pm

oh yeah you can pause mame with out the P, but it'll still be detected sort of in alphamame :) but any pauses at the begining of the game are going to be ignored cause the emu initialization always causes some pause times anyways, so you're probably safe if you need(?) to do that for sound correction.

dskys · Post by **dskys** » Thu Jul 10, 2003 4:46 pm

cool ! it doesn't let me pause when recording... it doesn't let me use the joypad either.... i know i'm prolly anal cos im new, but please helpppppppp

Chad · Post by **Chad** » Thu Jul 10, 2003 4:52 pm

it's all good, we're here to help. if you use the mame32 you proly just need to enable joystick, or if your using the command line use the -joystick option.

dskys · Post by **dskys** » Thu Jul 10, 2003 4:54 pm

i know im a pain, but (im using cl version) can you put what i'm supposed to type

atm, to record, i'm doing 'alphamame game -record filename'

(and i didn't realise there was a gui one

)

thanks lots

Chad · Post by **Chad** » Thu Jul 10, 2003 5:02 pm

yeah forget i said there was gui one :) if you're not into that that is.

alphamame game -record filename -joystick

and any other cli options you want after that. and don't forget to del nvram/game.nv before recording, hope that works.

dskys · Post by **dskys** » Thu Jul 10, 2003 5:04 pm

thank you

edited: but now my times are craaaaaapppppp - what's the diff between alpha and mame .66?

Chad · Post by **Chad** » Thu Jul 10, 2003 5:25 pm

basically none with a few enhancement attempts to make recording semi-secure, i wouldn't doubt there is a speed difference but the difference would not be noticble to the naked eye, especially if you are on a fast computer, maybe try disabling some background processies? p2p software is mostly the culprit, some are good some are cpu hogs.