Main > Software Forum
LEDBlinky - Arcade LED Control software and Animation Editor - v8.2
websherpa:
--- Quote from: arzoo on September 02, 2021, 02:20:25 pm ---
--- Quote from: websherpa on September 02, 2021, 12:19:49 pm ---Has anyone figured out how to better integrate/program LEDBlinky with CoinOPS / RetroFE for the front end itself? For emulators other than MAME being addressed by CoinOPS/RetroFE? (I know there is a plugin in early development but haven’t messed with it yet, not sure how big a scope it has yet.)
--- End quote ---
You're in luck - I'm currently working with the RetroFE dev to get LEDBlinky integrated with RetroFE and CoinOps. So this will be included with the next LEDBlinky release (hopefully in a few weeks).
--- End quote ---
Yay! Fantastic, thank you! LEDBlinky purchased!
jevansoh:
I just purchased LEDBlinky and am very happy so far, but I'm running into an issue where multiple P1 buttons and P2 buttons are lighting in MAME games, besides the correct ones.
For instance, in 1941, P1 and P2 Buttons 1, 2, 4, and 5 are all lighting up, when only 1 and 2 should light up. On Street Fighter, on P1, all six buttons light up, but as it's flashing each button, some of them will flash together, like button 3 and button 5, for instance. But on P2, only Buttons 1-5 light up.
I researched this before posting here and found the Troubleshooter.
Here's what it says:
The selected Emulator is MAME (or a MAME variant).
The Input Code(s) for the selected control [P1_BUTTON1] were defined using MAME default values. You can override the default Input Codes from the MAME configuration or in-game menu.
---------------------------------------------------------------------------------------------------------------
Analysis:
These are the Emulator defined Input Codes for [P1_BUTTON1]:
KEYCODE_LCONTROL
JOYCODE_1_BUTTON1
MOUSECODE_1_BUTTON1
Using your assigned Input Codes from the current Input Map, the following ports were enabled (ON):
iPACUltimateIO ID:1 Port:82 Label:P1B1 (RGB Blue)
iPACUltimateIO ID:1 Port:83 Label:P1B1 (RGB Green)
iPACUltimateIO ID:1 Port:84 Label:P1B1 (RGB Red)
iPACUltimateIO ID:1 Port:91 Label:P1B4 (RGB Blue)
iPACUltimateIO ID:1 Port:92 Label:P1B4 (RGB Green)
iPACUltimateIO ID:1 Port:93 Label:P1B4 (RGB Red)
If the wrong Button/Control is lighting up, this can be resolved by adding any one of the Input Codes listed above (in this color) to the correct LED Controller/Port(s) using the LEDBlinky GenLEDBlinkyInputMap application.
The following Control is assigned the same Input Code as P1_BUTTON1:
UI_SELECT (JOYCODE_1_BUTTON1)
This may cause P1_BUTTON1 to light when it should not, may be the wrong color, and may cause the wrong control action to be spoken. If this is the case, you must assign an unused Input Code to UI_SELECT which is currently using a MAME default value.
______________________________________________________________________________________________________________
I see it references both P1 Button 1 and button 4, so it's correct in reporting that both buttons are lighting when only button 1 and 2 should be lighting and not button 1, 2, 4, and 5, but I don't know exactly what it means by "adding" the port and don't understand what the problem is and what it's telling me to do.
I also don't understand the differences between KEYCODES and JOYCODES and would really appreciate an explanation as to what each of them mean and how each are supposed to be used and what they do.
Any help figuring all of this out would be much appreciated.
arzoo:
--- Quote from: jevansoh on November 23, 2021, 11:18:32 pm ---I see it references both P1 Button 1 and button 4, so it's correct in reporting that both buttons are lighting when only button 1 and 2 should be lighting and not button 1, 2, 4, and 5, but I don't know exactly what it means by "adding" the port and don't understand what the problem is and what it's telling me to do.
I also don't understand the differences between KEYCODES and JOYCODES and would really appreciate an explanation as to what each of them mean and how each are supposed to be used and what they do.
Any help figuring all of this out would be much appreciated.
--- End quote ---
KeyCodes are the keyboard buttons and JoyCodes are the joystick buttons (and directions).
Typically each button on your control panel is assigned one or more unique input code (otherwise multiple buttons would do the same thing). When you configure LEDBlinky's input map using the GenLEDBlinkyInputMap app, you assign the input codes for each set of RGB ports. For example if pressing a button on your CP sends keyboard "A", then you should assign KEYCODE_A to the ports for the LED under that button.
From the info in the TroubleShooter, you have the RGB ports for both P1B1 and P1B4 assigned the same input codes, so as far as LEDBlinky knows, these two buttons do the same thing and should light up together. Using the GenLEDBlinkyInputMap, you need to remove the input codes for one of those two buttons and assign the correct input code(s) based on what the button actually sends. You can use the QuickCode feature to help with this. Hope this makes sense.
jevansoh:
Ok, I understand better now.
The only thing I still don't quite understand is the difference between the KEYCODE and the JOYCODE.
Can you tell me why the JOYCODE should be put in the map? I understand the KEYCODE, but I don't see what the JOYCODE does to the features/functions of the system.
For instance, what would happen if I just simply remove all the JOYCODES?
--- Quote from: arzoo on November 24, 2021, 08:55:02 am ---
--- Quote from: jevansoh on November 23, 2021, 11:18:32 pm ---I see it references both P1 Button 1 and button 4, so it's correct in reporting that both buttons are lighting when only button 1 and 2 should be lighting and not button 1, 2, 4, and 5, but I don't know exactly what it means by "adding" the port and don't understand what the problem is and what it's telling me to do.
I also don't understand the differences between KEYCODES and JOYCODES and would really appreciate an explanation as to what each of them mean and how each are supposed to be used and what they do.
Any help figuring all of this out would be much appreciated.
--- End quote ---
KeyCodes are the keyboard buttons and JoyCodes are the joystick buttons (and directions).
Typically each button on your control panel is assigned one or more unique input code (otherwise multiple buttons would do the same thing). When you configure LEDBlinky's input map using the GenLEDBlinkyInputMap app, you assign the input codes for each set of RGB ports. For example if pressing a button on your CP sends keyboard "A", then you should assign KEYCODE_A to the ports for the LED under that button.
From the info in the TroubleShooter, you have the RGB ports for both P1B1 and P1B4 assigned the same input codes, so as far as LEDBlinky knows, these two buttons do the same thing and should light up together. Using the GenLEDBlinkyInputMap, you need to remove the input codes for one of those two buttons and assign the correct input code(s) based on what the button actually sends. You can use the QuickCode feature to help with this. Hope this makes sense.
--- End quote ---
arzoo:
--- Quote from: jevansoh on November 24, 2021, 07:47:43 pm ---Ok, I understand better now.
The only thing I still don't quite understand is the difference between the KEYCODE and the JOYCODE.
Can you tell me why the JOYCODE should be put in the map? I understand the KEYCODE, but I don't see what the JOYCODE does to the features/functions of the system.
For instance, what would happen if I just simply remove all the JOYCODES?
--- End quote ---
The joycodes are only necessary if you are using an input controller that has joystick buttons. If not, you can remove them.