JoeViking245

LaunchBox for Windows Latest Changes

As of Version 13.21, their location has moved. (look in /LaunchBox/Images/Media Packs/) Media Packs - LaunchBox

Select all the games in the platform (click one, then press Ctrl+A). Tools < File Management < Change ROMs Folder Path for Selected Games...

Thanks. Fortunately (unfortunately?) that all appears good. The only thing I can't verify is.... Double check that the games ROM file path is for-sure correct. Can click the Browse button, it should take you to that folder, find and double-click dkong.zip to set (re-set) the path. Click OK to save and close and then try the game. If it still doesn't work, you can install this plugin, run it on the game and see if it shows any incriminating symptoms.

Using the LaunchBox Install MAME (emulator) I think installs it into /LaunchBox/Emulators/MAME 0.2xx/. Where 0.2xx is the version installed. And if my recollection is correct, a 'new' version/release will get installed into a new folder (MAME 0.2xy). (this may have been changed since I last checked quite-a-while-ago). Either way, you will NOT lose any custom configs. A new MAME installation will only have the base files of the app, leaving all custom changes/additions/configs intact when installed over the top of an existing one. (Unless you're a power user and have gone in and modified something like crt-geom.json) When you say "it DOES import correctly", I assume you mean "install" [the emulator] correctly. (vs. "import" the ROMs correctly?) The afore mentioned updating procedure will [also] not change/delete the artwork (if you're talking MAME's /artwork/ folder [aka bezels]) nor will it mess with any images or videos you've downloaded in LaunchBox for your Arcade platform. But I don't think you have the latter because of the issue with the MAME Arcade Fullset Import Wizard. RE: updating your MAME set, get the 0.279 (actually, may as well get 0.280) fullset. Essentially replacing your 0.261 set. (As opposed to updating 0.261 to 0.262 to 0.263 etc. which is how it'd need to be done if you wanted to update your physical existing set. And is a PITA not a fun task.) As for updating the emulator, if you're happy with the one LB installed for you, you can just copy from your existing MAME install the folders: artwork (if you have bezels in it), cfg, ctrlr (if you created a custom controller.cfg file. Not to be confused with the game-specific ones in the cfg folder), ini If you made custom changes to MAME (like ROM path), you probably have a mame.ini file that should be copied over as well. IF you tried running the MAME Import Wizard and pointed to your 0.261 MAME install (accidentally or on purpose), that could be the problem. Some things were changed in how the xml that gets produced [quite] a while back. I forget when exactly. But Nov. 2023 (0.261) in MAME terms, to me falls under "quite a while back".

On "the next day", did you try a game that had worked the previous day? If the previous days' games still work, my shooting-from-the-hip guess is the next day's game(s) might be ones that require CHD's. To better help you, can you please share some screenshots of how it's setup in LaunchBox (see below)? Also, what version of MAME and its ROM set you are using? Edit your MAME emulator [in LaunchBox] and show screenshots of - the Main Details section - the Associated Platforms section Edit one of your Arcade games [that doesn't work] and show screenshots of - the main Metadata section - the Launching section - the Emulation section

No problem. Though it does seem a bit niche, I'm sure you have a good reason. Beyond "because I can". You can always put in a Feature Request to integrate custom core locations. Feedback - LaunchBox Navigate to the link and click Create a new post.

Are you pretty adamant about not having the cores in their default location? That is, are you adverse to having them in the cores folder? I know for myself, I do a bit of crazy customization for my emulators. But have never thought of moving the cores to a different location. As LaunchBox has made using RetroArch to be a near hands-free experience, it relies on several of its default settings. e.g. core location. There's [almost] always a way. For an atypical installation, you can use a custom command line in the games' emulator settings. Edit the game and in the Emulation section, check the box to Use Custom Command-line Parameters. Then below that, add -L path/to/your/cores/core_name.dll After confirming that works, then there's a Bulk Add/Remove Custom Command-line Parameters plugin that will allow you to add that to all games in that platform in one shot.

In vertical.ini, try -aspect 8:5 (don't ask, 'cause I don't know) Nope. Including order of precedence. If you have writeconfig in mame.ini set to 1, it will create a game-specific ini files (e.g. 1942.ini). Those will supersede what's in vertical.ini. Making any settings in vertical.ini essentially null and void. So be sure to remove any game-specific ini files and check the writeconfig setting in mame.ini.

Is your mame.exe from the official MAMEdev site? Or some variant (no-nag or otherwise)? The error message is saying it can't parse [correctly] the xml file generated by running mame.exe -listxml. Rerunning the importer would recreate the xml, fixing any glitches.

Looks like Unit3D is now VPE. You can read about some of their development here: Visual Pinball Engine - 2025 Updates - Visual Pinball Engine General Discussion - Virtual Pinball Universe Their main page Planet Visual Pinball Engine - Virtual Pinball Universe

In short, no. A little longer, no. There is not. That's pretty much near impossible (without A LOT OF legwork creating "config files"). I don't think any emulator, outside of MAME (and maybe a few other Arcade emulators), stores controller/cab button assignments that are in an accessible/readable format. And even with MAME, to get assigned controls for a game, you'd need to cross check several files for possible overrides against the default settings file. From there, read another external file (not innate to MAME) to convert the assignments to "names" (up/down/shoot/punch/kick/etc.). Then take that info and somehow get that onto a dynamic image. Note: the said external file containing "names" is largely incomplete.

To get an 8-year-old version of LaunchBox (or any past version), you need to contact support@unbrokensoftware.com.

Of course it hid them. Edit a game that was imported by the Welcome Wizard. Verify that the ROM has (version)(information) in its filename. If so, check that the (version)(information) got added to the Version field. Assuming Star Wars was one imported via the Welcome Wizard, it does seem that it's not importing the version info. Which would also, most likely, be why the multi-disc badge isn't showing. (it didn't catch (Disc 1) and (Disc 2) along with any of the version info)

It's showing the version. View < Show / Hide < Versions (Ctrl+R)

I only have enough knowledge to be dangerous. You can use an Additional App to load it. But you'll need to make another and set it to Run After Main Application that kills joy2key. Which is what lines 3 and 4 in the script does. Don't make it more difficult than it needs to be. Use the script that seemed to work for the OP.

Oh. OK. So you weren't even using the script you tagged me from. Or a script at all. (which is outside of the scope of the OP) That error message looks like maybe it came from joy2key itself. I've never used joy2key, so have no idea. My guess is you have something wrong in the command line parameters of your additional app, to get that error. And since your additional app only sets/loads the config, it's not designed to close itself when the game exits. Which was the intent of the OP and the need to use a script in the Running Script section (so as to close joy2key on game exit).

Can you share a screenshot of the actual message? (vs just saying what it says. there may be more clues somewhere in the actual message and its window). Did you change the paths (on the Run line) to match your actual paths? Does you path(s) have spaces in it? If so, did you put quotes around it (as shown on the 1st path)? Are you using that exact script (with path changes)? Or did you modify it otherwise? If so, what does it look like? Note: With an Additional App, you need to add it to each game. vs. putting the above in the Running Script section of the emulator.

Try rerunning the Full MAME Arcade Import Wizard.

Ahh.. yeah. That can be an issue. I say delete in place, then reinstall into the same location (/Emulators/Dolphin/). This way you wouldn't have to change anything in LaunchBox. Then see if you can double-click dolphin.exe and have it open. Next, try a game. [success] Try it then through LaunchBox. Even on the network, if it works in stand-alone Dolphin, it should work through LB. If not, try copying a ROM onto the local drive, (change the app path for the game in LB) and try again.

The quality is fine. Unfortunately (only because it doesn't give an easy solution) that all looks good. I presume that's the most recent release of Dolphin. Usually, the Details screen will show what your local version is and have a Reinstall button (which isn't needing to be done). Unless you're using an older version of LaunchBox before that became a thing. Another assumption is that you don't have 2 installations of Dolphin on your system (i.e. your testing done outside of LaunchBox was using a different copy of Dolphin). Which leads us to... (in LaunchBox) edit your Wii games and verify the game(s) Application Path (Launching section) is pointing to the games .rvz file. Also double check in the Emulation section of the game(s) that Dolphin is selected as the emulator. If all else fails, (though this should affect anything) remove from the emulators' Command-line Parameters everything between -b and -e. Leaving it with -b -e. A last grasping-at-stars thought is un-check Attempt to hide console window (your 1st screenshot).

Can you (in LaunchBox) edit your Dolphin emulator and share a screenshot of the main Details section the Associated Platforms section

To be clear, you opted into betas (Tools - Options) and installed 13.24-beta-1? (vs. the latest official release 13.23)

Regarding ROM location, amending mame.ini's rompath line and softlist BIOS files: If you plan to add more MAME softlist consoles and/or computers to your collection, I suggest placing their respective ROM folders all under one main folder, like "softwareLists". e.g. D:\LaunchBox\Emulators\MAME\roms\softwareLists\ D:\LaunchBox\Emulators\MAME\roms\softwareLists\fmtowns_cd\ D:\LaunchBox\Emulators\MAME\roms\softwareLists\fm7_cass\ D:\LaunchBox\Emulators\MAME\roms\softwareLists\fm7_disk\ D:\LaunchBox\Emulators\MAME\roms\softwareLists\aquarius_cart\ D:\LaunchBox\Emulators\MAME\roms\softwareLists\aquarius_cass\ This way you will only need to edit the rompath one time and can continue to add subsequent softlists with less worry. Since you're venturing into MAME's softlists, you probably have an Arcade fullset. Which in turn holds all the BIOS files needed for softlists. e.g. D:\LaunchBox\Emulators\MAME\roms\MAME_non-merged_fullset\ Note: Both example paths are within MAME's folder structure to ensure its' and LB's portability. If portability isn't a concern, put 'em wherever you want. Just be sure to add their relative [to mame.exe] or absolute paths, below. Using the example paths, mame.ini's rompath line will look like: rompath "roms;roms\softwareLists;roms\MAME_non-merged_fullset" Call it a once-and-be-done-with-it approach. Now when you add more softlist folders under /softwareLists/, you only need to worry about getting the command line parameters correct. MAME will find the respective ROMs and the necessary BIOS and Device files. This covers both Arcade and softlists.

You can disable the Pause menu per game by editing the game and overriding the pause screens. Or in Bulk by selecting the games and press Ctrl+E to start the Bulk Edit Wizard.