jonnieboyrevel Posted March 20, 2015 Share Posted March 20, 2015 Hi all This is probably a very stupid question but I thought it was better to ask before I started replacing things... I'm currently building a cab with LEDBlinky and RGB buttons. Currently I am using individual emulators for all my systems. I'd only recently come across Retroarch but quite like the idea of only updating one system rather than many. My question is, does Retroarch play nicely with LEDBLinky? As far as I understood it, LEDBlinky distinguishes different systems based on the exe file but I might be wrong. If this is the case, how would LEDBlinky know which system was being launched and which buttons to light up? Thanks for any help you can give me. JB Link to comment Share on other sites More sharing options...
Johannes1100 Posted December 22, 2015 Share Posted December 22, 2015 I was looking for an answer on the same question. Did you figure it out? Link to comment Share on other sites More sharing options...
newoski Posted December 22, 2015 Share Posted December 22, 2015 Hi all This is probably a very stupid question but I thought it was better to ask before I started replacing things... I'm currently building a cab with LEDBlinky and RGB buttons. Currently I am using individual emulators for all my systems. I'd only recently come across Retroarch but quite like the idea of only updating one system rather than many. My question is, does Retroarch play nicely with LEDBLinky? As far as I understood it, LEDBlinky distinguishes different systems based on the exe file but I might be wrong. If this is the case, how would LEDBlinky know which system was being launched and which buttons to light up? Thanks for any help you can give me. JB YES, it works great. But your understanding of LEDBlinky is a bit off. LEDBlinky doesn't use the emulator EXE to determine anything. The only system that it supports out of the box is MAME and MAME-related systems like SNK Neo Geo. It supports them natively because it is able to read the mamelist mame.xml, colors.ini, and controls.ini that MAME uses. This tells LEDBlinky what controls to light up etc. All other systems, like consoles, need to be manually mapped in LEDBlinky's ControlsEditors. For example, you can setup NES so that your joystick, button b, button a, start, select light up and speak the controls. However, again, it is a manual process. With that said, yes, RetroArch and all emulators are supported via manual mapping. LEDBlinky doesn't care what emulator you're using. It just needs to know what you want to light up. I have like 60 systems, including a TON of RetroArch dependent, set up and working without problems. Link to comment Share on other sites More sharing options...
Johannes1100 Posted December 22, 2015 Share Posted December 22, 2015 Great, thanks for the detailed explanation. I will try to config Ledblinky in the next days. EDIT: Works flawlessly with Rocketlauncher an Retroarch. Each system/emulator passes the name to RL (and LEDBlinky). Using the system/emulator names, LEDBlinky matches the controls. Link to comment Share on other sites More sharing options...
JKing3 Posted February 12, 2016 Share Posted February 12, 2016 @newoski - Would you be willing to share your Controleditors file for the different systems? Seems like this would be valuable, or point me to the right direction so I don't have to recreate them. and I'm still confused on how you pass the right core to ledblinky? Thanks. J Link to comment Share on other sites More sharing options...
newoski Posted February 12, 2016 Share Posted February 12, 2016 I will be sharing my setup soon. Putting the polish on the app. More soon... Sent from my HTC6535LVW using Tapatalk Link to comment Share on other sites More sharing options...
JKing3 Posted February 17, 2016 Share Posted February 17, 2016 Great, can't wait. Let me know if I can test out or help in anyway. J Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.