C-Beats

I'd have to see a screenshot of the screen you're referring to.

Not natively, you'd have to build something that did that. Really sounds like no-nag build is probably your best option in this case. Should be able to remove that script entirely after doing so as well.

One thing to note for a possible point of confusion that 10s is from the time we tell MAME to start. NOT the time from when you first see MAME pop up on your screen. That could be the cause of the 3 second difference you're referring to.

Nah everything you need has been installed for you. The fact that the window is being closed without you pressing anything to me would indicate the script is indeed working as those screens do not close without you pressing a key normally.

That the script I'm referring to. The sleep line needs changed to control the delay. That "10000" value is the delay time in milliseconds. To reduce the wait time simply use a smaller number, to increase use a larger number. For example 5 seconds would be 5000 ms so you'd use 5000 as the new value.

MAME cannot be configured to NEVER display those. You can make a setting in the INI so you only see imperfect warnings once per game, but there is no way to always turn them off. They are hardcoded in the emulator to do that which is why to completely eliminate them you need a recompiled build that has that code removed or commented out (like the one provided by MadK9). You can also adjust the timer and number of key presses in your MAME Running Script to make the script work more accurately on your set up so you don't have to wait as long for the script to close those windows. For me 5 seconds was far better than the 10 we had defaulted, but that length of time can vary based on your computer and settings.

Can use the Download Metadata and Media Wizard to update metadata and media on already imported items. Found in Tools > Download > (top most item)

Tools > Options > Updates > Update to Beta Release

Bin/Cue roms should never be zipped. If you want a single file you'd want to convert them to ISO or CHD (latter being preferred if the emulator supports it). Once you have them zipped import the file (import ONLY the .cue file, can use file explorer to search for *.cue and then drag/drop to LaunchBox). When running the import check the combine roms checkbox. If your emulator supports M3U files make sure in Edit Emulator to enable it and LaunchBox will open the game using a m3u file that points to each disk so you can swap discs inside of the emulator correctly.

If you are using the command lines we provide with the full set importer you don't need to set rom path in the INI we pass it to MAME for you. You DO need to assign the CHD path for those games though. If you're looking to manually add the path to the ini the multi path syntax is as follows "{path1};{path2}" (including quotes)

Should be the entry before this one (or typically is). Get one entry that says, "Hey the app did something it wasn't supposed to and is being closed" and then an entry like the one you posted that is "Hey we closed that app that had the issue"

At the top of the page where you select what items to download from LaunchBox Games Database & Steam. You must be on 12.2 or newer to have that option though.

Typically when debugging this issue the crash occurs because the OS is killing the process for whatever reason. The best log to get a good idea what is going on is the Windows Event Viewer log. There should be an Application Error log entry for the crash. That log will be quite a bit more useful to see than the Big Box log.

If you installed MAME using LaunchBox Fullset importer then the MAME folder is \\LaunchBox\Emulators\MAME (version number)\. Look in there for your mame.ini file

Could you copy/paste the whole error message for me? I need some of the bits of information cut off in your first screenshot.

Hmm... I'll take a look into that @fraganator, thanks for the heads up.

The plugin interface's documentation comment answers that for you. But yes, when launching the emulator the setting checks that EmulatorPlatform and uses it, if null it then falls back to the emulator.

Is your theme using the logo in GameDetails or somewhere else?

Largely because most people don't know as much about the system or it's games and don't have it in their collection. It was never released in North America and so a large number of users have no real reason to have those titles unless they look into it out of curiosity. There also is some media that just isn't really applicable for that system (like Box - Front) because the releases were all digitally distributed and didn't have cover art.

Responded to the PM. Does look like the new attract mode volume setting didn't get defaulted to the correct value and is causing the issue you're seeing. If you do what @faeran suggested I'd like to think that it will correct the issue you're having.

MAME controller configuration is an interesting one. If the controller isn't plugged in when MAME starts it reverts controller configuration back to default. Could this possibly be the cause of the confusion?

Can you throw your \\LaunchBox\Data folder into a zip file and send it my way? Like to take a look and see if I can use it to replicate. We've gotten a few reports of this but I haven't been able to replicate. Hoping the data files will provide some much needed insight into the issue.

Typically if you see them trying to download in the progress bar but they don't actually download it means you have the media limiter set and when we got to that file we determined you had hit that limit and then we skip the download. Can you verify that isn't the case for you?

Can make one yourself using Auto-Populate playlists. Make it so the only line is: Controller Support - Supports - Light Gun

To my knowledge all Epic store games should be working and have been for a while. What game aren't you seeing show in the importer?