Lordmonkus

I have mine unzipped and rename the file to gamename.pbp and simply import them like any other rom file. I do leave them in their own folder but that is only because I don't convert every game and I keep all my CD based games (cue + bin) in their own folder for organizational reasons.

I have never tried using eboot files but I do know that Retroarch supports pbp files (which I believe are the same or similar) and those are imported and work like any other rom file.

There might have been but it was something that never worked for me, even using the Lilypad controller plugin which is "supposed" to let you close out as well doesn't work for me. So the AHK code is the one way that works reliably for me.

To get it to launch fullscreen go to Config > Plugins > Video, from there pick the video plugin you are using and click the Configure button. Both plugins will have a Fullscreen and Window mode selection at the top left. Pick the Fullscreen and set the resolution to match your monitors.As for Retroarch not loading your games generally speaking if RA is not loading your games outside of Launchbox there are 4 reasons why they won't load. You either have the incorrect bios, bios aren't in your \Retroarch\system\ folder, you aren't loading the .cue file or your disk image is bad. You can check out a video I made a year ago covering how to get PS, Sega CD and TurboGrafx CD games working if you like.

No problem.

Go to your ePSXe Edit Emulator window in Launchbox and then the AutoKotkey tab and put this code in there: $Esc:: { Process, Close, {{{StartupEXE}}} } This will close out ePSXe smoothly for you.

This might be the best site for SSF info now: http://www.segaretro.org/SSF Brad did do a Yabause and Mednafen tutorials but Yabause is not very good and Mednafen is pretty system intensive but maybe you will have luck with the stand alone version of it over the Retroarch version which does tend to be more resouce hoggish than their stand alone counterparts. Like I said earlier though Mednafen is very picky about your disk images compared to SSF and Yabause. Unfortunately there doesn't seem to be any recent tutorials on it that I can find. Maybe someone will see this thread and throw one together or maybe if the mood strikes me I will throw one together.

SSF is a little more forgiving with its images and mounting disks isn't hard with a batch file to mount the disk, launch the game and unmount the image when you close out there game. I don't think @SentaiBrad did a tutorial guide for it or not. The biggest problem is the fact you will have to install and use DaemonTools which you have to be very careful installing to avoid the adware it installs. I don't recall having to have cue + bin for SSF though Mednafen does. It's been a while since I have used SSF now and I have since upgraded all my disk images for Mednafen because it is much pickier over the disk images. Saturn emulation is more system intensive because of the systems complexity. The system was an awkward beast back in the day with 2 cpus and 2 video processors, even Segas own developers had a difficult time programming for it back in the day.

PS1 won't be a problem, Gamecube emulation with Dolphin should be ok but it could be on that edge but using the Ishiruuka build (https://forums.dolphin-emu.org/Thread-unofficial-ishiiruka-dolphin-custom-version) could get you there. Saturn emulation though maybe tricky depending on the emulator you want to use. Mednafen (both the stand alone and Retroarch core) will most likely be out of reach but who knows. You would be fine with the emulator SSF though but you will have the added step of mounting disk images which isn't a terribly big deal but is something to keep in mind.

No problem. Some off brand controllers may cause issues also if you have some other controller like a flightsick or wheel plugged in that can cause issues as well. I have a flightstick and that causes binding issues in some emulators.

No problem. Though I will still recommend puNES, it is extremely high quality and much more accurate than Nestopia. Also Nestopia hasn't been updated since 2008 while puNES is new and updated fairly regularly. Nestopia will play the vast majority of games just fine though of course but you may run into a few problematic games here and there.

Pick your controller from the drop down menu at the top right corner, then in the Mapping column double click each line and then press which button on your controller you want to map to that.

You will have to configure the controller in Options > Input.

Ok, I pretty much got it figured out. The command line parameter -fullscreen messes it up, remove that. Then open Nestopia and go into the Options > Preferences window and enable "Switch to fullscreen on startup" and "Autostart emulation" Exiting right now with Launchbox controller automation exit combo is still problematic for me but I am sure there is an AHK workaround. On a side note I would like to recommend the NES emulator puNES to you. It's a very good stand alone emulator and just as easy to setup and configure. http://forums.nesdev.com/viewtopic.php?t=6928

Is your NES platform on the left named Nintendo Entertainment System or is it slightly different ? I don't currently use the stand alone version of Nestopia but I will download it and see if I see anything with it while I wait for your response.

Can you give us a couple of screenshots of your emulator settings in Launchbox ? Go to Tools > Manage Emulators and then go to your Nestopia emulator, the Edit Emulator tab and Associated Platforms tab are what we need pictures of. Also are you roms in a zip file or no ?

To be fair, the original statement was "offer more features and more robust customization than the retroarch cores" which is where I disagreed but for the exact same reasons. It all depends on the emulator and core being compared.

It's not being defensive, I was merely saying that making blanket statements and calling it fact is bad information for users. If I said something along the lines of "Retroarch emulates everything better than stand alones" and then cherry picked specific cases where it actually is true while ignoring the ones that aren't that would be an incorrect statement and a disservice to people new to emulation looking for information to help them choose which is best for them. And if I had to sit here and go through every single stand alone emulator and its Retroarch counterpart to compare each and every feature this thread would become a massive mess in a hurry. I guess if me pointing out a flaw in someones point of view is me being defensive then so be it. I would rather be "defensive" as you put it and give people correct information rather than tell people things that are wrong.

If you remove the old set from Launchbox you can import your new ones and it will use the old artwork and metadata that is still there, removing the games from LB doesn't remove that stuff. You can have multiple sets, import under a new platform if you want to but then you will have to rescrape and download so that would take some time. I have 2 sets imported into my setup. One is a full set with all the mahjong and gambling trash excluded and the other set is a streamlined set of my favourite games. I did this before we had playlists and stuff.

Yes, it's actually very easy to setup. You don't need to setup a rompath like in the stand alone Mame. Just import your roms like normal for Mame in Launchbox and then have Retroarch for the emulator with the command line -L "cores\mame_libretro.dll" You can then use the core options to disable the nag screen and use the Tab key to setup controllers (if you want) just like in the stand alone.

I was having this issue on my HTPC, the way I worked around it was using Xpadder to set a controller button combo to do a mouse click to bring BigBox into focus. Not exactly an ideal fix but it was a work around though.

Enjoy and feel free to ask any questions and for help with anything you need.

Correct, you need an emulator to play the roms. Launchbox is just a nice way to organize, display and launch your games with ease.

No, you do not need to use Retroarch at all if you find it's not for your needs but if you want I have a written guide I did for it here: There are also tutorial videos for it on the Launchbox Youtube channel and we are always here to help you set it up if that is something you want to do. In the end use whatever emulator suits your needs best but as @fromlostdays said there are some benefits to using it and once you get past the initial learning curve it's not so complicated.

I never said that Retroarch was definitively better than stand alones in all cases, I merely stated that Retroarch in many cases have just as many options as their stand alone counterparts especially when you dig into the core specific options. There are 2 things outside of universal shaders and controller support that Retroarch has over their stand alone counterparts. Much better audio sync and input lag customization. You can lower the audio latency to suit your system and you can adjust V-Sync frame delay to reduce input latency which in some cases can be very noticeable. I am most certainly not going to sit here and nitpick and compare each and every possible core and stand alone emulator. Like I have stated many times before in other discussions of this topic elsewhere. Retroarch and stand alones both have their pros and cons and comparing the pros and cons is a legitimate discussion for people to have but sit here and definitively say that stand alone emulators have more options and customization is patently false. As you said, stand alone emulators may account for edge cases. Only a small percentage of end users will ever notice and care about these though. Most people want a more universal system and Retroarch provides this. Setup one emulator and it applies to the bulk of their systems with a nice shader (if the user wants that), quickly accessible save states and cheats (for the cores that support it) and superior audio and input latency.