JoeViking245

In LaunchBox, for your MAME emulator, do you have anything like "-nofilter" listed in the Default Command-line Parameters?

It depends on if they updated the [individual] ROM. If you have a ROM for v0.230 and your mame.exe is 0.249, if they haven't updated the ROM in 19 versions you should be fine. BTW, there's no easy way to determine which version your ROM set is for. Most of the time when you find a set, they should say for what version of MAME they are. If not, you're playing roulette. If you had LB install it for you, you manually changed the default command-line parameters. Edit your MAME emulator and add a Space and then this right after "dinput" -rompath %romlocation%

@12shiko You can click Tools, Import, Manually Add Game... to import a single game.

Short answer, no. The reason the one game worked in MAME, after moving it into MAME's /rom/ folder, is that's MAME's default location to look for ROMs. But they don't have to be in there to work. One of the biggest issues that can happen with MAME is not matching the ROM set version with the MAME (mame.exe) version. What version is your "custom ROM set" for? (this info is helpful for troubleshooting) Did you have LaunchBox install the MAME version to match? If unsure, what version did you have LB install? In order to further help troubleshoot issues with MAME, please provide the following Screenshots: Go to Tools, Manage, Emulators, select the emulator you’re using for MAME and provide a screenshot of the following sections Details Associated Platforms Select one of your Arcade (MAME) games and click Edit (or press Ctrl+E). Provide a screenshot of the following sections Metadata Launching Emulation

You're welcome! But to be fair it was @launchretrogirl2562's idea to delete the script (brute force method of commenting out the lines. lol). But since that worked, this leads me to believe that when pressing the Space bar while in-game (Experiment #3), it will close MAME. (Which ain't good. ) Especially if Button-3 on your cabs are mapped to Space. If that's the case, SOMEWHERE you have the Space bar mapped to Exit MAME. Most likely in MAME itself.

I don't think so. That fact that, via LaunchBox, the games DO load indicates MAME and your ROMs are fine. If there was an issue with either of those 2, you wouldn't even see the game. Couple that with the fact that when you run them directly in MAME itself and they run fine. The issue is that when you launch a MAME game from LB, after it IS loaded, something is telling MAME to close after a few seconds. Watching the video, it's 'coincidentally' about 10 seconds after you launch the game. Also note that when it does exit, your selected game jumps to the 1st game in your view. Experiment #1: Click (don't launch) on a game lower down on the list. Say... "1942". The right sidebar will populate with 1942's details. Now press the Space bar. (see "Also note.... jumps to the 1st game..." above). [this is more of a rhetorical experiment] Experiment #2: Edit your MAME emulator. Go to the Running script section. Comment out the last 3 lines using a ; (semi-colon) at the beginning of the line(s). Just like the 1st line is. Click OK to save and close. Launch a game. Is it still exiting the game approximately 10 seconds after being launched? [conditional] Experiment #3: If the game is now NOT exiting itself, does anything happen if you press the Space bar while in-game?

You won't find any of MAME's key assignments in any ini file. MAME's default for the On Screen Display is the ` (tick) key (top left corner of the keyboard, left of "1"). The simplest way to reset that is to delete "default.cfg" in MAME's /cfg/ folder. If you have made other custom Input Assignments that you want to keep, instead of deleting the file: open standalone MAME open General Settings Input Assignments User Interface it'll be the 1st one on the list press Delete press Esc twice click Save Settings To confirm that it saved, exit MAME and then restart it. Navigate to User Interface and see if it still says None. If it didn't save, you probably have default.cfg set to Read Only or you're having MAME load a custom controller configuration file. If it's set to Read-only, right-click the file and select properties. Uncheck "Read-only" and click OK. Open MAME and go through the steps outlined above and then exit MAME. Set the file back to Read-only. If you're loading a custom controller configuration file, open that file (located in MAME's /ctrlr/ folder) with a text editor, and search for "UI_ON_SCREEN_DISPLAY". Change whatever it's assigned to (sounds like KEYCODE_DOWN), to NONE. <port type="UI_ON_SCREEN_DISPLAY"> <newseq type="standard"> NONE </newseq> </port>

Try ror (rotate right) 270 or rol (rotate left) 90. If neither of those work, try one of the auto rotates (autoror/autorol). But make sure you put the others back to 0 (zero) before changing.

In your vertical.ini, what are your current settings listed under #CORE ROTATION OPTIONS#?

1st, your game is in your "MAME" platform. Missing the Edit Game - Emulation screenshot, but I assume it's pointing to your "MAME" emulator. Next, your "MAME" emulator has the Associated Platform "Arcade" assigned, but not the "MAME" platform (which is the platform that the game is in). But don't think those have anything to do with your issue as the game actually does start (for a few seconds). But do check that the game (under Emulation) is pointing to your "MAME" emulator. In the video, did you press any keys right before it closed MAME and jumped back to LB? One odd thing is that when it does jump back to LB, it goes back to the top of your "All Games" list.?.?. (Instead of back to 1942.) In Edit Emulator ("MAME" emulator), is there anything inside Running Script? If so, what?

In order to help troubleshoot issues with MAME, please provide the following Screenshots Go to Tools, Manage, Emulators, select the emulator you’re using for MAME and provide a screenshot of the following sections Details Associated Platforms Select one of your Arcade (MAME) games and click Edit (or press Ctrl+E). Provide a screenshot of the following sections Metadata Launching Emulation

Found in the manual for the emulator... https://openmsx.org/manual/commands.html#fullscreen -command "set fullscreen on"

Try pressing Ctrl+S (or navigate the View Menu).

Adding the quotes will fix the error with files that have spaces in their names.

Right click the 2nd file (Convert All Folder XISO's to XISO.ISO's Bat.bat) and select Edit. Add a double quote ( " ) [not 2 single quotes] around the last part. "%%d" Also, on the next line add "pause" (without quotes). FOR /D %%d in (*) DO extract-xiso -c "%%d" pause Save and close the file and double click it again. Adding "pause" will keep the black window open when it's done so you can see if it errors or is successful.

Ya, looks like they both would go in the same folder. So now just double-click on the other one.

Double click (or select it and press Enter) the .bat file.

I'm not really familiar with all the XISO, ISO, XISO Folder stuff as I don't emulate Xbox. So I don't know what you start with and are supposed to end up with. I am however somewhat familiar with batch files. You say you have a bunch of ISO files in your C:\games\ folder. And that you need to convert from "ISO into Folder". It looks like that's what Darrel's 1st attached batch file will do. "Just put the .bat files and the extract-xiso.exe in the same folder with your games." "Don't work" is pretty vague. Can you maybe give more details on exactly what's not working? Maybe @darreldearthcan see something in your questions that I'm not understanding and can help out.

Did you try using the batch files from a couple posts back?

I imagine a search for "command line" got ugly real fast. lol LaunchBox.exe does not have any command line options available.

There's a plugin that will display an image during gameplay on the monitor you set it up for. It's in the Development and Beta Testing section, but I'm told it works. As in, it could probably go in the regular downloads section. But the interest level was so-so. So it's just as easy to point to that thread. lol There's an updated version about 1/2 down page #2 (v1.1) that displays the images better (scale-wise) and offers [more] options for image selection than the original on page #1.