Front End Support > MaLa Frontend
MaLa Plugin - LEDBlinky (v1.0.1 UPDATE)
arzoo:
--- Quote from: headkaze on March 13, 2007, 06:15:21 am ---It was quite a mission to change my plugin to do the same sort of thing so I appreciate the work involved in doing this. I changed mine so you could set up your controls the easy way (by control name) with the option of assigning them to keys if you wanted custom mappings. You might want to consider going this way arzoo (or not I just liked the idea of having both ways). This also supports colors.ini which I don't think the other one does yet. Nice work arzoo :)
Adding speech is relatively easy, do it in a thread and use WaitForSingleObject(). I posted about my findings in the other Mala plugin thread. Check it out if you want to add speech.
--- End quote ---
Thanks headkaze! I'll probably add speech eventually, but first I need to focus on the attract mode animations.
--- Quote from: Silver on March 13, 2007, 06:49:03 am ---Right ok thanks for clearing that up.....
So if you re-map buttons from game to game, thats what LEDBlinky was designed for, but for just using a standard layout, LEDwiz plugin?
PS arzoo - Are ALL your buttons RGB? How many LedWiz's?!!?
--- End quote ---
Silver,
The LEDBlinky will work fine for standard layouts also. The only real downside is that it's a bit more complicated to initially configure. But I've gone to great lengths to create config apps for doing this - you don't ever have to manually edit any files. I've also included detailed documentation. :)
No, the player 3 and 4 buttons and the trackball buttons are just plain old blue :(. The cost of this cp just kept going up and up, so I decided to cut back. Now I kind of regret not doing them all with EI buttons. So far I have 2 LED-Wizs. I'll need a third if I add any more EI's!
Silver:
Ok thanks.
For the sake of my curious mind, if LEDBlinky plug-in maps the hardware by input codes (KEYCODE_A, KEYCODE_LSHIFT, MOUSECODE_1_ANALOG_X...) Then what does the other plugin map the hardware to?
loadman:
--- Quote from: Silver on March 13, 2007, 08:21:33 am ---Ok thanks.
For the sake of my curious mind, if LEDBlinky plug-in maps the hardware by input codes (KEYCODE_A, KEYCODE_LSHIFT, MOUSECODE_1_ANALOG_X...) Then what does the other plugin map the hardware to?
--- End quote ---
It maps to the plug-in config file. This file is created with the nice config ap Edge has produced.
What a day or two and all will be clear after release.... ;)
arzoo:
--- Quote from: Silver on March 13, 2007, 08:21:33 am ---For the sake of my curious mind, if LEDBlinky plug-in maps the hardware by input codes (KEYCODE_A, KEYCODE_LSHIFT, MOUSECODE_1_ANALOG_X...) Then what does the other plugin map the hardware to?
--- End quote ---
Here's kinda how things work. When a MAME game is started, we have a list of control codes used by that game - Player 1 Button 1, Player 1 Button 2, Player 1 Joystick, etc. MAME then maps these controls to input codes - A, X, Left Shift, Joystick Up, etc. So here's how the two plug-ins differ:
LEDWiz
Game --> Control Code --> LED
LEDBlinky
Game --> Control Code --> Input Code --> LED
This is a very simplified example and as loadman has said, he's about to release a new version. Loadman, please correct me if I've misstated the basics here.
edge:
The LEDWiz Plugin:
- Goal was to keep it as simple as possible, with as many features as possible. :)
- This is meant for most control panels out there, where most of your games are mapped the same way. Ie, Player 1 Button 1 is usually on your top row of buttons, first position. Player 1 Button 2 is top row, second position. Etc...
- If in some of your games you remap your buttons (as hk mentioned for NeoGeo)... you can always create specific game overrides.
- Yo ucan also create default lighting for other emulators besides mame. So, for instance, you can create an atari2600 config to light when playing atari2600 games.
LEDBlinky:
- The power of arzoo's plugin is if you have different control mappings for many different games... and if you also like to change mappings on the fly.
- Instead of mapping buttons to controls in control.ini, it reads the actual mame input codes to figure out which button to light.
- (arzoo - please correct me if I am wrong)
In the end, both can be used for all panels. I suggest trying both to see which matches your control panel and mappings the best.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version