Headrush69

Did you delete the roms as well? Can't you just restore the specific platform XML from the Launchbox/Backups/Platforms folder?

I’ll check when I get home but I don’t use an emulator either. Sounds like just a misconfiguration. LB passes the platform and game name to LedBlinky, nothing about the emulator. Edit: Looks like the same issue as here: LB not passing LedBlinky game name

You can also use ClrMamePro to build a system specific platform from any rom set as well. It's as simple as only enabling the platform in Set Information dialog. This way you also know that your set is complete and contains all required roms in each zip.

What exactly mean by you can't edit individual games? So under Laser DIsc platofrm in LedBlinkControlsEditor, you can't pick NEW, you can pick NEW but can't edit the fields? I would suggest turning on Debugging in LEDBlinkyConfig and we can see what LaunchBox is telling LEDBlinky, where's it grabbing information and other info on your button mappings. (Just remove your email from the top of file before posting.)

Do mean just the ones you converted? My entire library is in CHD and launch fine with Redream.

Highly unlikely. I have converted my entire library to CHD also and every time I had an issue with one it was a "bad" dump. Finding another version always solved the issue. It seems weird as the original format would work (BIN/CUE or CDI/GDI), but the CHD format may be more specific and since it's a lossless format, these less than 100% rips cause issues.

What version of Retroarch are you using? What driver are you using for Controllers in Retroarch? I have a similar set up but with more controllers and using the latest version of Retroarch and XInput for controllerdriver and Dinput for input driver in Retroarch, my Xbox controllers always jump to #1 and #2 unless I use some controller ordering tool like Tur Game-Controller Order or devreorder.

Edit: Thread on Phoenix Launcher

That emulator is a little different than most and it's not as simple. There are some threads dedicated in this forum for getting these running more easily, just search for them. (Sorry don't have link handy)

Yes, purchase a copy of LEDBLinky.

So all those WIndows games you have to configure your buttons within each game to your XBOX controller. Some will not allow you to use analog input (Xbox triggers) for digital buttons. In these cases you would have t use a third party piece of software to do some remapping. I still don't understand how this is related to LEDBlinky. LEDBlinky doesn't have anything to do with gamepad configuration. Need more detailed information for me to be more helpful.

I am still confused. My guess is you are talking about mostly Retroarch. You want to map your arcade panel buttons to match the buttons on the XBOX controls. (So buttons A, B, X, Y, L1, L2, R1, R2) If that is true, this is done within Retroarch, not sure how LEDBlinky fits in here.

I'm confused about what you are trying to do here. LEDBlinky for the most part is used for lighting LED buttons but you are talking about XBOX controllers. Can you explain more what you are doing or your set up? The reason Quick Input doesn't see them is because they are analog inputs and button presses are digital. Some software will let you convert between them, but need to know your set up first.

The name length shouldn't be a problem. When you have any issues with LEDBlinky, should should enable debugging and look at the log file after. It is really verbose and clearly will tell you what information LB is sending to it and if it has a corresponding match in your LEDBlinkyControls file. Most of the time it's usually a mismatch in platform or rom names. P.S. If you post part of your debug log from LEDBlinky, make sure you remove your email address from it.

In LEDBlinkyConfig is the option to Light Controls in the Game Options tab enabled? (The light up option for while within LB/BB is a separate option.) When making any changes in LEDBlinkyControlsEditor, assumming you made the right entries and they match the rom name properly, you have to make sure to restart the LEDBlinky process. (Just close it in the taskbar)

With LB off, can you properly get the white using the LEDBlinky software alone? Just trying to isolate whether it's LB or something in LEDBlinky. If you backup and than replace the LEDBlinky config files as original, does the problem disappear. Turning on debugging should also tell us what information is being used to set the colors and where it's coming from.

Are you sure that the red LED hasn't failed? I had that on my LED ball joysticks once.

What exactly do you mean by" the way it does computer emulation"? The interface? Like sundoak I have tried all those options and frankly they just don't work nearly as well as MAME to me. To each his/her own, but the standalone options have there own setup issues as well.

Yes, I keep a clean system install that has everything set up. (For that OS). Than for each game, copy it and install that one game. Since this is on an Arcade cabinet it fits my needs where I don't want to keep a keyboard around.

It's a waste of space (but storage is plentiful these days), both Windows and Mac OS have autostart folders to automatically start applications.

For Amiga CD32 I think the names are kick40060.CD32 and kick40060.CD32.ext After renaming, start Retroarch, load the core, than go into Retroarch menu and check under Information -> Core Information and it should state if it sees and they are the right BIOS files. Edit: You might also want to bring up the Retroarch menu after starting and make sure that it correctly picked the right model (CD32). If not you might have to manually set and save a game or directory override so the right model and BIOS is being used.

I use the version of reshade here which is preconfigured for the m2emulator. Looks like they have updated to ArcadeCabView, but I haven't for this emulator. Only only use it for the bezels, no shaders.

My cabinet is a little slow to play that game, but in testing, even though the inputs for that game listed digital inputs, I had to set the analog inputs for player movements and they worked fine for player 2.

Yup, my mistake. Too many open tabs, and mixing up conversations. 🤐 Glad you got the right tools and got it fixed. Now just have to figure out how it got like that so you don't have that issue again. 😉