The NEW Build Your Own Arcade Controls
Main => Software Forum => Topic started by: jhonny_d on December 10, 2016, 09:44:31 am
-
Hello, I tried to follow the tutorial but can't get Mamehooker to register any output.
I'm on win10, mame64 161b (so that should exclude any issues with the output that arised with 170), here's what I'm doing:
-Load up mamehhoker, setup the mame path, enable alerts and tts
-Load mame, open digdug rev2, insert credit
-Nothing is registered by mamehooker
Any advice is appreciated :)
-
Hello, I tried to follow the tutorial but can't get Mamehooker to register any output.
I'm on win10, mame64 161b (so that should exclude any issues with the output that arised with 170), here's what I'm doing:
-Load up mamehhoker, setup the mame path, enable alerts and tts
-Load mame, open digdug rev2, insert credit
-Nothing is registered by mamehooker
Any advice is appreciated :)
Read the sticky Users of Mamehooker, LEDWiz, LedBlinky and Similar apps Please Read!
http://forum.arcadecontrols.com/index.php/topic,151464.0.html (http://forum.arcadecontrols.com/index.php/topic,151464.0.html)
-
already did, that's why I'm trying with 161b
-
Fwiw, I'm using mame 0180 with the output=windows setting and LEDBlinky is working great with game outputs like blinking start buttons.
-
@millercentral, thanks, apparently this did the trick, I assumed that if I used an older mame ver I would be fine withou changing the ini
edit: now I just need a kind soul who will add recoil output to Point Blank 1 :D
-
I have having trouble with the second monitor marquee option of Mamehooker. Upgraded from 0.146 to 0.181 and initially I noticed in the mamehooker Debug window that Mamehooker was not seeing the rom loaded and then I saw this post and made the (output windows) edit to mame.ini and I can now see where Mamehooker sees the rom currently loaded but I am still not getting the marquee .png to show up on second monitor.
Steve
-
Fixed it....I had grabbed a newer version of mamehooker from the web this morning that for whatever reason was the culprit...went back to my previous version and made the output windows fix mentioned and I am good to go again.