JoeViking245

MAME (Arcade) - What's New View File See what new Arcade machines (games) were added for a specific MAME release. Import some or all of those games from your updated MAME ROM set, into your LaunchBox collection. The intent of this plugin is to be able to see what new Arcade machines were added in the latest release of MAME. Then, along with your updated ROM set, provide a means of importing just those new machines into your LaunchBox collection without having to reimport the entire set or attempting to Scan for Added ROMs (which doesn't really work with the Arcade platform anyway). Features: See what new Arcade (ONLY) games were added specific MAME release Hyperlink to Arcade Games Database site for selected game Filter games by Status (Good, Imperfect, Preliminary) Import the new games (from your updated MAME ROM set) (Optional) Add an Additional Application direct link to the Arcade Database for the game A huge and special thanks to motoschifo and his Arcade Database (ADB) website! All data used comes direct from the Arcade Database and is what makes this plugin possible. http://adb.arcadeitalia.net Prerequisites: Requires LaunchBox version 13.19 or newer. Nothing else if you only wish to see what new games were added. If you wish to import the new games An updated MAME romset [containing those ROMs] Installing: Copy the contents of the zip file into your /Plugins/ folder e.g. D:\LaunchBox\Plugins\MAMEarcadeWhatsNew\MAMEarcadeWhatsNew.dll Using: In LaunchBox, go to Tools and select MAME (Arcade) What's New The plugin will attempt to find your MAME emulator If found, the MAME Revision field will populate with your MAME's version and populate the games for that revision To see new games that were added in a different release Change the number in the MAME Revision field Must be formatted 0.xxx e.g. 0.281 Press Enter Un-check/check the Show Status checkboxes to see only ROMs with those status(es) Click a ROM to see brief details about that game Click the Arcade Database logo to navigate to that game on ADB Existing: as seen below the game details refers to, if the game exists anywhere in your collection. Checks across ALL games in ALL platforms (by ROM filename). Below it will show the platform it is in (if "existing") This is useful if you're checking previous releases for that hidden gem you didn't know you were missing Importing: If you've updated your MAME set, you can import the new ROMs into your collection. All new ROMs shown will be imported. You can multi-select games to add just those games selected. If you wish to import just a single game, close the plugin. Then in LaunchBox, press Ctrl+N to add a new game. Click Add Games Select a platform (Arcade is set by default if exists) (optional) Un-Check Use Platforms Default Emulator Select an emulator to assign to the games being imported from the dropdown list Select the folder containing your ROMs (default is the folder your game files are in for the selected platform) If you keep a curated set separate from your MAME fullset, you can select the folder your fullset is in. Then after importing, have LaunchBox copy the ROMs and reset the game ROM path. **(see more below) If you've already placed your new ROMs in your curated set folder, select that. (Optional) Check the box Add link to ADB as Additional App Click Import Games Importing Notes: Games already existing (based on ROM filename) in the platform (step 2) will not be imported Games whose ROM file doesn't exist (step 4) will not be imported After import, a report will show the # of games added and/or skipped Anything in the games Title that is in (parenthesis) will get moved to the games Version field e.g. "Hacha Mecha Fighter (bootleg with Raiden sounds)" Game Title will be saved as "Hacha Mecha Fighter" Game Version will be set to "(bootleg with Raiden sounds)" (Optional) Add an Additional Application direct link to the Arcade Database for the game This will appear as an "Arcade Database" clickable link in the Game Details section (except for LaunchBox version 13.24). Game data set when importing: Title Platform ROMs application path Date Added/Modified Associated Emulator Version (if available) Getting Metadata and Images: After importing, in LaunchBox select all the newly added games Hint: Click Arrange By and select Date Added. Select the 1st new game. Hold down Shift then click the last, new game. Go to Tools - Download - Update Metadata and Media for selected games When asked "Would you like to update games with existing metadata and/or media?" Select "Yes, but do not replace and existing fields and media" Selecting otherwise will remove the Version data (if exists) Metadata Notes: If importing from the latest MAME revision, when you go to Download/Update metadata, the game(s) may not be found. ** Copying the new imported games ROM files to a different ("curated") folder: To Copy the ROMs and reassign their location (as seen by LaunchBox)... After importing, (in LaunchBox) select the newly added games Copying: Go to Tools - File Management and select Export ROM Files from Selected Games to New Folder Have LaunchBox copy the ROMs to the Folder your curated set is in Reassigning: With those games still selected, go to Tools - File Management and select Change Roms Folder Path for Selected Games Change to the Folder your curated set is in Plugin Updates: If an Update for this plugin has been released on the forums, - The Info/Support icon will flash red. - Click the Info/Support icon, then click the Update Available button. This will open the plugins download page in your default browser. Again, a big thanks to the Arcade Database and all its contributors! As always, all thoughts, views, suggestions, comments and accolades are welcome. Submitter JoeViking245 Submitted 10/30/2025 Category Third-party Apps and Plugins  

Here's some info from the LaunchBox Strategy Guide that may help. https://feedback.launchbox.gg/help/articles/4883944-music-in-launchbox-and-big-box

If the original posted was written in a different language, then yes. Depending on your browser, you should be able to right-click it and select Translate.

You can't use a cvs file to import games. I suppose you could get creative and create a batch file or PowerShell script to extract the names and create files (e.g. .txt files) from the names and import those. The Platforms.xml (in /LaunchBox/Data/) stores metadata for the Platforms in your collection. The [platform_name].xml file (under /LaunchBox/Data/Platforms/) stores the info for the games imported into your collection for that specific platform. The database file (located in /Metadata/) stores the metadata for all games. Once an imported game is associated to the respective game in the LaunchBox database, metadata from the database file is copied into the [platform_name].xml file for easy retrieval by the UI.

Adding things is easy. But there's other things to consider. Just a guess as to why... low cost-benefit [at this early stage of PS4 emulation]? Lack of interest from the user base (as deemed by limited Feature Requests and Upvotes)? Time (as in, it's currently being spent on features that have been requested/upvoted)? Regardless, I think it boils down to not being a beta issue. What can you do now? Upvote the current feature request for shadps4. Create a new Feature Request (vs. a Bug Report) to incorporate the importing of PS4 games. Once it becomes public, create a new thread asking users to Upvote the request(s).

Unless I missed it (and I'm sure someone will let me know if I did ), I don't believe anything's been implemented (even in beta) to cover Playstation 4 importing or for shadps4. There was this Feature Request to Add Plugin Support for ShadPS4 and ShadPS4 Plus Emulators about 4 months ago. But doesn't appear to have gotten much love.

Just tested (13.25-beta-2) and EmuMovies is working fine here. Tested via: Edit Game, Images, Download Media and was able to select images and videos in the EmuMovies tab.

You are very welcome. I'm just glad my guess was a good guess. (As I never pay attention to the playtime) Ok. So that xml folder was put there by something or someone else. It's not a folder that is default/native to, nor put there by, LaunchBox.

The are 1 or 2 (or more?) "Unbroken" references/declarations that cannot be added to Visual Studio. You can read a little more about it here:

What is the criteria you have set to have LaunchBox change it "Active"? If it doesn't meet the threshold, it will get marked as "Not Started". That said, I'm not sure if manually changing the games Progress value (either by simply editing the game or via editing the xml file) is "supposed" to stick or not. Or if it's to change per the set criterium. An aside... Where exactly are you finding the "\xml\" folder?

No worries at all. It's just a hobby and we get to play when we get to play. Sweet! Now I don't have to download it and test. And apologies for the assumptions and accusations. Settings I have are not necessarily settings you have. 😊 (thought it seemed too easy. lol) You're welcome and CONGRATULATIONS!!! 🎉

You can't change that because you have the Graphics API set to Auto. And that's fine. So I turned BezelLauncher back on to test this and was experiencing the exact same thing as you (but with plain QT). I tried a bunch of different settings and things in the Graphics settings menu (in PCSX2) and couldn't fix it. I then looked in the Interface menu section and un-checked Game Display - Start Fullscreen. After finding that it now works, I reverted all the changes I made under Graphics, and it still worked. 😊 One other thing I also noticed was it could get rid of (hide) the top menu bar. So what I did was, in BezelLauncher Setup - Test, set the Top of the emulator window to y=-20 (20 pixels above the top of the screen). Then stretched the bottom to the bottom of the screen. tldr: Verify you don't have anything telling it to go fullscreen. Either in the command line parameters or in the emulator itself.

Refreshing to hear. Thank you! It should work fine. Admittedly though, I've never the avx2 variant. My shoot-from-the-hip guess is that it's running Exclusive fullscreen. vs. just fullscreen or borderless fullscreen. You're quite welcome. Glad it's helping you work towards your goal.

No. Games saves are integral to RetroArch. However, some cores may not be able to support them. (I don't know this for fact but seems to make sense.) If you're referring to being able to manage them in LaunchBox (as shown in the 1st link I sent you), not sure. Is the menu item saying it's a premium feature?

Note that both LaunchBox and Big Box after closing/exiting, by design, does do work in the background to save data (aka, save any changes and create backups of changes to your Data folder). Depending on the size of your build, what changes were made [and to a degree, your system specs] this may take upwards of a couple minutes. But typically, shouldn't take that long.

My disclaimer: I've never used this feature. That said, It looks like maybe, possibly, a shoot-from-the-hip guess... LaunchBox is searching for Saves via Emulator - Platform, and assumes you'd only have one [valid] core associated with it, so grabs the 1st one (regardless of Default) it comes across. Which coincidentally? alphanumerically? is the fceumm core. Not to simply "pass the buck".... May want to file a Bug Report.

Tools < Options < General < Save Management

Hopefully you can find some useful information here: Managing Save Games and States - LaunchBox

You might try Tools < File Management < Restore Data Backup... I personally haven't used this tool, but I presume the prompts should be fairly descriptive.

Based on information you've provided... the exact same zipped ROM file will launch directly from within RA, but not when launched via LB, yet others in the exact same platform do launch [via LB], and all ROM files being used are zipped (e.g. "gameROM.zip"), ...leads me to there's something amiss with the specific game settings in LB for the non-working games. My last-ditch effort (akin having you share screenshots of everything) Edit (in LaunchBox) a game that's not working [in LB, but does direct from RA] Check the ROMs path (Launching section) Click Browse and verify it's pointing to the correct/same zip file and location used in both tests Check the assigned emulator (Emulation section) Verify it's assigned to your RetroArch emulator If you have more than one instance of RA make sure it's assigned to the same one being used by games that do launch via LB Make sure it's not using a Custom Command-line Parameter for the game (un-check the box) If you are using Custom Command-line Parameters for individual games, that's a different story/issue which you need to elaborate on Beyond that, I'm out of ideas.

No. This is the only instance in my 8-9 years here where I've heard of this being an issue. I mean, you could put in a feature request. I suppose.

In the emulation section of the game you launched, is it set to use the batch-file/emulator? If you've created more than one test-emulator, is it pointing to the correct one? Is the script I gave you the only thing in the Running Script section? If not, make sure it's at the top. Try changing where caption='fusion.exe'" to where name='fusion.exe'" (in that script). Try using a different emulator that is actually currently active. Like RetroArch with the Genesis Plus GX core. Or Ares. Try removing the 1st line in the batch file (set __COMPAT_LAYER=highdpiaware). Verify it works (even if it's only shows on 1/4 of the screen) with it removed when used as the emulator. Is there something in your graphic card settings you can change specific for "Fusion.exe" where you could run the emulator directly without the need of a batch file. Does the "1/4 of the screen" change to show everything when using the emulator directly from LB if you change your screen Scale (in Windows Display Settings) to 100%?

And when you edit the game in LaunchBox, the game's ROM path is pointing to the correct .cue file? (Not "and its tracks") Good! Now in LB, use the 1st of the 4 examples as your batch-file/emulator. In the Running Script section of this emulator, put Sleep, 3000 queryEnum := ComObjGet("winmgmts:").ExecQuery("" . "Select * from Win32_Process where caption='fusion.exe'")._NewEnum() While queryEnum[proc] t .= proc.CommandLine "`n`n" FileAppend, % t, .\Plugins\CommandLine_Fusion.txt Launch a game using the batch-file/emulator. Wait at least 3 seconds before closing the emulator. Close the emulator. Navigate to your /LaunchBox/Plugins/ folder and open CommandLine_Fusion.txt What's it say?

Did you verify your account (in Steam) is set to public?

Again, I don't use/have that emulator setup. So flying blind here. Remember, you're passing along whatever details to your batch file. So, whatever your batch file requires to be sent to it. And since you're running 'my' batch file, no boxes should be checked. Including boxes in the Associated Platforms section (except for Set As Default Emulator for the platform). I presume when you imported the games, you imported the .cue files. Correct? Try creating a batch file and run it by itself, outside of LaunchBox to start a game. You indicated you did that and it worked, but you didn't show what that one looked like. Should be something like set __COMPAT_LAYER=highdpiaware start "" Fusion.exe -scd "D:\myGames\Sega cd\my favorite game.cue" pause Change the above path to reflect the game that you were testing in LaunchBox, its ROM path. Now see if that works. I added a pause at the end (for testing purposes) so if any errors come about, you should be able to see them.