PurpleTentacle

Thanks for the reply. That's kind of a shame as I really enjoy keeping everything as portable as possible, but sometimes you just gotta live with hard limitations.

Thanks, my plane is to go in & test out which files are not compatible, and then import those separately so that it points to the MAME files that are compatible. Once I get it set up, I'll just leave it until I'm ready to update both.

This config worked for me after I replaced your file paths with my own, so I greatly appreciate it! Is there any way to point the file paths to in a way that keeps it portable? I.E. instead of "ROM_OS_A_PAL=H:\LaunchBox\Emulators\RetroArch\system\ATARIOSA.ROM" it would be more like, "ROM_OS_A_PAL=\system\ATARIOSA.ROM", similar to how RetroArch does in their config files...

I understand how MAME romsets & the romset/MAME versions work (I.E. you match the version of MAME with the romset version that you're using), so I only upgrade MAME when I upgrade my romset (I'm using standalone MAME by default with the MAME RA core just as an option in LaunchBox)... But when it comes to the FB Neo core in RetroArch, I'm not sure when I should stop upgrading the FB Neo core so that I don't overshoot the MAME romset version that I'm using (currently MAME .233). I only update every now again, so I'm not planning on staying on top of the MAME romset. I should mention that I have 2 Platforms for arcade games in LaunchBox - the default Arcade Platform uses standalone MAME as default, and a Platform that I named, "Arcade - Final Burn Neo" which uses RetroArch's FB Neo core as the default. They both point to the same romset to save space (as well as the same image & video folders), and I'm planning on seeing which games require some kind of prepping to use in FB Neo so that I can point the Final Burn Neo Platform entries to those specific files. Just out of curiosity, does Final Burn Alpha (the RetroArch core) work in a similar way in terms of matching the core version to the romset version? I have the FB Alpha core as another option (I.E. right clicking on a game and selecting "Launch With...", just so that it's there).

Oh, good to know! I'll check it out as soon as I get the chance. Thanks!

Hi, recently decided to redo some of my platforms after noticing that I was missing a few games or was using the PAL version on a few games... So I used the No Intro romsets for NES/SNES/Genesis, and I've noticed that it often chooses the beta version of a game as the default version to launch with. Currently, I'm fixing this by making auto populated playlists for each system with the condition of "contains beta in the rompath" as the prerequisite, that way I can see only the games that are using a beta version, and then I go through them individually & choose the release version (unless, of course, when the beta version is the only version). Does anyone have any tips for how to do this more efficiently? Obviously, I could remove the beta versions when importing the games, but I like the idea of having the beta versions as an alternate launch option. I'm also wondering if there's any way for LaunchBox to not parse games that start with "The" in the title by placing "The" at the end? For instance, "The Lost Vikings" changes to "Lost Vikings, The". LaunchBox ignores "The" at the start of a title anyway, so I just prefer for it not rearrange "The" (most importantly, I moved my image & movies folders from my previous installation, so any game that starts with "The" doesn't match with the image & video filenames. It works once I change it, so it's fine, I'm just looking for a more efficient way to do this.

1. What's the best method to update LaunchBox's copy of ScummVM? When I tried it on my backup copy of LaunchBox, I tried opening up ScummVM & then clicking "Options", followed by the Misc tab, and choosing the "check for updates now" button... But that downloaded an installer, and I'm assuming that's not good. Do I download the portable version, and just drag & drop the files on top of LaunchBox's ScummVM? Is that safe, and will it still work with EpicFail's ScummVM Launcher? 2. As far as EpicFail's ScummVM launcher, it's working great for me at the moment, but for some reason, the DOS versions of King's Quest V & King's Quest VI aren't working. The Windows versions work, but the DOS version never opens. Here's what I have for the bat file for the DOS version of KQ VI: And this is the bat file for the Window's version of KQ VI: I'm just wondering if there's a command line that's needed to get the DOS version running. Any ideas?

Oh! Glad to see this, as I was trying to figure out how I wanted to approach this. It's one of those things where I like having both options, although I might end up preferring using RetroArch as the default. I love how easy it makes setting up controllers & such, although I'm still trying to figure out how to bind specific keys to my controller (this is using the controller to act like a mouse & keyboard, with the left analogue stick being the mouse).

I did actually end up buying it, and I love it! I haven't had much use for the advanced features either, but in the end, that's because it does everything I require from it anyway. It's definitely the best of the 8bitdo controllers (the Sega Genesis 6 button style controller is fantastic as well, but it fits a different niche, so I can't compare them directly).

I actually found a better way. If you look in the \RetroArch\autoconfig directory, you'll notice other directories, the important ones being "dinput" and "xinput" (depending on if you have your controller set to dinput or xinput). In each of those directories, you'll find files named 8Bitdo_M30_BT.cfg & 8Bitdo_M30_USB.cfg. That's where it stores the key binds for the controller, so from there, it's a matter of matching up the button numbers with the buttons you want them to be. This, for instance, is what I have set for 8Bitdo_M30_BT.cfg: The tricky part is that the default keys in RetroArch need to be set to "auto", or else it won't use those. Unfortunately, I can't remember how to set it to "Auto". It was something like going into the RetroArch Input menu, and then "Save autoconfig", and then you have to save the default configuration file under the "Configuration File" menu. (the retroarch.cfg file). Lemme know if that works, if you try it out.

Thanks for the response. I'm considering making a work-around, something like making an identical Platform with a different title, but that points to the same roms & images/videos, so that it doesn't take up any extra hard drive space (with the only difference being the Platform title & default emulator). It worked well for separating my Arcade & Console versions of Neo-Geo games without having to have 2 copies of each.

So I do have an official version of MAME, but I use RetroArch with the MAME core as my default, with the official MAME as an alternative option. The high scores don't show with this setup, but I tried making a backup of my Launch Box collection & switched the default emulator to MAME, which allowed for the option to view the high scores to show up. I also noticed that it uploaded my score when using the Launch Box setup where MAME is the default, but it didn't work on my Launch Box setup when using MAME as an alternative. I assume MAME has to be the default emulator for this to work? Is there any way for Launch Box to recognize that MAME is there when it's not the default? Would really help me, since I like to use RetroArch as default across platforms to keep the hotkeys & general UI consistent (and I've yet to figure out if there's an easy way to switch which monitor is being used in MAME, outside of using command lines). Also, for some reason, I couldn't get Burger Time to run using the default version of MAME, but it runs under the RetroArch MAME core, so I'm not sure if all my games run under MAME (I'm using the 0.217 MAME romset & the 0.217 version of MAME, so I'm not sure why it's not running, but that's a separate issue that I'll have to look into). Of course, I'll understand if this isn't feasible due to whatever checks Launch Box has to make to verify that a valid version of MAME is being used...

Good to know, thanks!