Headrush69

You can override using LEDBlinkyControlsEditor and set intensity levels for RGB for any button per game, or you can also add new colors in Color-RGB.ini and then reference them in colors.ini For example: In Color-RGB.ini In colors.ini

I have a full non-merged mame2003plus rom set and core still working fine called from LB. Santaclaw, is it all roms or just some?

The problem with DAT files is they contain specifics about the roms in every rom set. That can change with MAME versions. Once I have my curated list, I just do a directory listing in Powershell, removing the file extension and redirect that output into a text file. This file just lists the rom set name, no details about the roms within. When you import that file in CMP, it will enable those rom sets and automatically grab all the roms within those sets.

A couple things: You have to click the Advanced button and make sure the Separate BIOS set is not enabled to make true inclusive rom sets. When rebuilding, CMP doesn't base the sets it's creates on what is in the input folder per sa. It knows the split or merged set you have in the input folder has roms used by other sets as well, so it tries to create those sets as well and thats why you see more rom sets in your output folder. To do what you want, you have to click the Set Information button when in the scanner section. When this opens, you will see all the roms and some like Neo-Geo are grouped. Deselect all and than only select the ones you want. The Set Information tab has some great features. Now that I have my MAME game listed curated, I have a simple text file with all the names of the roms I want. Each MAME release, I bring up the Set Information, deselect everything and select roms by the import file feature there. Only the roms I want update and super fast. The only time this won't work is if the rom set name completely changes (not the roms inside), but that doesn't happen often. (Especially with the common rom sets)

Exact same situation here as well. You're hardware is also going to matter as well, as some CHD games can be quite demanding as well. I generally start MAME and filter by working CHD based games and cherry pick the ones I want/like. I then only keep those one's on my main cabinet. Within LB I hide the ones my lowly i3 can't quite handle and might unhide if I ever upgrade the CPU in the future.

Corrrect, but 0,233 is newer and must be better! ?

Sounds like all standalone emulators. Have you added any command line parameters for these emulators?

I think at that site they are only at MAME version 0.198 (for roms) and that file was added with release 0.231. It's also a device file. Basically you'll have to find another source.

Your title said first ROM, do all ROMs exhibit this behaviour? What do your advanced settings look like? You have to enable them in options first so they appear. I know in there is a option to check for a previous running process which could be linked to your issue of it running on second try. PS. For N64 I use the mupen64plus_next Retroarch core and only use Project64 for mods and hacks which need extended memory. I find it's a better experience and works great for "normal" ROMs.

Are you using the "Demo Game Controls" option in LEDBlinky? If so increase the Demo Scroll Delay and see if it's any better.

What exactly happens when you have these performance problems? I have only an i3, but using the Unified Redux theme I don't have any issues, maybe give that a try. What are the I/O errors you get in LEDBLinky? You shouldn't be having any I/O errors and sounds suspicious.

Since the XEGS was essentially identical internally, picking the computer options in Retroarch should work fine. (130XE)

Select the games you don't want to see, right click and select edit. In the window that opens, for the Field, pick Hide. Make sure there is a check to enable hidden. If you every want to see hidden roms, just pick Show hidden roms under the view menu, You can edit individual or multiple files to change that attribute as needed.

I prefer to keep my iPac in keyboard mode as they are basically used for arcade games only, but you you can add more real XBOX controllers as well, The only thing you'll have to do is make sure you set the right controllers in each emulator. Sure, the STL files are on Thingiverse, but I don't have the direct link handy. SInce I used the iPac in keyboard I was able to enable both the arcade controls and the Xbox controllers at the same time. (very easy to do in Retroarch) I have since changed to just using the Xbox controllers for console games. Some of the games on consoles with analog controls, really need real analog to be playable.

I can't speak to the specifics of using a PI and driving your LED, but the information the LB sends to Pixelcade is quite simple and nothing is stopping you from intercepting that information and running whatever program you need to accomplish your task. In your LB's settings, just set the location of Pixelcade instead to your application. Use the Platform and game name passed as needed to decide what to display. Use whatever tool you need to send an image or text over to your Pi.

Another option is don't limit yourself and add some controllers. I have 2 XBOX wireless controllers that are mounted on the front of my cabinet. Using a few 3D printed holders they are very inconspicuous and don't crowd the normal arcade control panel.

Update: Seems MAME 0,233 has apple2gs joystick updates. I tested Gauntlet with it and I am able to play with it. The game start screen still has a tendency to pull to the bottom right corner when the joystick is centered, but you can move around the screen and in game it works fine.

Just use Reshade and you can add bezels to other systems fairly easily.

I would suggest adding your pre-emulator programs as additional apps in LB that launch before the m2emulator, than just adding the following in the running Autohotkey script for the emulator in LB.

Have you tried with a clean install and no cfg or nvram files? Have you tried entering the test menu of the game and checking/calibrating controls within the game

So what exactly is the issue? What is happening? If you open a command prompt and navigate to your MAME folder, then run it will tell us the problem.

This file will not be used. MAME will only read the one in it's ini folder. When you are using the -cdrm option, you are no longer using MAME's software lists and are passing the path to the chd for MAME to use. Your file structure needs to be like this if using software list loading: We also need to see your default MAME settings in the LB Emulator page. When using software lists, you only want to pass the software name, not a full path.