C-Beats

If referring to MAME games we get that information directly from MAME.

CTC to my knowledge only loads raw images for it's previews as opposed to cached images. Most image types at this point can be cached, though I believe there are a few that are not (like backgrounds). If you want to use a cached image you can use the FlowImage control and if that image group caches it will use it by default which can speed up load times. I'd be nice to get a theme dev controlled cache item for items/groups you know aren't changing but that isn't in the works just yet.

Not at this time. Horizontal games are games NOT in the vertical playlist and so unsure why you would want both. If you are looking to filter by that value you can always go to the vert playlist and add a Orientation custom field, and then use the various filters against that field.

It's there but you need to be in Platform Category view (which isn't a change, it's always been like that to my knowledge). That being said at this point that hasn't been added to that menu. We could take a look at potentially adding it there.

Big Box doesn't have touch screen support at this time so this makes sense. You can upvote the touchscreen support ticket we have here though.

This should be corrected in beta 2. Could you upgrade when you get the chance and confirm for us you see it corrected as well?

The ways I'd know to do what you're asking to do basically requiring you using the static image and referencing to it if the playlist name contains the platform string in it. Pseudo-logic would be like IF PlaylistName CONTAINS "Nintendo Entertainment System" THEN Use image ELSE Don't Won't be as clean of a solution but fairly certain you can do it with CTC visibility filters.

We don't configure an INI in the install process. so It's entirely possible it wouldn't be in the folder at all. I believe once you launch a game with the command lines we've added MAME will generate an INI file though. The only INI files you really should be messing with are the ones in the MAME root folder. At this point I'm not entirely sure what you are trying to change in the ini to even begin to look at the differences to tell you if they were right or wrong. Are you trying to change some shader setting or do something more elaborate?

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.