Hey all...I have quite the issue I can't seem to figure out..
I currently have a BigBox set up (on the latest build) running Ultimarc RGB buttons connected to a PACLED64 on a PC running Win10.
I've got LEDblinky setup to light up the RGB buttons that are in use for the current launched game as well as change the colors to match said game.
This has been working without issue...but now I am running into an intermittent issue.
When I launch a game via BigBox sometimes the buttons do not light up, other times its lighting up the wrong ones.
For example, if I launch MSlug2, it should light up buttons 1-4 on player1 and buttons 1-4 on player2, changing them to the NeoGeo colors as well.
What happens is sometimes it never lights the buttons or it will light up other buttons random colors. One example is it lighting up player2 button 6 (which is not used for this game) and then like my spinner 1 button, colors will be random too.
I went down the basic t-shooting, checked my configs, made sure all my buttons are mapped correctly, checked mame.xml, made a new one to boot and so on...same issue. Not always 100% of the time but it does come back.
So, I decided to run the LED-trouble shooter to get some debug logs to look at....and this is where it gets odd.
If I enable the debugger, launch BB like normal and select MSlug2 (or what ever game, issue is the same) the issue goes away..game buttons light as they should and everything is happy. As soon as I disabled debugging for LEDBlinky, issue comes back.
I can't figure out why LEDBlinky works flawless when I have debugging enabled but as soon as I launch it without, there's a 90% chance the issue comes back.
I have uninstalled LEDBlinky, deleted my configs and remapped all the RGB buttons again. Rolled back LB/BB, swapped usb ports for the PACLED64 and the issue persists, but if I enabled LED Blinky debugging, no issues whatsoever...
Anyone have a thought as to what might be the issue?