Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: Generic Eric on April 14, 2014, 10:27:13 am

Title: Capturing changes on the screen
Post by: Generic Eric on April 14, 2014, 10:27:13 am
I'm trying to get a better idea of how to implement mamehooker.  Say I wanted a LED to flash the underside of my control panel or part of my marquee when the k.o. was flashing, could mamehooker make that happen?
Title: Re: Capturing changes on the screen
Post by: Howard_Casto on April 14, 2014, 12:35:21 pm
Uh you've got to be a bit more specific man.  What game?  If it doesn't have outputs then no, it won't work.  Mamehooker isn't a hack, it interfaces to mame's official output system. 
Title: Re: Capturing changes on the screen
Post by: Generic Eric on April 14, 2014, 12:41:19 pm
Uh you've got to be a bit more specific man.  What game?  If it doesn't have outputs then no, it won't work.  Mamehooker isn't a hack, it interfaces to mame's official output system.

Sure.  I thought I mentioned punchout in my previous post.  I'm going to give your mamehooker a go after work this week. 
Title: Re: Capturing changes on the screen
Post by: Vigo on April 14, 2014, 01:08:33 pm
Autohotkey might be able to help with custom lighting. Similiar to what Nitz and Le Chuck put together for joystick autoswitch to 4 way on the Tron light cycles stage. Have a script that will trigger every time K.O. is onscreen.

http://forum.arcadecontrols.com/index.php/topic,117395.msg1243777.html#msg1243777 (http://forum.arcadecontrols.com/index.php/topic,117395.msg1243777.html#msg1243777)





Title: Re: Capturing changes on the screen
Post by: BadMouth on April 14, 2014, 03:06:30 pm
1. Did the original arcade machine have an output for such a thing?
2. Is the output hooked up in MAME?

Title: Re: Capturing changes on the screen
Post by: Howard_Casto on April 14, 2014, 07:10:49 pm
No it didn't, so no it won't work. 

That being said, troubleshooter 2 might do it.  You can use the output sections only, so you'd have to fire up cheat engine or something similar and determine the byte where the KO variable is stored, hook that to an output and use the broadcast outputs option to send it along to mamehooker.  Just remember that memory locations are rather temperamental, so if you ever upgrade your mame version your are likely to have to search for the byte all over again.