DJQuad

http://www.rlauncher.com/forum/showthread.php?2803-Best-Emulator-For-Each-System might help!

Oh ok, I thought you had the list already, but it wasn't incorporated into LaunchBox just yet. :)

When I asked about the list I was asking if you could share it in the meantime so those importing stuff don't have to wait. :)

progets said @DJQuad - If you're migrating from HyperSpin why wouldn't you just use your existing RocketLaucher setup? If it works in HyperSpin it will work in LaunchBox. I probably will for my setup, but I'll be helping friends starting from scratch who don't use it. Do you know if the plugin was created? I know they were close.

SentaiBrad said Yes, we are working on changing the default emulators. Those haven't been updated in about 2 years. Do you have the list already made?

So one thing that really confused me when importing ROMs was the suggestion of the "best" emulator for that system. I can't remember the exact system but I think it was Nintendo. It was suggested that I use an emulator like Nestopia, but why? Both MAME and RetroArch run it perfectly fine as far as I know. Another example was that I install VisualBoyAdvance. That is literally one of the worst emulators I have ever tried to configure. I'm not a huge fan of RetroArch and would personally rather not ever deal with their confusing UI, changing cores, incompatibility with the features they brag about, etc ever again. It's not at all clear what should be the ideal setup for LaunchBox should be. I have G:\LaunchBox\Emulators\MAME 0.174, G:\LaunchBox\Emulators\WinVICE-2.4-x86, MAMEUIFX 0.173, MAMEUI 0.173 (that includes MESS 0.172), RetroArch 1.3.4, Atari800 3.1.0, ePSXe1925, kat5200, and so on. Vanilla MAME was also suggested, which includes things like nag screens, no direct input, etc. It's a freaking mess. Even Jason suggested to change the default. It's so confusing.

progets said HyperSpin doesn't use box/flyer art in its front end. If you have a complete RocketLauncher setup these files can be found in D:\RocketLauncher\Media\Artwork\MAME. They are laid out in a different format and won't be easy to use directly with LaunchBox. Many people store the MAME artwork directly in their MAME installs which can easily be mapped to LaunchBox. Yeah the biggest issue is the videos that take up the vast majority of space. I have a complete (or at least I thought complete) RocketLauncher setup, but I don't have an Artwork folder under Media. I really wish they'd build in options to make the migration process easier because the vast majority of new people are from the HyperSpin community who have their media folders completely sync'd.

Thank you progets, I've spent the last couple hours trying to determine where HyperSync puts everything. I wish there were some sort of variable since the system is the only thing that changes both with HyperSpin and LaunchBox. I think putting the paths in Manage Platforms would be easier than using old school sym links ;) but at least I know the appropriate paths now. Thanks again! Also, MAME doesn't appear to have any box art. HyperSpin\Media\MAME\Images\Artwork3 is empty. Their ArtworkX folder structure makes no sense whatsoever.

Thanks for the reply Brad. Most HyperSpinners already have premium licenses to both HyperSpin and Emumovies. The vast majority are now evaluating LaunchBox and some have already have licenses for BigBox. They aren't ready just yet to make a complete switch so moving and/or copying all that media to the ideal LaunchBox locations will either break their existing HyperSpin, or waste GBs of HD space that not everyone has. Some HyperSpin installs are upwards of 4+ TBs. I'm not sure how familiar you are with HyperSync but this is basically the structure of the media folders both with HyperSpin and RocketLauncher from my system. https://mega.nz/#!7MlyjCaD!ZHJb1nCaf78Vw5UnJWqgNruOAsIqJ-4hmlBXJPg18FI

So a lot of us are migrating from HyperSpin and have everything already sync'ed via HyperSync. In my case I only have about 20 systems setup, and my media folder is over 23GB. I read that you can change media paths, but for the initial ROM import, do we deselect everything as far as box art, screenshots, logos, as well as everything in the Emumovies dialogue? I'm not sure where HyperSync puts everything so I'm a bit unclear what these paths should be set to. Keep in mind that many are transitioning from HyperSpin and do not want to duplicate media in the process. The easier and more automated the devs make it, the more people will make the leap.

Not the biggest deal from a security standpoint as it's very tricky to exploit, but to be safe everyone should update their version of 7-zip (7z) to at least version 16.0 and recompress all 7z files with the patched version. http://www.zdnet.com/article/severe-7-zip-vulnerabilities-cause-top-security-software-tools-patch-panic/ http://www.bit-tech.net/news/bits/2016/05/12/7-zip-vulnerabilities/1 http://betanews.com/2016/05/16/7-zip-major-vulnerabilities/ This is one bad side effect from open source. When something is popular the bad guys pour through the code for ways to exploit it.