Headrush69

That's normal behavior. When using a system like that, it would read the system artwork if it existed. So in this case a pegasus.zip artwork file. So use the -override_artwork option and if it doesn't exist for that specific rom it will fall back to the system one. (pegasus.zip artwork)

Make sure Launchbox\Games is an empty folder Open Disk Management Selection the partition you want to mount into the Launchbox directory Right click and select Change Drive Letter and Paths Click Add in the window that opens Select Mount in the following empty NTFS folder Hit browse and pick your Launchbox/Games folder

It's a tiny little bit of work (just moving, not copying folders), but what I do is have all my platform rom folder in the root of my E drive, than I also mount this drive onto my Launchbox\Games folder. I can access files through E drive or Launchbox\Games and this means i can leave platform file locations as default and use relative file paths. This should work for you as your current paths are within the Launchbox folder, so your entries in your platform.xml files should be the same. I'm sure there are other options as well, just how I have mine and works great.

The same folder as the Dolphin.exe is the only place it will be. If it's not there you are used the shared global location. Explained here. Just the first line, Once you open the editor you should see that gameID already in the User Config area on the bottom. You add your control information there. Dolphin will create the ini for you automatically. See the picture I posted above. (My example is a Gamecube example, but Wii game is same method.)

It's just an empty text file exactly named portable.txt. That tells Dolphin to save files in that folder rather than a system shared location.

Do you have the file portable.txt in the Dolphin folder? If not it saves in system wide save location and why they would be using the same profiles.

Do your profiles work using Dolphin directly? Selecting one in controller options and clicking load should work. Note that the profile also includes the native device it is mapped to, so that has to be right as well.) Right click on a game in the Dolphin gamelist and select properties. Click the Editor tab. In the User Config section, you set your custom controller settings. Attached is a sample I have for setting a Gamecube game to use my Xbox 360 wireless controllers. Note: My Xbox 360 profile is mapped to device Xinput/0/Gamepad The Wii controllers work the same, just use the WiimoteSource and WiimoteProfile instead.

Glad you got it working. Nothing like an illuminated track ball.

Sure, you just need to make a gameini file for games that need custom controller settings. Dolphin docs about GAMEINI

Is the input within MAME mapped to the track ball? If you enable debugging in LEDBlinky and start missile command and than post the debug log (minus your emial), we can probably see where the issue is. You can try running the LEDBlinky Troubleshooter as well, it can find many issues.

Check the Supermodel.log file after a failed launch and check what parameters are being passed to the emulator. You should see something like this: This will tell us where the issue might be.

There's no single simple answer as every emulator is different and how well they do digital to analog conversion can very greatly. One thing you can try is turning off or down the auto repeat key speed in windows, so your not sending the same key repeatedly when held down longer.

Sure, but I don't think the default colors.ini and controls.ini included with LEDBlinky includes an entry for Missile Command. (I don't use the stock files, everything is custom.) You'll have to start LEDBlinkControlsEditor.exe and make an entry for missile in the MAME section. Within there set the colors for your controls including your trackball. The LEDBlinky documentation is quite good if you need more detailed explanation. Just remember you have to restart LEDBlinky for changes to be seen.

If you can write a text file with the roms you want, (You can echo a directory listing into a text file as well), you can use that file to filter rom sets in ClrMamePro and do exactly what you want very easily. Each MAME update you can use that same text file and it will pick up any rom changes within sets and fix as needed.

Yes and no. LEDBlinky uses the control.ini file for finding the primary controls before checking your custom mapping set using LEDBlinkyControlsEditor. This file only contains some games. You also have to remember that depending on how you imported into LB, region based roms may not have an entry in controls.ini. So for example, if you imported the MAME game 1941, but you have the North America version, 1941u, that isn't in controls.ini and LEDBLinky doesn't search the child-parent tree like MAME roms do. If you enable the LEDBLinky debug option, the debug log is very informative and easy to read, you'll be able to tell if a specific rom is finding an entry for a rom and whether the issue is LEDBlinky itself, or just a missing mapping.

Even though it works, just be aware that when you include the ! character, you are sending ALT + F12

Change to the following line:

Yes, thanks. I was hoping the app had a true native launch option. Do you use SSF as your go to Saturn emulator? I generally use the mednafen core in Retroarch but I'm always open to other options that improve the end user experience as much as possible.

Do you have it starting full screen without using 3rd party tools? I can't seem to get it trying all the "old" posts about how it should work.

You want to save either a core or a content directory override with the universal bezel for each system enabled. If there is a game specific one it should override the universal one.

Have you set the the primary control for the games that need a change in Controls Editor? A post of a debug log would probably indicate where the issue is fairly quickly.

In the controls section of Retroarch's quick menu, save a core remap, a content directory remap or a game remap and it should be set ever load. You probably want a core remap unless you have a core that runs multiple systems, which you'll probably want content directory remap for that one.

If you start the core, bring up the Retroarch quick menu and go to Options -> System and enable Display MAME menu Return to the game (any game is fine), hit the tab key and it should bring up the old MAME menu. There should be an option there to generate and XML file. I think it saves it in the core's save folder, can't remember 100%. There's your DATA file.

They are ALL complete sets, just each is for a different MAME version. MAME2003 reference set is for the MAME2003 core which is based on MAME 0,78 <- this set doesn't change MAME2003plus reference set is for the MAME2003plus core which is also based on MAME 0.78 <- this set however does change. Best way to get complete set is use current DAT to rebuild. Although they share a lot of the same roms and some haven't changed at all, it can explain why so work and some don't. @santaclaw Glad to hear your happy with the solution. You might also want to look at the FBNeo core. Although I keep a current + roll back packs for all 3 emulators, I'm looking at switching to FBNeo for many of my main arcade titles for it Retroarch integration and features.

You never answered whether it was all roms or some? FYI, the 2003 reference set isn't the complete 2003plus set. (They are both based on MAME 0.78 though) The MAME 2003-Plus Reference set found on a popular archive site is from 2018 as well. So not up to date,.