neil9000

Dont use it if you dont have a fullset. Could be though that you only have a parent and not the clone, or vice-versa if its not a full set, who knows, so unless you know exactly what files you have the filter for mame isnt going to be completely accurate anyways, as you may be missing files that the filter settings you chose are actually looking for. Sets that have been trimmed like that really are asking for trouble when you are using tools that expect other files to be present that are not.

Cannon Ball is not a simplified name, thats the name of the game, and there are two games with that name, as you state. the simplified names, or "shortnames" that MAME uses are different, "cannball" Vs. "cannonb2" two completely different names. I think the proble may be that Launchbox does its image search after the metadata import and that is after we rename the game to its full name. Can you check both games in your setup and see if they have have the same, or different database ID's associated with them. Also can i ask why you are using the standard rom importer and not the dedicated MAME fullset importer we have? The dedicated importer does not use that mame.xml data file and pulls the data file directly from the version of the MAME emulator you are using (which of course should match your romset version).

No problems, just stating they are aware, but it seems to be a emumovies specific issue. They had been having some issues lately, but circo posted yesterday saying they hoped to have the issues sorted yesterday, not sure if they did or not, but might be worth checking if there are any improvements there.

Yes, i reported this on the first page of this thread.

Its not the sound driver, you wont miss it.

Its emumovies, we informed them last week, so its out of our hands at that point i'm afraid.

Why did you download a 20 year old romset, when the same place has the current one? That romset/emulator is too old to work with Launchbox out of the box and will need to use the standard importer rather than the mame one.

Will need far more info than that. What rompack did you download, and did you verify it works in a emulator first (no point troubleshooting Launchbox if you just found bad roms on the internet)? What system are you trying to import? what emulator are you using? What opens short but then closes?

No, as i said its a playlist file, it simply lists the discs you have, and that is parsed to the emulator instead of a single discs cue file. ECM files are not correct file types, you need to "un-ecm" them, also you only import the cue files not anything else. To be honest it sounds like you have awful roms there, bad format, and possibly incorrect cue files to go with them.

That is a graphics driver issue, i would check that your GPU drivers are up to date, and i would instal directx9 as well.

Launchbox doesnt "remember" any file names once deleted from the program. My guess, you have a xml file in the data folder that is being read for that platform still. Have a look in Launchbox/Data/Platforms and see if you have any files there that shouldnt be, should just be one file for each platform imported.

Not sure why you had issues with the Mayflash, its a native xinput or dinput controller, both of which work on PC (although xinput is more widely used). I have the F500 and have never had any issues with Launchbox or MAME with it.

Pi 3 is real weak hardware, these settings will probably make it worse.

Disc swapping is handled by the emulator, not Launchbox, so the process will depend on the emulator you use. You can set Launchbox to create a m3u file at launch which is essentially a playlist of all the discs, but the emulator needs to support that file type to start with. Most emulators should have a "open disc tray" option and another option to choose another file and then a "close disc tray" option, at least retroarch does, i cant speak to standalone emulators there as i dont bother with them.

Yes, as each cue will point to the appropriate disc number.

Mednafen, and its Retroarch core are the standard, but cannot be upscaled. If you want upscaling you need to use a more inaccurate emulator like Kronos or Yaba Sanshiro, both offer upscaling, but are far worse at the actual emulation.

Either audit a platform from Tools/Audit and sort the spreadsheet that appers by video, or change the dropdown top left to games missing media, and then choose videos, after that putting a system name in the search will narrow it to that system.

Those links are working fine here.

Not something i have ever seen before, looks like a scaling issue of some sort though. Looks like you are using a ultrawide, but Bigbox is 16:9 still for some reason, can you try the theme linked below and see if it is any different. Also your Windows scaling seems excessively high, can you try it at the normal 100% ( i also have dual displays and one is a 4K TV, and i dont see this issue). Lastly, open task manager and go to the services tab and see if a service called "Nahimic" is running, if so disable it and test Bigbox again.

I know Chromebooks these days run Android apps, but i dont believe Chromebooks have ever been tested with Launchbox, nor do we advertise compatibility with them. Also doing a quick google it appears you need a chromebook from 2018 or newer, and sideloading apk's is not officially supported so you have to use dev mode. How to Easily Sideload Android Apps on Chromebook [Guide] | Beebom

OK, a few corrections here, Launchbox is not overwriting or creating saves, nor does it check for saves either. That is all handled by the emulator itself, Launchbox is simply not able to do what you are suggesting here. The only way it MAY be possible is if there is a command line argument to create a save at launch, and you manually added that command to Launchbox, which I would imagine you have not done. Launchbox is simply a launcher it starts the emulator, gives it a path to a rom and says load this, that is literally all it does, and settings like controls, graphics settings, saves are handled exclusively by the emulator you choose to use. So i would dig around in the options and maybe google if there are any bugs in Duckstation when launching via the commandline, which is what Launchbox is doing, i have seen issues like that in the past, Dolphin specifically had a issue that when loading a game from the command line the controller would not work, but it was fine when starting Dolphin by itself, so bugs like that can occur.

If you have those playlists then you used the fullset mame importer, you shouldnt of used that if you have no Capcom games, as that is clearly NOT a fullset.