SentaiBrad

It's also worth asking what the size of your library is, how many images and videos did you grab, if your install is done caching, and if you have a GPU. Your GPU isn't a slouch for mobile, but it's still a mobile CPU, and if you don't have a GPU, then the more and more you add to your library, the more and more it needs to load. If you only have a CPU, then the CPU is doing two jobs at once instead of 1. It's also worth noting that a GPU plays a bigger factor in to Big Box than it does LaunchBox.

Not checking for all games specifically I don't think, at least I'm not sure if that was originally intended. There is a lot we could do with Audits though, and this would be pretty cool and something I am sure Jason would want to do. However, since we're rom set agnostic, what do we check a full list against? How do we make sure the check is accurate? Those are legit questions, not trying to say this wont or couldn't happen.

You could drag multiple shortcuts and it will import those through the import wizard, but you'll need to bulk edit the emulator off. You'll need to assign one temporarily. You could also use the regular Tools -> Rom Import, go that route, point it to a folder of shortcuts and bulk edit the same setting.

Creating a private server is extremely difficult and can be very costly for the proper hardware. I wouldn't doubt one exists for this game for Real Dreamcasts, but not for emulators. The best thing is to grab PSO Blue Burst for Windows. It was the final re-release for the game and has private servers running.

If you're using a Merged Arcade set, that's why it's not assigning the proper region. Merged doesn't work well at all when importing in to LB. You'll need split or non-merged only (non-merged for .182 since split for .182 seems broken, but split for .174-.181 works).

Now if it's not doing anything, then now the command line could be bad. If you downloaded the core, make sure the default command line parameter in associated platforms is set to your core, and make sure the system name matches the name you gave the system. If that's all correct, then it can also be the BIOS. Bad BIOS for every system (bad game rips for that matter too), are all over the place.

Or the games are using a different emulator. That error says a path is wrong. Click a game in this platform, Ctrl + A to highlight them all, Right Click -> Edit, choose emulator from the first drop down, then from the second drop down choose RetroArch. Thats how you change the emulator they're using. If it still says that, then change the path to RetroArch in the manage emulators screen.

The Windows Import is a bit locked down, but you can drag and drop the exe in to LaunchBox or press add in the bottom right corner if you're mostly concerned about this one game.

If the upgrade to an i7 is there for not much more (I wouldn't drop the K component though if you're worried about overclocking), then I would look at those options, but otherwise it is a good list.

If nothing even loads, make sure that the command line is set up properly for RetroArch. Make sure the Associated Platform name and default command line are set up properly.

I only have GDI's, so I am unsure. I have other systems that use CHD's, all in the same emulator, with the associated platform command lines all different, and the demul settings the same. Everything loads up off the same settings. GDI for dreamcast, CHD's and zips for everything else.

Do you have the proper platform names? If not, change the platform names or set up the scrape as to the default system names. PS2 certainly has metadata, and if you called your platform FBA then you'll also want to scrape that as Arcade.

Are your demul settings set up properly? Do you have the proper default command line set up? In this image the only line that matters in this case is the Dreamcast line. Make sure the Associated Platform Name matches your platform name as well. Here are my Demul settings as well:

Probably because most people don't know it, or don't want to do it. NTFS Compression will be the easiest method and save you some space, and you wont have to re-import or change paths. Are you having an issue with getting the CHD convertor to work or haven't tried yet?

InputMapper has some issues with Windows 10, but it's extremely easy to solve: Close down Steam and plug in the controller. Every time I have an issue with that, that's all I do. As well, they updated several times to help remedy some of the issues, and have systems in place to help it, but it can't be solved completely by them as it was Microsofts doing. Glad you got it fixed up though!

What file extension are your games?

The rom directory needs to be pointed at your full list of roms, no where else. Just put the rom set in the mame/roms folder, that's where it looks by default, and when importing tell LB to look there. Otherwise, did you try putting MAME in a different location / hard drive? Have you tried another PC?

It sounds like you're missing pre-reqruisites. MAME Is much more complicated than grabbing a few roms. Sure, that can work sometimes, but it's the hardest. Check to see if your roms have any parent roms or BIOS that are required. The easiest method would be to grab MAME .181 and a MAME .181 Split Rom Set, or MAME .182 and a MAME .182 non-merged rom set. In the sets are all the required parent and child roms, and all the required BIOS. With the MAME Importer, LaunchBox will import only the games you want based on your preferences. A split set will be fine from MAME .174 to MAME .181, but you want the latest for more games and more features. .182 split seems to be broken, so a non-merged set is best for compatability. Merged sets do not work as intended in LaunchBox, so ignore these all together if you want them easily imported. For extra help, check out the MAME Tutorial. It's a bit older, so replace the version numbers in this tutorial with the ones you want, and ignore the extra program as it's out of date in that video and completely different now. Otherwise, it's still completely valid.

I use gdi's actually, not CHD's. At least for Dreamcast. I would try NTFS Compression for them and see if you get a good enough decrease. Like other compression, it can lead to slower load times, but so can a CHD I believe.

If the forums don't let you, change it.

There are some good CHD games. It's mostly when we start getting in to later Arcade games where CHD's become most prevalent.

I built my PC for about $1k and it plays everything I throw at it. I'm about to up it's GPU as well. If you're comfortable building a PC, and have a part or two lying around that you can use to cut some costs, building one for fairly cheap is easier than you think. If you want to play all the latest games for the next year or so at good quality, you want all recent hardware, there's no way around it. If your goal is to not play the latest games at high graphical intensities, but games that work on a cab and emulation, then you can go back a few years and still be just fine. An i7 from within the last 2-3 generations, a GTX950 (you can go higher or lower, but the older series are harder to find, and the 950 is fairly powerful for the price, but a GTX1050 / 1060 are more powerful and not that much more expensive), a decent motherboard that has dual channel ram, preferably DDR4. The motherboard you get will determine the CPU you can use as well because of the socket it has on board. A good amount of RAM, I would say at least 8GB would be good, that way the OS has it's 4 available to it. With some services cutting and making windows lean, 8GB can go far, but 16-32GB would be best in the long run, though you really don't need 32GB unless you want to run the latest games and maybe do some intense applications. 8-16GB I think might be the sweet spot. 12GB works, but finding 2 6GB sticks is more odd, 4GB and 8GB sticks are common. As for the drive, an SSD for the OS and a 7200RPM that's as big as you can afford. 5400RPM will work too, loading times in game nor transfer speed will be affected all that much. It will mostly effect seek time and how long it takes the drive to pull up from after turning it's self off (which will happen after a time it's not being used, even with the PC on). I found an 8TB drive, but it was 5400RPM (the 7200RPM ones were either non-existent or much more expensive), and this drive is perfect. You want to prioritize in this order (for LaunchBox and emulation), CPU, GPU, RAM. You ideally don't want to slouch on any of them. i7 4k, 5k and 6k series CPU's are the ones you want to go for. The 6000 series might be too expensive, and the 4000 and 5000 series might be more affordable, but obviously you lose some power the farther back you go. It's also dependent on your Motherboard. Depending on the socket, say it only takes a 4000 series, if you don't buy the top of the line in that series, you'd be at your limit right away and need to buy a new motherboard and cpu to upgrade, then your RAM could also potentially be out. Find a decent motherboard you like, with features and ports that you need, then see where the RAM and CPU lie. The GTX1050's and 1060's are certainly not the top of the line, (that would be the currently released 1080's and soon to be upgrades), but they're affordable, and much more powerful than previous GPU's.

There isn't a category for it, but it could work under Banners. At least that's what I would do. If you want to request another category, open up the LaunchBox Games Database BitBucket (the Issues/Requests at the top of the Database, not the forums), and let Jason know.

Right, I have been wanting to do a show like that actually. No promises, but I'll talk to Jason about it and see what he thinks as well.

I'm a bit confused, that's not a video suggestion. If you're having issues with MSX I created a tutorial and it doesn't matter (if I recall properly) the extension.