JoeViking245

You and me both. lol When I searched the error, that was one of the "possible fixes". So simple. Yet so mind boggling. Glad to hear [at least] that is all working now!

Can try this: Can try this:

Thanks. The MAME Output says there's something messed up with the audio. (Not a common issue.) It could be a DirectX thing. If you're running the latest 0.278 MAME release (not an issue in 0.277), it could be that you have the Realtek app "Nahimic" running on your system. I've even heard your speakers not being plugged in can cause this and/or plugging in headphones fixes it. If none of that "turns on any lightbulbs" for you, we can start simple.... Have you done some customizations in MAME? Look in your MAME's root folder for "mame.ini" and [temporarily] rename it to something like "old-mame.ini". Also look in your C:/MAME/ini/ folder and do the same thing. (there should only be 1 mame.ini altogether and will be in one of those 2 locations). Click Test Game and see if the output's the same.

Only certain emulators have that feature available. Generally the more popular (recommended) ones. Which coincidentally are also ones that regularly have updates. If you go to Tools < Manage < Plugins... you can see which ones are available. (or just at the section your screen comes from. )

A link to the .NET 3.1 dependency can be found in the LaunchBox Strategy Guide under Moving Your LaunchBox Instance to a New PC. In general, most ("newer") Windows installs will (should) have the DirectX runtimes. But if you have issues with the PC you connect to, that's something to look at.

Because of how Steam games (internally) launch another application that is the actual game, the LaunchBox pause menu cannot innately be used with Steam (and other applications that 'sub-launch' their games. ("sub-launch" is not the technical term. But I don't know what is. And it sounded good to me. )

And the game you're trying to launch (Asteroids for example) still doesn't launch from LaunchBox? If so, see if this plugin can provide any insight as to what might be going wrong. With LaunchBox closed, follow the Installing and Using instructions.

Can you share another screenshot of the section where you added that parameter? Having 2 folders with the same contents won't cause any conflicts. As long as the files you imported are still in the folder you imported them from.

No worries. Were you able to get it to work with my suggestion?

You got this! We have faith in you. Though seems like a lot of work for all f o u r games. Nonetheless, when you're on a mission, you gotta follow through.

Since your path to the Roms folder has spaces in it, try putting that part within quotes. "E:\Fujitsu - FM Towns Marty\Roms"

Maybe try the forgot password? But I suppose it'll try to email you [again] and we know how that went last time. But could still try it. Otherwise, may need to email support or see if they respond here tomorrow (normal business days). (or both)

The LaunchBox Games Database site login now uses the same credentials (user name and password) as your Forums login. No need for separate ones. But you do still need login separately.

Assuming with your premium license you've updated to at least v13.21, you can read about the new locations here: LaunchBox Media Pack Feature – Version 13.21 - LaunchBox

Arcade Games Won't Launch (stand-alone MAME) - Troubleshooting View File Question: "When I try to launch an Arcade game using stand-alone MAME, all I see is a flicker of a black screen then it goes right back to LaunchBox. Why?" Answer: "Because something is wrong with your ROMs and/or something is wrong in your settings." This plugin gathers data and provides checks to help you determine what that something may be. Features: Shows the required dependency files needed (if any) Launches the game in MAME and captures the command window output that you never see. (Potentially useful 'Why the game isn't launching' data) View the emulators Running Script. (Typically never contains "the issue". But doesn't hurt to look.) Verifies ROM and dependency (BIOS & Device) file(s) exists and are accessible to the emulator when launching**. If found, checks and verifies the zip file contents (all inner files exist and CRC32's match). If a CHD is required, this only verifies the file exists and is accessible to the emulator when launching**. ** "accessible to the emulator when launching" The plugin looks for the "rompath" setting per MAME's order of prescience. This dictates which folders MAME will scan for ROMs and dependency files. This will NOT "fix it" for you. But should tell you everything you need to deduce "why" you can't launch a MAME game via LaunchBox. Once you know why, all you need to do is fix that part of the equation. Requirements: Requires LaunchBox 13.19 or newer Requires the games emulator to be mame.exe Only works with MAME Arcade machines. No software lists Only works with ROMs that are .zip (Not .7z) Since MAME is generally an all-or-nothing type of thing, this is essentially a one-off plugin. But if needed, it should provide sufficient information in a one-stop-shop to resolve your MAME launching issues. Installing: Extract the contents of the downloaded zip file into your /LaunchBox/Plugins/ folder. e.g. D:\LaunchBox\Plugins\MAMEtroubleshooting\MAMEtroubleshooting.dll Using: Start LaunchBox Right-click an Arcade game and select MAME Troubleshooting. Read through the Quick Analysis tab Click Test Game to capture and see MAME's command window Output If it indicates the game launches fine and you know it doesn't, click it again to see if it tells you a different story. Note: clicking a 3rd time won't change the answer it showed the 2nd time. Click Running Script to view the emulators Running Script. This usually is never the issue. But doesn't hurt to look. Click Check ROM(s) to scan the contents of the games ROM and Dependency (if any are required) zip files. This verifies the contents of the zip files and cross-checks those contents' CRC32 value against what MAME says they should be. (Works with both Merged and Non-Merged sets) For games requiring CHD files, it will only check that they are accessible to MAME and provide the files size. It won't do a hash check. Click Save Report to create a text file of all the produced data that you can share with your friends and family. Files are saved to /Plugins/MAMEtroubleshooting/Reports/[rom_name].txt (or /Reports/[rom_name] (Clone of [parent_rom]).txt) Once created, 2 icons will appear to open the txt file or open the /Reports/ folder. Once you've studied all the data and see "the issue", fix it and play games. 😎 Submitter JoeViking245 Submitted 06/29/2025 Category Third-party Apps and Plugins  

the {dash}id{equals}1 (-id=1) would go in place of the "full/path/to/rom.zip" @echo off echo Starting 3DSen with game... "D:\Launchbox\Emulators\3dSen\3dSen.exe" -id=1 echo Game loaded. pause You might need to add cd "D:\LaunchBox\Emulators\3dSen" before the 3dSen.exe line so that you're starting in that directory. (unless the .bat file is already in the same folder as the exe). Or... you might not need it. Dunno. If you want to launch this [batch file] from LaunchBox (aka: not have an associated emulator) and have it work with the shutdown screens, you'll want to add a "wait for game to exit before continuing" (/w) start /w "" "D:\Launchbox\Emulators\3dSen\3dSen.exe" -id=1 (when using this in LaunchBox, you don't want the other lines.) But doing it this way, you then have a bazillion batch files. But if you insist on doing so, you'll want to hide the command prompt window that pops up. To do that, create a shortcut of the batch file. Right-click the [new] shortcut, select Properties. Change the Run line to Minimized. Click OK to save. Then add the shortcut to LaunchBox. Note: you'll now have a bazillion batch files and another bazillion shortcuts.

That's kind of what I figured. That's exactly what I hoped. Glad [in the end] it works. Be sure to read through all the other cool Data Bindings in The LaunchBox Strategy Guide link I gave above. You might find something you never knew you wanted to add to your theme.

The error indicates something is up with your license file. Email support@unbrokensoftware.com and they can sort it out for you.

It shows using ActiveGame, but it may work for SelectedGame also. Data Bindings - LaunchBox ActiveGame.PlayTimeHms The selected game’s playtime in “##h ##m ##s” format <TextBlock Text="{Binding Path=ActiveGame.PlayTimeHms}" Foreground="White" />

I asked for 4 screenshots. You provided 2. Only 1 of the 2 was 1 of the 4 I asked for. I try not to ask for things unnecessarily in order to best help. Hopefully, I may still be able to help. In your 1st screenshot under Default Command-line Praameters, add -rompath %romlocation% after what's there. -keyboardprovider dinput -rompath %romlocation%