Software Support > PowerMAME
PowerMAME - New Derivative Build
boykster:
I think the author of that mod is moving toward a unified ini file.....
gamename,framenumber
That makes a ton more sense IMHO.
Rich
RandyT:
--- Quote from: MYX on February 12, 2006, 09:15:43 pm ---I found this when I was on my quest for knowledge about 49 ways the other day. Kinda of eerie.
--- Quote from: brandon on March 20, 2005, 03:51:50 pm ---well.. maybe RandyT will invent a cheap output board based on the KeyWiz that could be used for driving LEDs, Solonoids(Qbert, T2 recoil), lamps, relays.. etc.. of course you would need something inbetween to change the TTL signal to something with more current or whatever.. but you can find lamp driver board from pinballs and skeeball machine for cheap AFAIK.. in fact I probably have a few mixed with all my junk.. I'm no engineer but I bet Randy could make a USB device like the keywiz but with different firmware that would have all outputs instead of inputs.. of course writting drivers and incorporating it into mame would be a whole different story and perhaps parallel port might be easier.. I dunno.. just tossing out the idea...
--- End quote ---
--- End quote ---
Not as eerie as reading something like that when it's sitting in front of you three quarters finished. Makes me start looking around for hidden cameras ;)
RE: Multiple units
There's still a little bit of head banging to do on this one. From a high level standpoint, the inputs should be virtualized. So hopefully, when talking to the devices directly via Mike's DLL, you would think about addressing output 15 on board 3 like so:
32 x ( [board number] -1) + [output number] = [virtual output number]
or in other words
(32 x (3-1)) + 15 = 79
The actual command language used for creating animations will need to have some additions. Most likely, I will use the same commands currently in use, but will be deciding which board to send commands to, based on the first 3 letters of the command: LWZ for the first device and LW1 through LWF for devices 2 through 16, using HEX for the 3rd character.
Hopefully, most of this is stuff only the programmers will need to worry about :)
RandyT
MikeQ:
--- Quote from: RandyT on February 13, 2006, 08:47:04 pm ---
--- Quote from: MYX on February 12, 2006, 09:15:43 pm ---I found this when I was on my quest for knowledge about 49 ways the other day. Kinda of eerie.
--- Quote from: brandon on March 20, 2005, 03:51:50 pm ---well.. maybe RandyT will invent a cheap output board based on the KeyWiz that could be used for driving LEDs, Solonoids(Qbert, T2 recoil), lamps, relays.. etc.. of course you would need something inbetween to change the TTL signal to something with more current or whatever.. but you can find lamp driver board from pinballs and skeeball machine for cheap AFAIK.. in fact I probably have a few mixed with all my junk.. I'm no engineer but I bet Randy could make a USB device like the keywiz but with different firmware that would have all outputs instead of inputs.. of course writting drivers and incorporating it into mame would be a whole different story and perhaps parallel port might be easier.. I dunno.. just tossing out the idea...
--- End quote ---
--- End quote ---
Not as eerie as reading something like that when it's sitting in front of you three quarters finished. Makes me start looking around for hidden cameras ;)
RE: Multiple units
There's still a little bit of head banging to do on this one. From a high level standpoint, the inputs should be virtualized. So hopefully, when talking to the devices directly via Mike's DLL, you would think about addressing output 15 on board 3 like so:
32 x ( [board number] -1) + [output number] = [virtual output number]
or in other words
(32 x (3-1)) + 15 = 79
The actual command language used for creating animations will need to have some additions. Most likely, I will use the same commands currently in use, but will be deciding which board to send commands to, based on the first 3 letters of the command: LWZ for the first device and LW1 through LWF for devices 2 through 16, using HEX for the 3rd character.
Hopefully, most of this is stuff only the programmers will need to worry about :)
RandyT
--- End quote ---
I think there are 2 aspects to this. I think the users need a GUI that virtualizes. In other words, if you have 2 LED-Wiz's hooked up, the interface shows a single group of 64 LED's number 1-64. A drag and drop interface would be nice but that is another topic.
The user can create a sequence with all available LED's without knowledge of what device they reside on. The instructions that get spit out in the LWA files will not be virtualized. A single "frame" of lighting that spans multiple devices will generate an instruction for each device in the span.
The .DLL will accept the instructions as it does now but convert the LW1, LW2... instructions back into LWZ instructions while also steering them to the appropriate device.
Modified:
Randy, If you can at least define the new language, I can update the .DLL and incorperate it into PowerMAME. This will allow people to at least hand generate LWA files that support multiple devices. If the GUI isn't going to be coming soon this will allow people to at least do it the brute force way.
MYX:
--- Quote from: RandyT on February 13, 2006, 08:47:04 pm ---Not as eerie as reading something like that when it's sitting in front of you three quarters finished. Makes me start looking around for hidden cameras ;)
--- End quote ---
Yes, we are using hidden cameras and you need to stop picking your nose. :P
MYX:
Randy,
If I am right, we loose one channel to gain another board. Is this right?
The GUI could tell the app what is being done. <-- Sorry, Talking out my butt as I have no idea how this stuff works. But, Click a radio button and another 32 LEDs appear in the interface or they were already there and become ungreyed out.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version