C-Beats

@starfiretbt The correlation between the ROMs and the Emulator when talking about MAME isn't the same as other emulators. Other emulators are designed to use any dump file for the system they are designed for. MAME has a lot of logic in the app to help with a very specific dump file and so changing the emulator without changing the ROM can cause mismatches that make things break. For that reason you don't update your emulator without grabbing the ROMs for that specific version. While you technically CAN grab games one by one, you'd have to ensure they are all from the same MAME set which typically is easier said than done which is why we recommend just grabbing the whole set and then whittling down to what you want. Also you can only whittle down a non-merged set in this way. Split/Merged share files between games and deleting one file may break several games making that pare down far more difficult.

@trublu289 are you having the same reported issue? You're the first person thus far to report they have any issues that don't have a 14mb DLL file. You also aren't showing the same error message every one else reporting this has shown. I'm thinking your issue probably isn't the same as the others.

You may be able to look in the logs and get the exact error that is throwing that notification. "In Use" is just the standard reason that step errors but there are other possibilities (like the destination can't be written to)

Until some one can get my the VirusTotal url for the BigBox.dll I can't really move forward with this reported issue. It's very clear though that something is altering your files (whether it's you or something else on your machine) so until we can find out what is altering your files we can't really do much to help with the issue. The official product doesn't have this issue the fact that you are using files that aren't official is causing this issue.

We do things the way we do because MAME and MESS have been combined and MAME is actually a viable emulator for a pretty large number of platforms and so for our workflow and how our database is set up it's not all that possible to cram it all under one platform.

MAME covers FAR more than just Arcade games. MAME.xml has information for all rom files that are supported, not just Arcade games. LaunchBox does it's best to whittle down the ROMs to only those that are for Arcade titles and so there may be some differences. I've personally never used RL or Hyperspin to know what they are doing. Thankfully sounds like all systems mentioned are more than open-ended enough that they all give the user plenty of options to choose from.

The number of working games Neil quoted is number of working arcade games, and is 2828 parents as of the latest release. Your screenshot shows non-arcade machines (like 4004clk) which is increasing the number you are seeing. Arcade Italia is a great resource for looking up MAME roms and whittling them down based on parameters using the same MAME.xml and INI data LaunchBox uses in it's logic. To address the OP and their question directly: You want to keep your emulator and set at the same version but really don't need to update unless there is a feature or game add/revision that interests you. I personally am using .232 and haven't personally really felt compelled to update my set since. As MadK9 was saying though, if you upgrade one you need to upgrade both. This is because the emulator is built around the corresponding set and may have version specific information that was changed in either the ROM file or in the emulator, and having a mismatch set can cause issues for you. That being said LB media goes by filename which (as DeadDevoid pointed out) doesn't typically change per set. Because of this when swapping versions you can simply rerun the full set import in LaunchBox and the only media that will be grabbed is stuff you didn't already have.

Thanks for the finite numbers. I was clearly off on the CHD estimation. I didn't even realize they had that many titles in the 232 working set that needed CHD. That's my bad on that one.

MAME sets include games/chd files that aren't playable. They are distributed mostly for preservation and so people actively trying to develop MAME can try and make them working. If all you care about are playable games and the files they need then yeah, you definitely don't need 1TB of data.

If you grab non-merged you can pare down your collection quite a bit. Grab non-merged (without CHD) which "costs" around 135gb. Then use LaunchBox to import the working roms (and whatever other filter you want to apply) and then move them to another folder using the in-app tools. What's left in your download folder you can delete which brings your fullset down to something like 20gb. Then if you kept the games requiring CHD grab the ones you need and go from there. You can have a full working set for around 30gb or so (even smaller than a merged set)

They initial said there were dropping it, but they had a pretty large community backlash for it on top of the backlash that users couldn't redeem tables they already owned. Sounds like they had to give on one of those fronts. I personally don't care for much of any of the design decisions they took in the title and will probably ignore it. Glad to hear though that the Vpin community got to take a home a win and got them to at least give them proper cab support.

That MD5 is correct and doesn't contain the DLL you linked. Can you provide the VT results for the DLL file? Also you can just link the URL, no need to try and copy the page contents.

That link doesn't have a direct download and wouldn't be where you got the installer from.

Can you upload your installer to VirusTotal.com and let me know the hash value you see?

We don't have any direct download links on our website. Can you provide the link you used? Also could you upload your DLL file to virus total and show the results.

Did you get the installer directly from our website or in-app updates? This DLL file isn't the correct size for 13.2.

Recent Games grabs the first 10 games ordered by Last Played or Date Modified (whichever comes first) and since cloud syncing may be upgrading the records it's possible that is causing what you're seeing. We are looking into ways to make that section appear closer to what people think it should be at a glance (Recently Played/Added). Unsure if any change will make it in before final release however.

The hasher app can't read many compressed file formats and we'd have to decompress them for you. We do this for 7z but haven't looked into .gz for it.

Did some quick digging and does look they finally succumbed to the angry mob. They have a FAQ specifically for the cab support mode they added recently: https://www.pinballfx.com/?page_id=7754 If I am reading this correctly there is no current way to launch into table though but should be coming in a future update.

Unless Zen changed their mind they aren't bringing cabinet support to Pinball FX and will not be making it possible to launch direct to a table. Was announced when first announced the title.

Not sure I follow. I don't know of any import wizard we have that doesn't support multiple files.

Make sure you go to Tools > Options and look for a section labeled "Game Details" (I believe it under visuals) and in that page there is a checkbox you can turn everything off/on. Make sure you have the Videos checkbox checked.

Can you navigate to \\LaunchBox\Core\BigBox.dll and right click and select properties and post a grab of what that window looks like? We had one user do so and their DLL info didn't match what I see for that install. Trying to confirm my suspicions that the DLL file is getting corrupted somehow.

Can just ask the question and if some one can answer they will. If it's a private matter than it's best to email support@unbrokensoftware.com and they can work with you.

1) is a personal preference and really doesn't matter since Big Box will presumably be open the entire time you're using the device and so you won't be accessing the desktop or start menu anyway. 2) To get Big Box to work as well as possible in Windows Display settings place the marquee to the right of your primary screen. When doing so the upper right corner of your primary monitor should be right next to the upper left corner of the marquee.