Main > Software Forum
LEDBlinky - Arcade LED Control software and Animation Editor - v8.2
arzoo:
--- Quote from: wolfsoft on May 28, 2009, 03:22:55 am ---But I have a little problem with the emulator mess.
I want to set default button lights for each emulator.
eg I use mess for vectrex, atari 800, atari 5200
is there a way to set default buttons for each mess emulator
default for all atari 800 games via mess one button
default for all vectrex games via mess four buttons?
--- End quote ---
I think with mess you'll need to create a separate batch file for each emulator (vectrex.bat, atari800.bat, etc.). The batch files will need to accept the mess parameters and then launch the mess exe (mess32.exe %1). Then from mala you'll pass the params to the batch file. This way LEDBlinky will use the batch file name as the emulator and you can then specify unique controls for each actual emulator.
csa3d:
Arzoo:
Just some feedback tonight on getting Nestopia hooked up to Mala and Ledblinky. Because Nestopia runs a windows menubar, you cannot use the default MAME mappings for Left Control, Left Alt buttons, as it activates Nestopia's menus. Thus, I've gone ahead and created an emulator remapping for this one emulator. This resolves the menu bar issue, but to make this work, you need to upload this new keyset to the ipac when that emulator is selected via Mala. Thus far, Nestopia is the only emulator on a different key mapping.
There are a few issues here. Led Blinky appears to map lighted buttons for Other Emulators based on the current keyset loaded into my ipac, and defined in the main mapping. At this time, I do not remember if I had to go back to the master port mappings and add two bogus entries, just so Led Blinky thought I had extra key bindings available for assignment.
Upon selecting a NES game, Mala will eventually upload that keyset to the ipac, but NOT BEFORE led blinky looks to see what keys are currently mapped to what. What this means is that when setting up the "other emulator" in Led Blinky, what you are really doing is setting up the emulator button handles to be whatever default keys those buttons WERE before the ipac key remapping happens. If you do not anticipate the key change, and assign your 'other emulator' buttons with the keys they eventually WON'T be, then Led Blinky will not know how to correctly light up your buttons. (Does this make sense?) Checking the "always light this button" didn't seem to light the button at all, despite the fact that I really don't give a rat's :censored: if my other emulator never turns any buttons on or off.
I found setting up an Other Emulator while changing key mappyings to my ipac quite confusing. I really wasn't sure where to change data for quite some time, and after much playing around with different settings just to try to trick it into working.
If i'm being totally dumb, please let me know. Perhaps there's a few bugs in the system, perhaps another iteration on the interface is necessary for clarification. I did get it to work, but just wanted to let you know of my experience setting this up, in case you haven't tested this scenario of events. I get the feeling that Mala's order in which key remapping happens vs. led blinky plugin is called to light the buttons is off, or Led Blinky didn't really anticipate encoder remapping on the fly. :dunno
Love this app, would love to help make it better. Hope this helps.
-csa
-csa
arzoo:
csa-
Sorry you had a hard time. A bit of clarification - LEDBlinky doesn't read any data from the IPac - the only way it knows what keycodes are assigned to each button for any emulator (other than mame) is based on the settings defined using the controls editor for each emulator.
So here's an example;
Let's assume in the device/port input map you have LEDWiz port 1 assigned to KEYCODE_A. That means any game for any emulator with a control assigned to KEYCODE_A will light up port 1.
Next, LEDBlinky needs to know for each emulator (other than mame) what controls each game uses and what keycode is mapped to each control. This mapping should match your keyboard encoder (IPac). Since LEDBlinky doesn't read any data from the keyboard encoder, you need to configure this manually - that's where the controls editor comes in.
So let's configure a fictitious emulator; ABC. You create a <default> control group for emulator ABC and add the control P1_BUTTON1 and assign it to KEYCODE_A (very important!).
Now, when your FE starts a game for emulator ABC, here's what LEDBlinky does;
- The FE passed the emulator name ('ABC') and the game name ('pac-dog').
- LEDBlinky looks for unique controls defined for 'pac-dog'.
- Since none have been defined, it looks for 'ABC' <default> controls.
- It finds P1_BUTTON1 mapped to KEYCODE_A.
- The device/port input map links KEYCODE_A to port 1 and the LED wired to port 1 lights up!
So that's the basics.
But let's say you defined P1_BUTTON1 for ABC but didn't assign it to any keyboard input code. Technically, nothing should light up. Unless... you've upgraded from an older version of LEDBlinky. In this case your controls xml file may have defined a set of overall default control input codes for all non-mame emulators. This can lead to some confusion and in retrospect maybe I should not have migrated this data. If you want, edit (using notepad) the LEDBlinkyControls.xml file and looks for this node:
<controlDefaults groupName="OTHER"
If you find it, you can just change it to this and the data will be ignored:
<controlDefaults groupName="OTHER-ignore"
Anyway, hopefully this helps understand what's going on. But if you send me your debug.zip file I can get a better picture of your exact configuration and help out.
arzoo
arzoo:
--- Quote from: EnderWiggen22 on June 06, 2009, 04:03:58 pm ---I'd be down, but I can't seem to get my sh*t together. When I add plugins to mala it crashes/freezes...
--- End quote ---
Any plugin? What have you tried?
--- Quote ---Basically, I've created a few lwax animations and I only want them to run once the screensaver starts (or a timed period of inoperation). Then I either want all the lights on during both fe and mame use or all off.
Sorry to post this here, but I figured this would get the best responses. I know you, and those who view this, are likely to have faced a similar issue before.
I guess I am asking for a piece of software that will run a lwax file after a period of inoperation. Anybody seen this before? Controlling the lights always on/always off behavior would be a plus.
Thanks guys
--- End quote ---
Yes - it's called LEDBlinky ;)
If you've created lwax files you must be using the animation editor. Have you tried LEDBlinky with MaLa?
kellenmeister:
Hi there,
it is possible to display the associated controls from a Mame Rom by "Selecting" a Game in Hyperspin? Atm work this only at "Starting" a Game.
In MaLa is this possible.
Sorry for my bad English. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version