Main > Software Forum
LED control from Mame--in over my head again?
Howard_Casto:
Just wanted to give a quick update. I tired RevX with my force feedback controller just to see if it was the debug window not being able to keep up and thankfully it was! The gun fires properly. One thing that seems odd to me is that when you insert a coin and ONLY when you insert a coin, the gun for the coin slot you used rumbles once. Is that how the arcade game did???
Anyway, I'll have to install a more robust debugger in mamehooker to figure out terminator 2 as it's now apparent that my debug window is too slow to keep up. Hopefully this will lead to the answers we are looking for.
1UP:
Really cool. I had no desire to play RevX before but now I'll have to. Its been awhile since I've recompiled Mame so I'll have to browse the docs a bit so I can try out all this stuff.
smalltownguy:
--- Quote from: Howard_Casto on March 11, 2010, 08:34:03 pm ---Just wanted to give a quick update. I tired RevX with my force feedback controller just to see if it was the debug window not being able to keep up and thankfully it was! The gun fires properly. One thing that seems odd to me is that when you insert a coin and ONLY when you insert a coin, the gun for the coin slot you used rumbles once. Is that how the arcade game did???
Anyway, I'll have to install a more robust debugger in mamehooker to figure out terminator 2 as it's now apparent that my debug window is too slow to keep up. Hopefully this will lead to the answers we are looking for.
--- End quote ---
Yes, as I recall the Rev X guns would rumble when you coined up.
1UP:
Finally got newer roms for these games, will have to test this over the weekend. So far I'm not seeing anything in the debug. But I'm sleep deprived and probably doing something wrong.
Howard_Casto:
Again, I'm not messing with the source atm, but I wanted to let you guys know the best way to write a script for operation wolf/ operation thunderbolt
Since the outputs for these games are always on/ always off, you might want to put some strobing in there depending upon your output device. I had to test to make sure mamehooker was fast enough to work and that the driver updates the state quickly enough but, anyway.....
In the command simply make one action switch the device with the %s% tag and then immediately turn it off again with a ","
For example, on my xinput device I use the command:
motor0=xip 1 %s%,xip 1 0
The state is refreshed every frame, so the script is constantly re-loaded, meaning there isn't a need for a loop.
Now this is a little weak for my 360 controller and it uses an offset motor for rumble anyway, so you'd just keep it on, BUT if you were hooking it up to a kickback solenoid this would be just right.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version