Zombeaver

Yep, it's actually really simple. All you have to do is create a text file with the name of each of your .cue files, in order, one per line. So, for example: Enemy Zero (Disc 1).cue Enemy Zero (Disc 2).cue Enemy Zero (Disc 3).cue Enemy Zero (Disc 4).cue Then save it. Now you just need to rename the file and change the extension from .txt to .m3u and use that .m3u file as your "rom" in LB. In Retroarch you'll need to assign keys to the "open/close tray" function, "next disc" function, and "previous disc" function. These have default keys but I changed them so I don't recall what they are. I changed mine to 0 for "open/close tray", + for "next disc" and - for "previous disc". So if I want to change from disc 1 to 2, all I have to do is press 0 (open), + (next disc), and then 0 (close). At that point you can continue playing normally. Keep in mind, like I said, this doesn't quite work yet for Saturn. It works beautifully for PSX though. This is how I have all of my multi-disc PSX games setup.

Yes, WBFS is it's own file system (that's actually what the "FS" stands for) just like FAT32 or NTFS that's not natively readable by Windows. That's what WBFS Manager is designed to do.

Yeah this is actually one of the first things I tried. It doesn't work currently in either standalone or RA. m3u support is sortof there but only in a preliminary state. The first disc will load when loaded via m3u, but in RA you can't actually switch to a different disc and in standalone you can switch but the graphics are all screwed up afterwards. I think it's just something that's still being worked on. Enemy Zero is a good game to test this with, for reference - the first disc is literally just an intro cinematic.

No problem!

Like I said just add Big Box as your non-steam application and launch it from Big Picture. Once you're done playing a game it should take you back to Big Box and once you close Big Box it should take you back to Big Picture.

ScummVM could obviously use some streamlining. You have to build each entry basically from scratch. I'm actually working on Amiga myself at the moment. I don't use a loader though - I just use regular old WinUAE. The method I've been using is to just load the disk(s) into the swapper, tweaking any game-specific settings I need, saving it as a config (.uae) file, and then importing the .uae file as the "rom" in LB with WinUAE as the emulator. It works fine but it is time consuming. I honestly don't think there's any way that LB could improve this process though, since nearly all of the work is taking place in WinUAE itself. By the time I get to LB in this process I've essentially got a single rom file that works with an emulator just like any other rom+emulator combo so the LB import itself takes about 5% of the total setup time. Regarding the specific question above about proper names upon import, if all of your games are in separate folders by title you could tell it to use folder names instead of the file name. I have all of mine in separate folders as it helps organize the separate disks. This probably isn't the case if you're using a loader though...

How do you have things setup to launch exactly? I have Big Box itself as the "non-steam application". From there you can launch whatever you want (in Big Box) and it'll go back to Big Box afterwards.

You shouldn't need to do any of that so long as you're incorporating the core you want into your Retroarch emulator entry in LB. If you want to use FBA for NeoGeo, you just need to open your Retroarch emulator entry in LB -> associated platforms -> find NeoGeo in the list (or add it if it isn't there already, though I think it should be by default) and add/edit the command line parameter field to be -L "cores\fba_libretro.dll" (there are actually several different FBA cores, so double-check your core dll file name in your Retroarch -> cores folder. Whichever one you want to use needs to be in the command line parameter field after "cores\". After that just add Retroarch as the emulator (if it isn't already) to any relevant games in your library.

According to this post the files should be named as either (Disc #), (Disk #), or (CD #) so, based on that, the ones in brackets might not work (though it might not care what the special characters are, I'm not sure) but the ones in parenthesis definitely should. Drybonz seemed to be experiencing some issues with it as well.

No it's totally understandable. People should be able to organize their own library however they choose (and you still can) we just have to organize things in such a way that they're manageable and so we don't end up with a bunch of duplicates that have to be separately maintained/moderated. The single entry separation is somewhat in place at this point - take a look at the the Contra III entry for example. You can see that the NA, PAL, and JAP covers are all there, and have signifiers for the region (hover over them and you'll see "North America", "Europe" and "Asia") but we don't have region-specific names yet (Super Probotector in Europe). That's being worked on though.

The idea is to still include the differences (including things like region-specific names and unique artwork) but within a single DB entry. It's not quite implemented yet, but with one entry they'll be divided up to still have all the information you want (in it's own subsection), just not spread across multiple "duplicate" DB entries. You're still going to be able to do what you want to do, don't worry. And you can still divide your own library in LB however you choose.

This just in, gifs work in the new forms (maybe they always did, dunno)

Yeah I used it for Neuromancer. It has a complex copy-protection method that uses combinations of keywords to determine the appropriate passcode. There's a website that has all of the combinations. I was trying to figure out how to include a link in the note description but then I just thought "I wonder what would happen if I just threw this URL in the application path..."

I'm sorry if anyone was offended, as that wasn't my intention, but I won't apologize for voicing my opinion, even if that opinion puts me at odds with anyone (or everyone) else. It's not much of a discussion if everyone agrees. If that dissent was conveyed too forcefully, well then my apologies. I just thought the joke was a bit inappropriate to be honest. Rob seems like a good guy. We chatted for a bit and everything was civil I'm very open to suggestions, honestly. I'm not dogmatic - obviously there's always room for improvement, and those potential improvements should be encouraged. I encourage people to post their ideas on feature requests on Bitbucket almost daily. I won't blindy agree with/endorse anything though, and if it's something I disagree with, I'm going to say as much, and in detail (I feel like you have to otherwise it's just being argumentative for its own sake). That said, I'm strongly opinionated and yes, as Rob put it, passionate; passionate because this is a product and a community that I care about and want to see thrive. Sometimes that results in more vehemence than is necessary or, honestly, intended.

Mmmmkay. What you should feel like is someone who burst into someone else's birthday party and said "Chocolate cake sucks. I want carrot cake".

Which is precisely what LB facilitates already. Which is precisely how RA works currently. Want Genesis support? Click a button. Decide you don't want it? Click a button. Now I see why you're proposing this in the first place... Again, all of the sort of wide-ranging catch-all support that you're looking for is already present in Retroarch. If you're having trouble getting it setup, that's what we're here to help with, and we're happy to do so, but suggesting a complete and fundamental reworking of how LB is structured because you don't understand how to use Retroarch is a stretch in the extreme. I get wanting a simplified solution. I get wanting to just hit a button and it work. Believe me, I really really do. But what you're suggesting just isn't going to be beneficial (or likely even feasible) in the long run.

I can't say I agree with much of this to be honest with you. The beauty of LaunchBox is its modular, do-what-you-want-with-it nature. You could literally use it as a front-end for... anything really. It doesn't even need to be emulation related, despite that being the obvious focus. That freedom is a strength, not a shortcoming. Flipping that on its head and saying that it needs to directly integrate emulators provided by various and sundry developers does literally nothing for it. Because you know what that's called? "Bloat." You can plug (or not) whatever you want into it. You laud OpenEmu for not having individual modules per platform as if that's praiseworthy, but I would argue to the contrary using your own example... how many people do care about emulating a Fairchild? So what, the fact that they get it regardless is somehow beneficial? What? We already have Retroarch as the sort of catchall solution you're talking about and it integrates just fine into LB. Also, $25 a year? Have you actually spoken with the audience that you're proposing this to? I'm not saying there aren't people out there that would agree to this, hypothetically, but generally speaking this is a pretty insane notion. EDIT: Also, everything @lordmonkus said

I've never used it either, but I did some reading on it and the feature list for it specifically mentions "bulk extraction and deletion".

Yep. It's called WBFS Manager.

You need to extract them via WBFS manager. There's obviously a way to do this for the .WBFS files themselves (not just converting to iso) because people use individual WBFS files in Windows in association with Dolphin. The specific instructions for doing that isn't something I can help with because I've never used the manager. It's not something you'd be doing though LB - it's with the manager.

On the description for WBFS Manager page one of the features is "batch extraction and deletion". That's probably where you need to start.

I don't know what to tell you. WBFS is a file type that is usable in association with Dolphin via Windows. There has to be some way to extract them. That's not an LB question though, that's a WBFS Manager question. Beyond that you could look into launching them via special command line parameters. Right, but he apparently can't get to them/see them on the hard drive where they're stored...

It is a file type. It has a standalone manager as well though. Newer builds of Dolphin support loading games of WBFS file type, just like any other emulator supporting say .zip.

Well you have to have something to associate your game entries with. My knowledge of WBFS specifically is limited, but don't you have individual files for them? If so, I'm not sure why you'd need to do anything "in WBFS". You should be able to just drop in the WBFS files and tell LB to use Dolphin as the associated emulator.

So what is happening when you try to drag them into LB? LB doesn't actually care what the file type is - it'll categorize them under whatever platform you tell it to (in this case you'd just tell it that you're importing Wii games).