Hey guys, I'm hoping you can help me identify which file(s) to edit so my LEDblinky controls work correctly with Launchbox and Singe 2.0. (Mostly trying to run Daphne games) I'm just trying to illuminate my joystick buttons that are active for the selected game. I have it set up and working fine with MAME, but when I add games for Singe 2.0, all 6 buttons stay illuminated.
Details:
LEDblinky works fine with with MAME
The arcade controls work with JoytoKey mapping, but it seems like a bandaid to the real fix and I feel that could be causing issues with LEDblinky
When I select a game, the correct controls light up, then when the game starts, all 6 buttons illuminate. (see attached picture)
I'm launching directly from the .bat file, not using emulation to launch the games.
Should I be using emulation? I didn't use the emulation because I didn't have a .txt file for Dragon's lair 2 and didn't know what I needed to include. My Time Traveler ROM came with the .txt file to use with emulation and that launched fine. DL2 didn't.
I couldn't figure out how to configure the Singe controls to work with the joystick panel so I started running JoytoKey. That worked, but now I have a proliferation of files that could be managing control settings.
Launchbox default controls
Singe 2.0 emulator default controls
LEDblinky emulator and game specific controls
Daphne game specific controls (for example, Dragon's lair 2 has it's own controls file within the Singe 2 root folder.)
JoytoKey button mapping
Weird detail I'd like to fix but it's a low priority: When at the Launchbox menu, all 6 player 1 buttons are on, but all 6 player 2 buttons are off. Once a game is selected, the lights match the game files. It's really weird.
I'm running the ultimarc pacled64 for my ledblinky
So my two goals right now are:
How do I only illuminate the buttons used in the Singe/Daphne game being played?
Understand which file really manages the controls for each Singe game so I can edit those as necessary. It works with JoytoKey mapping just fine, but I feel like that might be what is messing up LEDblinky.