Main > Software Forum
My official MAME output wip thread.
milhouse:
I'm a little confused. I have MalaHooker up and running with my LedWiz (controlling a Q*Bert knocker). Now I am trying to get force feedback controllers (Direct Input) working. Do I need a separate controller to read the MameHooker output and control the motors? Or is it built-in to 142 roms?
Thanks.
Howard_Casto:
I think if you would read isamu's question and my reply which is literally just above what you posted, you would get your answer. ;)
milhouse:
I did, but since its not working for me, I wanted to make sure I had everything I needed. Thanks.
Howard_Casto:
Well I still don't have a clue what you are asking.
Obviously for force feedback to work you must have a controller (gamepad, joystick ect...) that supports force feedback. The "show supported devices" option in the mamehooker menu will let you know if it's supported. I have no clue what you mean about "142 roms". The mame driver must have feedback hooked up to an output and the ones that do are prety much the ones listed in this wip.
Howard_Casto:
I'm having bouts with insomnia again, so my loss of sleep is your gain!
I'm looking at the outrun driver that hasn't been submitted yet. Everything is in working order, but I have to alter it before I submit it for a couple of reasons.
1. The outrun driver has changed since I wrote this, so I'll have to alter it slightly to get it working.
2. The mame devs decided that we should handle the giant case statements of outputs differently, and I tend to agree.
They altered my last submission before approving it last spring and I'm going over the changes. What they did was create two generic callbacks, one for each byte and then make custom init functions for each game with outputs. In their individual inits, the various games re-direct the generic callback to a specific one for each game, which transforms a giant case statement for 12 games into 12 tiny functions.
Outrun.c only had a few games in the driver so it shouldn't take long. I just want to make sure that I fully understand what they did (memory managment is crazy to wrap your head around sometimes) before I start work. We should get the outrun.c at least, out before the next build cycle if all goes well.
Then I want to put up a tutorial on the mamehooker website about how to actually use this stuff. Those of you who have sent me vids/pics of your cabs running, if you want to make a little writeup of what you did (both software-wise and hardware-wise) then please do so and I'll put it on the site.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version