neil9000

This can be adjusted in the options.

Just go to tools/manage emulators, double click your MAME entry and use the browse button to point to the MAME 0.202 exe instead of where it is currently pointing.

1. If you only have the one platform you can set Bigbox to open into the "All" category in the options. 2. Again in the options is a option to "Skip game details screen" check that and it will load straight from the wheel. 3. In that options menu is a "Lock" option, you can set a pin and lock out specific options so they need a pin entry to change in future. Hope that helps.

Just because Retroarch recognises the controller on launch doesnt mean that that is what it is actually using, it just means it knows it is connected. Like @DOS76 said you need to go to settings/input/user 1 binds and make sure that controller is actually selected there for use. I use a XBOX ONE controller with the official Microsoft wireless adapter and it works perfectly in Retroarch.

You are right clicking the game and then choosing PCSX2 Configurator at the bottom of the list right?

Download them from here, https://forums.launchbox-app.com/files/category/7-big-box-startup-videos/ And place them in Launchbox/Videos/startup folder, if there isnt a startup folder there just create it, you can put as many videos as you like in this folder and Bigbox will play a random one each time.

Bigbox takes as long or as short a time to load depending on how many systems/playlists you have, the more you have the longer the load. My Bigbox with around 10,000 games and no playlists loads in around 5-10 seconds. You cant really compare it to how long hyperspin takes to load as they are built on completely different platforms and therefore have different assets to load. I suggest getting a startup video to cover the load, and there is a splashscreen when Bigbox is loading that can be toggled on/off in the Bigbox options.

What theme are you using?

Cool, glad you got it sorted.

Yeah, you really only have two options with MAME. 1. Get a set and stick with it by not updating the romset or emulator version. Or. 2. Update every month and keep on top of it and update the emulator every month as well.

You will need it, 0.206 will only contain the changes from 0.205 to 0.206, not any changes that were made from 0.204 to 0.205.

There are references to the SteamLauncher plugin in that error. Try copying that plugin out of the plugin folder and see if it helps.

Options/Videos/Prioritize game theme videos.

Yeah, thats why we have a value for alternate names in the database, exactly for times like this when there are two games with the same name on the same platform, and the alternate name on the database page is, Biohazard :RE 2

OK, i just checked and i was getting the same. How i got around it was by putting in the Japanese name, so, Biohazard RE:2 When i did that it found it and automatically renamed it to Resident Evil 2.

Are you using CTRL A to highlite all the games in a platform first?

Drag the shortcut onto the launchbox window and choose the "none of the above" option in the import wizard.

If you have the 0.202 MAME romset then use 0.202 of the MAME emulator. Also depending on the romset type you have you may be missing the bios files, the non-merged romset contains all the bios files inside each game zip, the other two merged and split may not have those bios files in the romset at all. I can confirm that all the 1940 series do indeed work providing your romset is good, are using the correct version of the emulator and you have the bios files.

When you say you are using 0.64 do you mean that you are using the 0.64 romset, or do you simply mean you are using MAME64 as the emulator?

Drag the shortcut onto the Launchbox window to start the import wizard, choose the "none of the above" option so that it is not associated with a emulator and name the platform the shortcut is to go into.

Thats why we never like people buying pre configured drives, if something goes wrong you have no knowledge or experience to fix it. The reason changing the emulator from rocketlauncher to snes9x is not working is because you need to bulk edit the actual roms in that platform to use the new emulator. At this point though with you not understanding how it is put together and what does what i think your best bet would to be to start from scratch. We have excellent tutorials on our youtube channel.

Depending on the romset you have it may or may not include the bios files. You say you have a 0.205 romset, are you using the 0.205 version of the MAME emulator? and what romset type do you have, Non-Merged, Merged or a split romset.

Chd's should not be zipped, they should just be in there own folder with the CHD inside. You just need to unzip them and they should automatically go into the folder with the correct name.

Yeah, Launchbox doesnt touch the Retroarch config files ever. All it does is pass the rom you have selected to Retroarch via commandline, it's not even aware of the config files or how to alter them even if it wanted to. So something got changed somewhere along the line, but not by Launchbox/Bigbox i'm afraid.