neil9000

Turn on attract mode in the Bigbox settings.

Launchbox was completely re-written since 7.6 so i can pretty much say with certainty that it wont work, of course you are free to try it for yourself.

Yes, load the game, change the settings you want then save it as a game overide in the quick menu.

This is old and obsolete information. You can now have as many startup videos as you like, and named as you like, just place them all in Launchbox/Videos/startup folder and a random one will play each time.

I have just installed the latest dev build from 12 hours ago, and games are launching just fine here with the -b -e, i dont see the UI at all.

Ah OK, yeah thats the issue then i'm afraid. Launchbox does not currently have support for software list roms, i believe it is planned for the future, but currently it will not be able to match games to the database very well due to them using the MAME short names rather than conventional naming.

You are calling the system Colecovision right? It should find all the games just fine, at least it did for me when i imported them. So unless you have poorly named roms then they should import just fine. Or are you using MAME software list roms?

Mine has the framerate in there.

Its in your MAME folder, but you can also do it through the UI, just load MAME without a game and go to configure/Directories/Roms and point it at your romfolder. Then back up a couple of screens and be sure to "save configuration", before closing MAME.

I use it in dinput mode also for MAME, i leave it plugged in all the time, and it conflicted with normal PC games when in xinput mode as games would default to that rather than my xbox controllers, so i always had to unplug it when playing PC games. Keeping it in dinput mode fixed that as PC games generally look for a xinput device first not a dinput one.

I have the F500, i keep it in dinput mode and Retroarch recognizes it as the mayflash F500 when Retroarch loads.

I dont emulate model 3.

This is a emulator issue and nothing at all to do with Launchbox/Bigbox.

The current set is on "pleasuredome", but if you get a older set from somewhere like the internet archive, just get the MAME emulator version that matches it, then the game that are working will work. Its worth noting that there are thousands of games in the fullset that do not currently work in any version of MAME. If you use the Launchbox fullset importer and leave the filters at there default it will only import working games.

As a example the three files your Captain America says it is missing i have in my rom, i have a 0.208 romset and emulator, so it looks like files have been added to that rom since whenever your version is from so will not work in the current version of MAME. As my rom version and emulator match that game works just fine for me.

This is exactly the reason you need to for the most part keep your roms and emulator versions in sync. The actual game roms change when they get better dumps, or when a specific part is emulated more accurately, or when some encryption is broken etc. so a version of a game may break from one version of the emulator to the next, as both the rom file and the emulator itself have changed, and the MAME emulator knows exactly what files should be present in the rom files for that exact version of the emulator, and obviously looks for and loads those files, if the files you have do not match the game will not work. Also its worth pointing out that picking random games from random places on the internet is a awful idea. Not only do you not know which MAME version it is from, and therefore which emulator version to use for it, but there are three different versions of romsets, merged, non-merged and split, and depending on what version your random rom is from you could be missing a ton of files for that game. This is because MAME works on a Parent and Clone basis, a lot of games ran on very similar hardware so there is no need to have every file needed in every game rom as that is a waste of space, so they make one game the "Parent" which has all the needed files and the other games only include the files that are actually different from the parent, so MAME actually looks for two roms in those cases, the actual game you are loading, and the parent that includes the bulk of the data, if you dont have that parent then that game is going to fail with missing files, like in your images. The only exclusion to this is the non-merged roms, as each game there contains all the files needed for that game to run, but when downloading random game files you have no idea whether its a merged, non-merged or split rom, or from which version it is meant for. Also depending on the rom types you have they may be completely missing bios files which are needed for games to run. These bios files also change over time so you cant just grab any version, you need the versions for your version of the emulator. Recent examples of this are the qsound bios for capcom games and the neogeo bios. If you have a old version of those you cannot use a recent version of the MAME emulator.

The same way as any other file type.

It is in the Launchbox MAME metadata.xml, but it is marked as "imperfect" rather than "working".

OK i do have it in my roms folder and in MAME it says that it is working but with sound issues. However when i try to launch it from MAME it crashes to desktop.

I have a full romset and i do not have that game in Launchbox. Is it possible it went under another name also and that it needs a parent rom?

There would need to be a database of every game ever released and what controls it used, so i dont see that ever happening i'm afraid. You can already do this in Launchbox. These seem more like emulator features, so therefore out of the scope of Launchbox.

This thread is old and your information is obsolete, as STEAM has native support for PS4 controllers.

Well the fact that you say it still happens even after you close Bigbox leads me to believe its something else on your system, if Bigbox is closed, then it's closed and not using any resources.

Also what version of Bigbox/Launchbox are you running?