Main > Software Forum
LEDBlinky - Arcade LED Control software and Animation Editor - v8.2
rom116:
Sent. I think i created it correctly. I ran troubleshooter, opened BB, ran a steam game, exited, tried to run Mortal Kombat for MAME, twice it kept the Steam Game (Street Fighter V) button layout. I ran MK2 for MAME and it displayed the correct button colors. Thanks.
Foxhole:
Hi. I seem to have an issue with the combination of LedBlinky and MameHooker. Whenever i have functions that require mame's outputs turned on, such as "Game pause animation" or "Flash player start + etc" it will randomly cause mamehooker not to see mame's outputs. What i mean by randomly is that when it happens it always happens after launching a game, but there's no specific number of games i need to launch before this issue occurs, it can happen either right on the first game i launch after starting up the Cab, or the second, third, or fourth launch and etc.
Once it blocks Mamehooker from seeing the outputs i have to reboot the pc in order for it to work again until the next time it messes up.
If i disable the functions that require mame's outputs from ledblinky, then there are no issues with MameHooker anymore and it works just fine every time.
I've been having a go at this for the last three days, trying to come up with something, or some workaround, but no success.
As far as I'm aware, ledblinky shouldn't cause any issues with MameHooker as long as there are no hardware conflicts, and there's none since i use ledblinky only for leds and i use mamehooker to output for the recoil of my guns.
Would love to find a fix for this.
Frontend is HS and backend is Rocketlauncher, but i also tried outside of HS and RL, and it still happens.
Ledblinky version is 7.0.4
Haven't seen any changes in Ledblinky's change log that sound like it will fix this issue. But if you believe updating would fix this issue, I'll try.
Tried on mame .211, mame .223, model 2+demulshooter outputs, happens with every emulator that supports outputs.
Of course mame's output system is set to windows.
arzoo:
--- Quote from: Foxhole on July 29, 2021, 05:46:41 am ---Hi. I seem to have an issue with the combination of LedBlinky and MameHooker. Whenever i have functions that require mame's outputs turned on, such as "Game pause animation" or "Flash player start + etc" it will randomly cause mamehooker not to see mame's outputs. What i mean by randomly is that when it happens it always happens after launching a game, but there's no specific number of games i need to launch before this issue occurs, it can happen either right on the first game i launch after starting up the Cab, or the second, third, or fourth launch and etc.
Once it blocks Mamehooker from seeing the outputs i have to reboot the pc in order for it to work again until the next time it messes up.
If i disable the functions that require mame's outputs from ledblinky, then there are no issues with MameHooker anymore and it works just fine every time.
I've been having a go at this for the last three days, trying to come up with something, or some workaround, but no success.
As far as I'm aware, ledblinky shouldn't cause any issues with MameHooker as long as there are no hardware conflicts, and there's none since i use ledblinky only for leds and i use mamehooker to output for the recoil of my guns.
Would love to find a fix for this.
Frontend is HS and backend is Rocketlauncher, but i also tried outside of HS and RL, and it still happens.
Ledblinky version is 7.0.4
Haven't seen any changes in Ledblinky's change log that sound like it will fix this issue. But if you believe updating would fix this issue, I'll try.
Tried on mame .211, mame .223, model 2+demulshooter outputs, happens with every emulator that supports outputs.
Of course mame's output system is set to windows.
--- End quote ---
When mame outputs stop working, does it fail for both LEDBlinky and MameHooker or just MameHooker? What happens if you disable LEDBlinky entirely from your FE (or exit LEDBlinky after it starts up) and then run the MAMEOutputTest app - does the problem still occur?
Are you using the same hardware (like an Ultimarc UIO board) for LEDs and your gun recoil? If so, there may be a hardware issue here.
Nothing has changed with how LEDBlinky uses mame outputs and I haven't heard anyone else reporting an issue with MameHooker conflicts, but I guess it's possible. This may be a question better directed to the MameHooker dev.
Foxhole:
"When mame outputs stop working, does it fail for both LEDBlinky and MameHooker or just MameHooker?" Just mameHooker.
"What happens if you disable LEDBlinky entirely from your FE (or exit LEDBlinky after it starts up) and then run the MAMEOutputTest app - does the problem still occur?" I haven't tried doing this procedure yet with MAMEOutputTest app running, but if i disable ledblinky completely then i have zero issues with MameHooker, i will try running the testapp alongside mamehooker and see if there's any change.
"Are you using the same hardware (like an Ultimarc UIO board) for LEDs and your gun recoil? If so, there may be a hardware issue here." No, the leds are using a pacled64 and the guns use an arduino via serial communication.
"Nothing has changed with how LEDBlinky uses mame outputs and I haven't heard anyone else reporting an issue with MameHooker conflicts, but I guess it's possible" i haven't used ledblinky alongside mamehooker in the past, so I can't really say whether it worked better in the past, I've only started using mamehooker alongside ledblinky just a few days ago.
Thank you for the prompt response. Hopefully i can find a solution that doesn't require me to disable ledblinky's output support.
arzoo:
--- Quote from: Foxhole on July 29, 2021, 10:27:09 am ---Thank you for the prompt response. Hopefully i can find a solution that doesn't require me to disable ledblinky's output support.
--- End quote ---
I did a quick search and this post indicates that MameHooker cannot be used in conjunction with LEDBlinky (with mame output features enabled). It's an old post from 2015 but based on what you're seeing, it seems to still be accurate.
Strange that LEDBlinky can work with MameHooker but not the opposite, wonder what's different in the two code implementations? Anyway, given that the two apps can't use the mame output system at the same time, the only option would be to have MameHooker handle what LEDBlinky is doing, or have LEDBlinky handle what MameHooker is doing. I can't speak to the first, but it's possible that LEDBlinky could send commands to your Arduino based on mame outputs; LEDBlinky does support serial communication outputs.