Main > Software Forum

Mame Hooker 2.0 Released!

(1/5) > >>

Howard_Casto:
Same bat time, same bat channel, the link in my footer should take you to the homepage with all the info. 

The big news is the new dde interface.  It means applications other than mame can send commands to mamehooker. This can be done with either a direct interface (for developers) or by launching mamehooker again with command-line options, which will be sent to the already running mamehooker.  If you are a emulator or front-end developer and would like to add support for mamehooker, which automatically gives you support for all the various devices mamehooker can control, please contact me. 


More on this release as the week goes on, including where to get display files for the artwork system.

brock.sampson:
I'm having problems with display files.  I'm running mame on my primary monitor and then displaying the image files on a secondary monitor.  Secondary monitor is configured to be above the primary.  When I start mamehook and then mame the image is displayed at the size in the dis file 1024x768.  On subsequent loads of the same game only a portion of the image is shown.  I also tried testing without starting mame just testing within mamehook.  I get the same results full size on first load and then only a portion on subsequent loads.

gt2k.dis
[Layout]
x=0
y=-768
width=1024
height=768
image=gt2k.jpg

gt2k.ini
[General]
MameStart=lds gt2k
MameStop=

Any ideas what the problem might be?

Howard_Casto:
Yeah, it's an unresolved rendering bug.  I seems to work ok on my display now though.  The cause is mame messing with the video display as the lds command is executed, corrupting the display.  Reducing your screen resolution should help.  Also you can try sticking a wait command before the lds command.


The lds command should be working fine without mame.  My guess is you've made a super-huge dis file and it's having trouble loading in time.

hulkster:
i may be the only one....but what the heck is mamehooker?!   :dunno  i went to your site and you talk about the release....but dont really describe what it is.  im guessing its some kind of FE developer type thing?  so um....what is it?

brock.sampson:
Quoting Howard, quoting the readme.

Overview
========
Arcade games have always had outputs.  Lights, sirens, motors, solenids scoreboards or what have you, cabinets have always had ways to interact with the player.  Until recently, mame had all but ignored this, with flashing keyboard lights as our only source of output.  Thankfully, Aaron Giles built us a whole new output system last summer, that allows mame to relay the states of various outputs to any windows application.  Unfortunately, knowing the state doesn't magically make a device fire, thus the need for this app.  Mame Hooker keeps track of outputs and uses their state to control several output devices including, but not limited to the keyboard leds, ledwiz, the parallel port and force feedback controllers.  More devices will be added as the project progresses.

Navigation

[0] Message Index

[#] Next page

Go to full version