JoeViking245

I have one plugin that [still] uses that copy of VLC. Fortunately, it's only one and can easily be changed to use the assets under /FFMPEG/. Thanks for the reminder that this removal (could happen?) is imminent.

A fresh install of MAME doesn't come with mame.ini. Open MAME double-click General Settings double-click Save Settings Press Escape 2 times make your changes to [the now present] mame.ini

Though I'm not familiar with this, it looks like a handheld game. MAME carries many handheld games, but they don't fall under the Arcade platform. e.g. Tiger Electronics' "Tiger Game.com". At a quick glance, this should in the platform "VG Pocket". (or VG Pocket Mini? or VG Pocket Caplet? or VG Pocket Tablet?) Since that (or those?) platform(s) do not exist, you can put in a Feature Request to have it (them?) added.

Try: Open up your Epic Games client (external to LaunchBox), sign [back] in and accept their terms.

After doing the import from the updated ROM set, do you [now] have a game with the Title Geo Storm? After doing the import from the updated ROM set, did your look for Gun Force? or Gunforce? For the game Gun Force II (vs. Gunforce2), Is your ROM filename gunforc2.zip (vs. gunforce2.zip)? Are you importing the game into your "Arcade" platform? When you updated your ROM set, did you also update your MAME emulator (to 0.284)? When [attempting to] import the ROM, is the emulator you're selecting the updated MAME?

Place the BIOS files in the same folder as the ROMs (vs. in a separate subfolder). e.g. D:\LaunchBox\Games\Arcade\rom1.zip D:\LaunchBox\Games\Arcade\rom2.zip D:\LaunchBox\Games\Arcade\rom3.zip D:\LaunchBox\Games\Arcade\bios1.zip D:\LaunchBox\Games\Arcade\vios2.zip

System Menu < Options < General < Primary Screen: Screen 1 Change the 1 to whatever your monitor is on. Note that what Windows see as Monitor #1, may not be what Big Box sees as #1. So try the different available #'s to you find it.

The import wizard is geared towards adding games to your LaunchBox collection. Not really for 'updating' it. Arcade is unique to other platforms in that its ROM set encompasses all things arcade, emulatable or otherwise. Including but not limited to Arcade machines, fruit machines ("slots"), pinball and handheld games. I won't even go into its soflists side of things in which the main ROM set includes all the devices and bios files for. Even more unique are the 3 types of ROM sets MAME has. Merged, non-merged and split. That alone can make updating your collection challenging. It's primarily because of these differing sets that Arcade is purposefully blacklisted from the AutoImport feature. With MAME being updated monthly, there's no real automagical way to have newly added ROMs classified into their respective 'genres'. e.g. poker/casino, fruit and handheld (which is a lot of what's being added these past months). This part of the MAME integration into LaunchBox is done [at least] semi-manually. And doesn't (can't?) happen as-soon-as a new update comes out. I have no idea how frequently LB developers update that aspect of it. I presume within a week-ish of the [MAME] new release. I suspect this is what/why you're seeing the post 13.21 issue. Thanks for the follow up on the bezel updating. That's good to know. RE: -listxml, when importing, LB will actually run that [in the background] to get a list of MAME ROMs your MAME emulator is aware of and use that to import from. When doing a fullset import, LB doesn't even look at all ROMs you have in your set. It just goes off "the list". e.g. if you have a 0.284 ROM set, but your mame.exe is 0.179, you'll have a lot fewer playable games imported than are in your set. (a farfetched example, just to show a point).

This was fixed in version 13.21 (Apr. 24, 2025) "MAME Gambling games are now marked as Casino games allowing you to easily filter them out during imports" Don't have LB delete media when deleting your existing Arcade platform and then click None for both LB and EmuMovies media during re-import. Since MAME doesn't really add many "new" machines between releases, those few games will be easy to identify. If you are manually updating your emulator, you can of course skip that step. I haven't checked in a long while, but I believe when "updating" this particular emulator, LB will install (unzip, basically) MAME into a new folder, suffixing the folder name with the release number. Essentially giving you a "new" install vs. updating your existing install. It then reassociates the game to use the "new' emulator. Do note that a new/fresh install of MAME only includes the base files and that there are no configuration files included. I manually update my MAME emulator myself. Which involves downloading the binaries from MAMEDev, right-clicking the exe file and opening it with 7zip (as the installer is just an executable zip file). Then copy the complete contents of the "zip" into my existing MAME folder. After at least 5 years and doing monthly updates, I've never ran across an issue doing it this way. If doing a full import, I don't know. If after the import is complete you go to Tools < Download < Update Metadata and Media for Selected Games..., I'm fairly certain it will only download the missing artwork (bezel files). But I not 100% on that. It shouldn't affect your Categories at all. Since you're importing only one Platform (Arcade), it will still get added under the Arcade Category. If your current Arcae Platform is under multiple Categories, then you will probably need to reset that in the Platforms Parents tab. On the other hand, Playlists you had or have manually created that look specifically for games in the Arcade Platform will still be there. Maybe someone else can chime in on how best use the import wizard for monthly updates. I don't use it for that. I update my Arcade ROM set each month, update the emulator as mentioned above then read through whatsnew.txt to see what new Arcade Machines were dumped/added. If I see something intriguing, I'll manually it (them?) using Ctrl+N. There's also a plugin in which you can see what new Arcade Machines have been added with each release. It only shows you MAME cabs, so you're not inundated with fruit machines and the sort. Unfortunately, since the plugins release, there haven't been any "new" machines added to speak of. A lot of new or updated ROMs, yes. But not cab machines.

The purpose of the emulator integration plugins is for installing and updating those emulators. It won't actually update the emulator until you specifically tell LaunchBox to do so under Manage Emulators. To get rid of the update plugin notifications, you can update the plugins [without having any effect on your existing emulator installs].

The error code indicates there's an issue with your license file. Contrary to the message, you need to contact support regarding licensing issues. email: support@unbrokensoftware.com

Is the cheats file compatible with the version of MAME you're using (looks like 0.279 is the most recent)? You're using stand-alone MAME. Correct? Or MAME via RetroArch? Are you using MAME from MAMEDev? Or a derivative of MAME (like MAMEUI)? Which version? Just tested here with cheats 0.279 and MAME 0.284. Placed "cheat.7z" in the same folder as "mame.exe". Started MAME and enabled Cheats (and Autofire) in General Settings - Plugins. Exited and restarted MAME. Started "1942", pressed Tab and selected Plugin Options and both Cheats and Autofire were showing. Maybe the game you're testing doesn't have cheats available for it. Not really sure how that works as I don't use it.

The zip file goes in the same folder as mame.exe. Individual game custom xml files go in the /cheat/ folder. Autofire is a MAME plugin.

It moved to here: MASH's MAMEINFO

What Windows sees as monitor #1 and monitor #2 is not necessarily how Big Box sees them (order-wise). It's not a bug or something that will cause ill side-effects. It's "just a thing". In Windows, set your monitors in the order you want them. Then in Big Box, change it to "1" or "2" until BB is on the monitor you want. Also, though "shouldn't" affect your particular setup, when setting up the monitors in Window's Display Settings, align the tops of the 2 'monitors' and have them side-by-side (vs. one on top of the other). It "seems" like this shouldn't matter, but (e.g. not having the tops aligned) can have undesirable effects.

At first, it sounded like something was done to do a mass edit on all your games. Which was really odd. That Feature, also found under View - Show/Hide - Versions, toggles showing the version along with the games Title in the Main section.

According to the help printout, yes. What's your games ROM path pointing to?

When running suyu-cmd.exe -h from the Command prompt, it shows: -c, --config Load the specified configuration file -f, --fullscreen Start in fullscreen mode -g, --game File path of the game to load -h, --help Display this help and exit -m, --multiplayer=nick:password@address:port Nickname, password, address and port for multiplayer -p, --program Pass following string as arguments to executable -u, --user Select a specific user profile from 0 to 7 -v, --version Output version information and exit -l, --applet-params="program_id,applet_id,applet_type,launch_type,prog_index,prev_prog_index" Numerical parameters for launching an applet. If no game is provided, then the applet will launch off of the applet_id. Make sure you're using suyu-cmd.exe for the executable.

I think it's time to file a bug report. Top of this page under Help & Support.

A couple quick tests shows switching the games startup theme in Big Box on-the-fly isn't applying the newly selected theme. But switching theme, exiting/restarting Big Box does work. Tested back-and-forth between Default, SlipStream and StageBox startup themes. Same results each time: The "old" (originally selected) startup theme still showed until Big Box was restarted. But... (regarding your PS2 dilemma) when I switched back to Default, exited and restarted Big Box, then launched PS2's Arctic Thunder, the spinny disc, spun. aka it used the 'Sony Playstation 2.xaml' startup file. So maybe the restart is the trick? "trick". NOT to be confused with "solution". BB not applying the changed startup theme seems like it may be a bug. 🐞 Which brings me to, my tests were all using LaunchBox version 13.25-beta-3. Yours? (I didn't test on any earlier versions of LB/BB)

(just some background info...) For game startup themes, it will use the xaml file that has the same name as your platform. If it can't find one named the same, it will look for one named after the platforms Scrape-As value. If it can't find either of those matches, it will use Default.xaml. However, it doesn't explain why you see the spinning disc when launching a Sony Playstation 2 game from LaunchBox and not from Big Box. So call this a non-helpful fyi reply.

Read here: LaunchBox Licensing FAQ - Name or Email Change on a License