Main > Software Forum
LED control from Mame--in over my head again?
1UP:
BTW, Thanks for spending so much time on this, I didn't realize you were spending all day on this. Hope I can get home early enough tonight to check out the other games you worked on.
Howard_Casto:
--- Quote from: 1UP on March 10, 2010, 11:55:30 pm ---BTW, Thanks for spending so much time on this, I didn't realize you were spending all day on this. Hope I can get home early enough tonight to check out the other games you worked on.
--- End quote ---
Well I hadn't planned on it. The problem is when you make progress it's hard to stop.
1UP:
Tell me about it. I end up spending about an hour too long at work every night when I'm making "progress".
1UP:
So I tried a quick othunder test tonight by typing "led0=lws 1 16 %s%" in the test window but no dice. Will this only work with a script? May also be the version of Mame (1.03), I'm not sure when the output system was put into place. In 1.36 I can't even run othunder because it is an outdated rom...
Howard_Casto:
--- Quote from: 1UP on March 11, 2010, 03:53:42 am ---So I tried a quick othunder test tonight by typing "led0=lws 1 16 %s%" in the test window but no dice. Will this only work with a script? May also be the version of Mame (1.03), I'm not sure when the output system was put into place. In 1.36 I can't even run othunder because it is an outdated rom...
--- End quote ---
Not sure when the output system was implemented. You need to elimate the middle man.... the procedure when first writing commands for a game is to always open up the mamehooker debugger window and run the game in windowed mode. This ensures the game in question has outputs hooked up. If that version of mame is older than the output system, the debug window should remain blank the entire time. If you get [mamestart] and [mamestop] messages then the output system is there but the outputs for operation thunderbolt haven't been added yet.
If they were added in after the output system was implemented then the person who did it should be ashamed.... those aren't leds!
I couldn't resist looking a t2 a little more and I think I may have taken a wrong turn. Going into the sound menu makes obvious that all the bits I've hooked up simply create the "track number" for each sound effect to play. It still doesn't explain why they blink in the output test menu though.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version