Headrush69

It's not clear what you are suggesting your problem is. So you have enabled LEDBlinky support in LB? You have set up LedBlinkyConfig to enable setting Ultrastick maps? You have set up LedBlinkyEditor so the primary controller is set so for your games so it knows which Ultrastick map to load? If all those are working correctly, are you saying the Ultrastick has a slow response time?

The github page has a package to download that has BAT files already configured for most of the games supported and the easiest method is just to set each game to runt hem, not use the emulation settings in LB. Hypseus Windows BAT files

That it works when you zip the CHD and enable "decompress before launch" but it doesn't work when not zipped and that option is disabled, sounds like the "decompress before launching item" is still enabled. Are you sure the Extract ROMs option in your Associated Platforms sections isn't enabled?

I'm not familiar with the brooks board, but I do have a setup with 8 different controllers including an iPac. Currently I'm using Tur-Game_Controller_Order_1.5. It uses devcon as well but also includes instructions for getting it to run with administrator privileges on startup. This also has the advantage that it can continuously monitor usb insertions and deletions and make sure device order stays the same.

If you have children in the house, mapping those functions to the shifted feature of the iPac might be a safer option. You pretty much double the number of keys you have and it gives you lots of options for handling keystrokes needed for even games in computers systems. (ex Y, N, F1..F11)

Yes, being network based it does add a slight latency to image display but it does offer some advantages as well. If you ever add light guns (IR based at least), or have emulators that change resolutions, you don't have to deal with several issues that dual screens set ups have, and it works in LB as well. There are ways to deal with them, and if you boot directly into BB you can hide them, but it's one less thing to deal with and maintain. Tell me about it. I bought 2 (not from Pixelcade), and they look absolutely identical, but one was a complete disaster needing custom timing and other issues and the other one worked out of the box perfectly without any configuration or "hacks" needed.

There are some handy 3rd party tools like Display Fusion that are useful for multi monitor set ups and I believe include actions for moving specific windows to selected monitors.

I felt the same way about mine and also found the switching wasn't always so easy. If it wasn't easier for me knowing how to do it, I knew it would be worse for other users. In the end I switched to Ultimarc servosticks which allowed me to automate the switching which was a better end user experience and everybody seems comfortable with the greater throw of those sticks.

Sounds about right. I think I have 3-4 less than the full working CHD set and I'm at 87GB.

Glad you got it working. That is a confusing option for many as you would naturally think you are passing a zip file to Retroarch, it needs to be unzipped.

Are you 100% sure you are checking the right location of Retroarch? Did you install Retroarch using LB's bult in installer or from a manual install of Retroarch? Do you have both installed by chance?

That's a huge task and might not be practical considering the percentage of people that use Windows over other OSes. For now you can place a shortcut to Launchbox/Big Box in your Windows startup folder. There are some links about cleanly and silently setting up Windows to boot into LB. I don't have the link handy, but I think there was a good exhaustive and detailed instructions on the arcadecontrols forum.

If you look in your Retroarch -> config -> corename folder you will see overrides you have saved. (.cfg files) One named the exact same as the core name applies to all games run by that core, a game specific named overrides that and applies to a specific game. Any other named ones are directory overrides that match a folder. The order they are applied is core -> directory -> core If you look at the files, right near the top, likely the first line is the overlay file it is set to use. The easier method is just pick your overlays in Retroarch, bring up the Quick menu, go to Overrides and make sure to pick the correct override you want. It will replace any previous saved version and correct any mistakes you made.

All those are based on open source Linux. LB/BB can't legally distribute a copy of MS Windows.

Are you sure you saved the game bezel as a game preset and not as a per-core or a per-directory overlay preset?

I've found some scripts that do that by modifying the registry but iexplorer.exe needs to be restarted as well. Not sure that's a great solution but I can message you the script if you want to take a look. My issue with killing and restarting MameHooker as needed is MameHooker seems to take some time to start up and that's less than optimal then I want for my cabinet.

Just haven't had time to add rumble to my Gun4IRs, but did some testing and finding the same issue as you. Although both MameHooker and MameOutputTester (from LEDBlinky) can run concurrently and both will see the MAME outputs, once you "consume" the event with one or the other it seems doesn't work. To test I used LEDs and the rumble feature of my XBOX 360 controllers. Even if I try to consume different outputs on each, it seems only one can consume events at a time. I'm really going to have to think about the best option moving forward. Short of LEDBlinky adding serial support to outputs or MAMEHooker seeing my Ultimarc Ultimate, there doesn't seem to be an easy or elegant solution.

MAME shows both player controls because in cocktail mode the controls would be physically different. Just spit balling here, but maybe using cocktail mode and some custom layouts might be able to get the results you are looking for.

I'll just be adding the rumble to my Gun4IRs later this week, so can't do that specific action, but when I said MAMEHooker was speaking, I didn't mean just that it found outputs and was speaking them. It was a custom action for a specific MAME output that I added to speak my chosen phrase, so sending a COM port command shouldn't be any different.

I just tested and with both apps running LEDBlinky handled LEDs and I had MameHooker speaking. So it should be possible to have LEDBlinky handle the LEDs and MameHooker send COM outputs to control rumble in the Gun4IRs.

Good to know. I haven't got around to setting up the outputs for my Gun4IRs yet. MameHooker doesn't recognize my iPac4 Ultimate, so I was just using LEDBLinky for now as it worked just fine for LEDs. Is it not possible to run both apps and have them just react to the outputs they need to command different functions? I haven't look at it deeply yet but I thought MAME outputs used a broadcast system and that might work.

Without a screenshot we can't give you any real answers, but that you say it happens with different SNES cores and no other Retroarch cores, suggests maybe you have a directory override with some changed setting.

There is no per game option to turn it off, you could use a pre launch command in LB to turn off LEDBLinky.exe. You also know that LEDBlinky has built in support to respond to MAME Outputs as well? Some simple ones like flashing start buttons blinking when coins are inserted are enabled by default, but you can add more complex ones as well. I have my LEDs flashing between red and blue for police lights in Chase HQ without using MAME Hooker.