SentaiBrad

Oh I missed that, I'm sorry. I swear I read it... and I just missed it. I'm sorry. Yea, they use MD5 for their check, and it wont get you the CRC, but you'll have a list to go off of. I do know there is a correct "RetroArch BIOS" pack out there too. You could always grab the pack and check against that.

Opening up the Core Info files will tell you all of this info, they're all in there.

Did you update to a beta yesterday morning / early afternoon? If so, Jason accidentally messed that one up and published a new beta to fix this.

Sweet, thank you for the kind words. It makes me happy that I've helped, and happy that you've searched out the answer. I don't know how many times I've answered this exact question.

If you're never gonna play them, in most cases, just don't import them. Because, if you download all media (images, music, manuals and video), then we're talking some potentially serious file space here. No to mention, if you've got even a slightly older computer, or you have slight performance issues (besides fixing up a ton of other things), Library File Size is the primary factor to any of that.

The + was just an example, but I figured it'd apply. My reasoning was that I do notice a lot of sets not using symbols where they can. So instead of seeing a + in the title name, the words Plus are used. I'm not too concerned about the rom sets, but I do like what No-Intro does. I don't like the idea of blindly conforming to one of those sets, because there are times where I and others disagree. Knowing that, would it be hypocritical to want to create a set of proper names for our Database? We'd just be another in a long line, and I don't know how well it'd work from within LaunchBox, meaning it's usefulness drops. If LaunchBox did it automatically, without error, that'd be great. But I don't see it happening without error without a ton and a ton of work. If a game has a character in it's title, then I don't think there's no reason to not use it. The beauty of the Alternate Titles, is that we can have both cases. In almost every case, the hyphen (-) will turn in to a colon on the Database side, so that should never really be an issue. When a file name should have a colon, it's almost always standard practice to use a hyphen. Should we create a standard conversion for other characters? For a slash, I can see the ampersand and + signs working. I think the ampersand looks cleanest. I'm by no means perfect when it comes to figuring this stuff out, that rule has been there for a long time and just got changed up, so I am certainly not above editing things to make them better. Figuring out what to do, now that's the hard part.

I made some changes to the guidelines, primarily rules 4 and now 5. I split up rule 4 primarily, and clarified it a ton. It was pointed out that it made little sense to someone new.

I'm the one who wrote the Guidelines. So Jason has the final approval, but has given me the day to day control on this one. I'm not above changing, adding or editing things, I've done that in the past a lot, but this has been set for a while. The forums has them pinned, the mega thread. They're not linked on the Database directly, but I'm trying to get that changed, and even get them in-line. So, per this issue, Alex is back working on the Database. I just had a talk with @Vlansix today. He's going to be working on Stability and the Bugs from the Bit Bucket. Past that, there is a short list of things, and they should be getting worked on. This is going to be apart of that short list. This is partly why I don't want to remove the games, because then someone needs to completely re-add them instead of editing a single value. Editing is easier than adding, but adding a ton of entries before the tools exist is a bit foolish. Hence the grandfathered approach; Anything that exists is fine, but lets not complicate things further right now.

If everything is crashing or not working related to a controller, but it's working for all of us, then I am leaning towards a Driver issue actually. Something seems wrong there. Big Box should never crash like that (and doesn't for the record), and RetroArch and PCSX2 are working. RetroArch does automatically config the controller for Xinput controllers. The Ipega controller won't most likely. For Big Box, you will need to go in, select the controller you're using (or check the box to use all attached controllers at once, which can cause issues with some drivers and arcade boards), and then set up the needed controls. Also, you need to touch the controller config for PCSX2; RetroArch automatically doing it is actually rare. Most emulators don't.

Oh, and for the record, EmulationStation is much more complicated to get up and running unless you go out and buy a pre-made box that is highly illegal. It's one thing to make a front end, which that's all EmulationStation does, and then it's up to the user to do the rest of it. It's another to go on ebay and sell boxes pre-loaded. Or, a friend helped / set it up for you, but the box resellers are a common plague in our hobby.

Of course, no problem! That is odd, but I have no way to explain that.

And yea, the deletion bug was never fixed it looks like. We need to know exactly what game you marked as a duplicate that was never removed though.

Because only one controller works in LaunchBox at a time, unless you check the box to use all controllers in the controller options. I remember there being an issue with the ipac though, if that button is checked. It could have been another arcade stick, but I want to say it was the ipac. With the use all controllers option checked, it would constantly try to keep scrolling with the ipac plugged in and that check box checked. If it's another arcade stick, then someone please correct me.

No, lets not mark them for deletion at all. Like I said, this is covered in the guidelines! Lets just leave them there for now, either they slipped in accidentally or are carry overs from the GamesDB days. They're fine staying for now, there's no reason to remove them, but we shouldn't actively be adding more to make the problem worse.

For setting up a controller in RetroArch, it's actually done automatically if it's a 360, Xbox One, PS3 or PS4 controller (the last 2 require extra software to work with PC's). So it's even more so, download RA, import games, download the core, make sure the associated platform is set correctly and go. Edit: I re-read the first post, and if you're having performance issues then something somewhere is screwing with Big Box. Once you've picked your controller, and set or left the keys at default it should work just fine. I would say that a few PC things should be done to make sure your PC is good to go first. Making sure Drivers and Codecs are up-to-date, as well as any Windows Updates. There's a few pieces of software listed here that should really help.

Ah, then if it's not even launching outside of LaunchBox, then it's most certainly a BIOS or bad disc image. In some cases, like N64 and PS1, since they're using different rendering engines in some cases, and things are wildly different, you need to have your settings set very carefully, and you can't use shaders. For most everything else, leaving things at default and it should work just fine, so if it is then that leaves the BIOS and Disc Images.

You need to bulk edit that they're even using an emulator. They by default don't use one because DOSBox is included with LaunchBox. I personally even replaced that with DOSBox Daum, as it's much better than that even. Using the RA DOSBox core is ok, but Daum and -x, and other variants, are much much better.

If everything is on the same drive then it'll use relative paths and you wont even need to make sure it's all on Z anymore. Going forward, leaving it all there will be best, but yea, the entire LaunchBox folder needed to move.

No, the default box only matters during import. I'm not sure how BizHawk handles things, so I can't speak to how that works. If something is not launching in RetroArch through LaunchBox, then a setting is off. It can simply be the names aren't matching, the right name isn't in the associated platforms page correctly, or the command line parameters are off. It could even be some of the check boxes or extra command lines that shouldn't be there (if you added any), the BIOS or the games could be bad, the cue sheet specifically could be wrong, it could be any number of things.

You didn't even need to install LaunchBox again, just move the old install to the same location it was previously, or even to a new location.

The guidelines have this scenario covered. For now, just leave it, but we can't add more to make the problem worse. The scope of the Database is for the released games first and foremost, but we want to have a place where Rom Hacks, Homebrews and Unlicensed games can live.

No, updating didn't cause this. I run 1.5 Nightlies just fine. This, if anything, is either an issue with the OS or LaunchBox, since It's not having anything to do with RetroArch. It's not reaching the RetroArch stage. Also yes, if you install LaunchBox on top of your current install you'll lose nothing. Are you on the latest LB Betas or Stable by chance?

If the emulator supports archives, you're good to go. Otherwise, you need to check the box when you edit an emulator to unarchive things. I personally hate archives, and I have nothing like that in them. I still use compression on stuff, just not archival compression. If you're curious about ditching archives but still needing space on some systems: Not using them is all me though. If you still want to, then go ahead, but for RetroArch you'll need two entries. One for consoles that aren't archived or don't need to be unarchived, and then an entry for games that are archived and need to be extracted.

It's not a particular priority for us at the moment. It will get added, but it's not currently high on the list.

I'm not sure. For Neo Geo I would just use MAME, and not inside of RetroArch at all. Past that, for NES, no BIOS are required. Making sure the Core is downloaded from within RA, make sure the command line is set properly (the Platform Name and the Command Line parameters (Platform Name in Associated Platform must match what you've called your platform)), and all of your games are using RetroArch as they're emulator. That's realistically all you should need to do.