Headrush69

It's going to be hard to give you specific advice (at this point) because you have too many variables about what you are going to use. The Mame2003Plus set is based on a very old mame set, so using it with a newer MAME standalone is likely to introduce problems. Nothing is wrong with using it, but best suited if you stick to the Retroarch 2003plus core. You said you installed touchmote, so are using using wii remotes as your light guns? Do you have one or two? Are they connected with a Mayflash bar? If only one wiimote, you don't need touchmote, just set it to mouse mode (assumming Mayflash), and it should be simple to configure in standalone mame.

RingWide Media

Could the pause be from LEDBlinky parsing the mame.xml and/or creating the minimized mame.xml it uses? Maybe have LEDBlinky load on Windows startup instead of when Big Box launches. Another option is create a small AHK, to launch BB. Have it start LEDBlinky first, pause a bit and than launch BB normally. Edit: Or delay the mame xml loading. As per LEDBlinky site:

Those programs don't decide on the naming, it's the dat file itself. You can find all kinds of specialized or altered dat files. You can even make your own dat file using tools like dir2dat. I don't use them anymore and just keep the games I like/want manually like you. Wasted too much time keeping sets up to date rather than just enjoying using them, The only complete set I maintain is the MAME set, and I simply just let the bittorrent client keep it updated rather than using a rom manager.

Basically it's just a list and checksum of all the roms/images for that system. So if you're trying to build a complete set of all roms, you'd use that file and a management application like ClrMamePro or RomCenter and it would check what you have and do other things like rename to proper name, remove duplicates, things like that.

They don’t. Check out redump.org or www.tosecdev.org

It's probably related to their site being recently hacked. The libretro prosystem github pages seem to be intact, so I'd just give it some time and it will likely get fixed up.

If you are using the stand alone variants, you have to configure your controller within each emulator as required by each one. That's an advantage of using the Retroarch cores of the same emulators, auto configuration of controllers. If it doesn't already have an auto-config, which I believe the F310 does, you configure it once and all retroarch cores use it.

I keep LaunchBox on my SSD and all my roms on my larger platter drive. If you go into Disk Management, you can also set your HD to mount onto a empty directory, which I do to the LaunchBox Games folder. Using this method you can leave the LB defaults and keeps things simpler. You can access files in the LB Games folder, or the drive letter.

Just another Phoenix Launcher

Thanks, Really love the look of the work you have done.

LaunchBox doesn't set up controllers for within emulators, you have to do that manually. Those settings are for controlling LB itself. What emulator are you using, Retroarch? If yes, do you see any messages about the controller being autoconfigured? I thought the F310 had an autoconfig included with Retroarch, but you might have to update joystick profiles within Retroarch to get that.

I don’t understand this, don’t upgrade then. Is the issue more you paid for a lifetime license that you don’t really need or that you DO want future updates, but without upgrading other dependencies? Seems like unreasonable request if the second option.

What version of LEDBlinky? There was a recent update that helped with an issue like that.

After trying several different backup solutions, I settled on FreeFileSync as well.

So you’re using a pre-installed image on retro pie. This really isn’t the forums for supporting retro pie, and pre-installed images, but it sounds like you didn’t set up the second controller yet. If I remember correctly, the initial installation on retro pie only does the first player. Check on the retropie forums and you’ll find out how to set up the second one. After that retroarch, should be configured automatically.

Are trying to use MAME as well or a different emulators like Retroarch?

Some great info on the changes recently to the Retroarch N64 cores: Low Level RDP upscaling Mupen64plus-next 2.1 So you have the option of using same GlideN64 as m64p, and all the extras of Retroarch. (If you like or use those)

Check out Demulshooter I believe it includes some lua scripts to add to the m2emulator to add crosshairs for those games.

I get the same output even using the software list cassette image. The sysinfo page for this system says there are issues including interrupt and memory handing, so it's bound to have issues with some software.

Can you run it from a Command Prompt or Power Shell using the verbose option (-v) and post the output to see what's happening?

I've been using this exclusively for MAME. You can waste a lot of time searching, trying. and evaluating so many shaders options that some will say are better but it's so subjective and nothing is perfect for every game. I've found this one to be well rounded for the games I play, performs well and stopped looking at others and started playing more.