JoeViking245

@mgtroyas I've posted an update on the plugins main download page to (hopefully) fix the list sorting and (for sure) the popup message(s). Please let me if the "Select a Computer/Console to Import" list still isn't sorting correctly for you. As always, to you and everyone else, thank you for your feedback and suggestions!

Thanks!! Ya, this has definitely been looked into. Unfortunately there doesn't seem to exist any filters nor categories for softlists like there are for Arcade Machines. But if you do happen to come across something like this for softlsits, please let me know. And you right, it would round out the plugin quite nicely.

That message box was put there for testing purposes and never got removed. Click OK (Aceptar) and the process will finish. (I'll fix that too.?) For what it's worth, that message is saying you're updating that particular softlist (FM-7) and MAME has renamed an existing games' Title. Same rom file_name.zip, revised Title.

Thank you so much for the kind words!! The odd thing about this request is that I've never seen the list NOT be sorted. Guess I just got lucky. I will get that resolved for the next update. Ya, definitely out of my hands. If you haven't already, try using the 2nd option when Downloading. Selecting this won't replace the games Title. Then as far as which game ID it associates to, I've no idea how close the Title has to match to the database to get selected.

If those are the commands you want to send when MAME starts (4:3) and when MAME exits (16:9), In the Running AutoHotkey tab of your MAME emulator, put: Run, SerialSend.exe /baudrate 9600 /devnum 5 \"M3x1\" $esc:: { Run, SerialSend.exe /baudrate 9600 /devnum 5 \"E\" WinClose, ahk_exe mame.exe } The \ (slash) in front of the quotes are needed to make them literal. If SerialSend.exe is not in your PATH and you need to point directly to the file location, put that full path in quotes. i.e. Run, "F:\My\Extra Programs\SerialSend.exe" /baudrate 9600 /devnum 5 \"M3x1\" Do that on both "Run" lines. Lastly, if your using an older release of MAME, change mame.exe to mame64.exe. (or to whatever variant of the MAME executable you're using).

The only way to do that (both Free and Premium versions) is to start LaunchBox/BigBox using a batch file (or other similar script type language). Something like: start "" "F:\MyProgram Folder\MyProgram.exe" start /w "" "D:\LaunchBox\LaunchBox.exe" taskkill /F /IM MyProgram.exe The line beginning with "start /w" will start LaunchBox (or you can change it to BigBox.exe) and WAIT ("/w") for it to exit before executing the next command. In this case, exit the program you started on the 1st line.

You can try getting medieval on joytokey and instead of WinClose, use: Process, Close, joytotkey.exe It's not a desirable way to do it as it uses a 'brute force' approach to KILL the application. Kind of like pressing and holding the power button on your PC to shut down Windows.

Add an Escape hotkey to the Running AutoHotkey Script and have it close the emulator and joytokey. ;================================== ; Running AutoHotkey Script ;================================== run, joytokey.exe $esc:: { WinClose, ahk_exe joytokey.exe WinClose, ahk_exe myEmulator.exe }

You might be able to start that 'pre app' in the Running AutoHotkey Script tab for the emulator. I mean, you can. But I'm not sure if it'll kick off "before" the emulator starts. Or if they'll launch simultaneously. So if the pre app has to be fully running before the emulator starts, I guess you have a 50/50 chance with this. But again, I'm not sure exactly the order they load. If the pre app loads fast, you should be good.

Not sure the key press is possible in a batch file, but since you're asking in the AutoHotkey thread, how about an AHK script instead? SetTimer, Quit, % 14520000 ; (4hr * 60min * 60sec * 1000) + 2min = 14,520,000 = 4 hours + the 2 minute wait Sleep, 120000 ; 2min * 60sec * 1000 Loop { Send, {Down} Sleep, 17000 ; 17sec * 1000 } Quit: ExitApp Though I suppose you could create a batch file that launches the AHK script.

Yup. More than likely. LaunchBox starts the 'game' (in your case the batch file) and executes the Running AutoHotkey Script. Once the 'game' exits, LB closes/exits the script. In this case, the batch file starts the game and then Exits itself. LB see the 'game' [batch file] exit, and bam! No more running script. One option (and probably the easiest to implement): To keep your batch file "alive", add in a /w on the start line. start /w "" myGame.exe This will wait for "myGame" to exit before 'exiting' (or continuing any subsequent commands in) the batch file.

I doubt it. An executable file (.exe), by any other name is still an executable file. Unless the exe spawns another program. You stated that your script worked outside of LaunchBox, so we know "WinClose, \serve.exe" is a good command (provided you use "SetTtitleMatchMode, 2"). So it could spawn another exe, but \serve.exe happens to be in the windows title. No. I think the issue is that your original script waits for RetroArch to close, then tries to close serve.exe. (hear me out....) If the script is in the Running AutoHotkey Script section for the emulator (which is where it should be as @Koroth stated), when the emulator (RA in this case) exits, LaunchBox closes out the Running AutoHotkey Script. So basically it never reaches the next line of the script. Which is to close serve.exe. Try Koroth's script as suggested where you set Escape to close RA and serve. Just is case, maybe switch the order of those 2 and close serve first. If "WinClose, ahk_exe serve.exe" still doesn't work, add in the "SetTitleMatchMode 2" at the top and change that line of the escape sequence to "WinClose, \serve.exe".

"Automatically Run After Main Application" A.K.A. 'run after the game exits.' The "Wait for Exit" (only available with "...Run Before...") waits for your Additional App to exit Before starting the Main Application. This is useful if say you have a batch file that moves/renames configuration files for the specific game. You want that to completely finish before launching the game. The issue that can arise with "Run After" is if your Main Application 'spawns' another program that is the actual game. A simple example would be: your main app is a batch file ["runMyGame.bat"]. And in the batch file is something like @echo off G: cd "G:\myGames\coolGames" start "" "BestGameEver.exe" When you launch the game in LaunchBox, "runMyGame.bat", it then starts "BestGameEver.exe" and closes/exits/quits the batch file, while BestGameEver is still running. LaunchBox sees "runMyGame.bat", the 'Main Application', has Quit, so executes the "Run After".

I don't know how to use dat files in conjunction with the Full Set Importer. You could create one though at Arcade Database and filter only for Arcade. You can also filter for Emulations Status: All, Working Only, Working and Imperfect... and all sorts of other good stuff. The DAT file output is formatted for CrlMAMEPro (if that matters) and you can specify which MAME release/version you need it for.

Since LaunchBox gets the 'list' of roms from your copy/version of MAME (mame.exe -listfull), you could try using an Arcade Only version of MAME. I don't know if you can find one that's already compiled for the release you're currently using. But you could always compile your own. make SUBTARGET=arcade

Since you have a curated set of roms, you should be able to do the Full Set import (for a proper Import) and then Scan for Removes ROMs. And that'll take out the 'blanks slots' (the entries that got imported, but are not in your particular romset). But if the unplayable games you're wanting are in not your romset, then.... never mind.

From the other post I linked... - In the ‘../MAME/cfg’ folder, copy “default.cfg” and paste it into the ‘../MAME/ctrlr/’ folder. From here you can rename it to something like “MyControls.cfg”. It probably have said "... you should rename it..". Which I assume is what you did. Renamed it to "zerodelay_x2" because that's what your mame.ini is looking for. (I'm guessing you mistyped when you just now wrote "zerodelay_cfg" [vs "zerodelay_x2"?]). Whichever it is, make sure it's name is the same as what's in your mame.ini. So it's now copied into the ctrlr folder, is properly renamed... now insert the "<mapdevice device=" lines just as you did before [but with those corrections noted above].

Just fix those 2 lines in whatever file you're loading your controllers with. According to the verbose out you showed in 'dmList.txt', you're using "zerodelay_x2.cfg" to load your controllers. So change them in there. I'm guessing in your mame.ini file, you have listed under # CORE INPUT OPTIONS... "ctrlr zerodelay_x2". If you have that in there AND you're trying to make changes to default.cfg, you're you're going to have a real tough time troubleshooting.

@darrenmarchand It looks like it loaded your 2 Generic USB Joystick's like it was supposed to. (note: "joycode #0" shown here is your "JOYCODE_1". "joycode #1" is your "JOYCODE_2") Looking again at your zerodelay_x2.cfg file, I think you need to revise the lines for Kinmotek and XInput. For those 2, remove the stuff before (and including) "Device id: " after: Moral of the story, put in the devices ID info, but not "Device id: ".

@darrenmarchand May I see what your verbose output looks like (with at least your 4 main controllers plugged in and on.. if not everything, including wheel etc.)? Open Windows Command Prompt and navigate to your MAME main folder. At the prompt, type mame.exe -v >dmList.txt (change mame.exe to mame64.exe if needed) After the MAME main window gets fully loaded, Exit MAME. (don't be tempted to play games. ) Drag and drop the new "dmList.txt" file that it created into your reply here.

It's saying your cdimono1.zip is missing those 2 files.

That's probably because of the language your chd files are in. cdimono1 is for PAL and cdimon2 is for NTSC.

You asked. We delivered. (Bulk) Remove Additional Applications (though may be a little bit too late. lol)

(Bulk) Remove Additional Applications View File (Bulk) Remove Additional Applications The intent of this plugin is to Remove the same** Additional Application for all games in a given Platform, all at one time. **Same is determined by the Additional Applications Application Name and Application Path. If they match exactly, they are the ‘same’. Why use this? Quite possibly because you used the Bulk Add Additional Applications plugin and you clicked “OK” before realizing you forgot to add in the Command-Line Parameters or it's simply not needed anymore. Setup: Download and extract "BulkRemoveAdditionalApps.dll" from the zip file and place it in your Plugins subfolder of LaunchBox. Right click the dll file, select Properties, and click "Unblock" (if it's there) and click OK. Using the plugin: - Click Tools and select "Bulk Remove Additional Apps". - Click the dropdown box and select a Platform. - Click Get to show the Additional Apps for that Platform.*** - Check the Remove box(s) for the Additional Apps you wish to delete. - Click Remove to delete/remove all occurrences of those selected Additional Apps.**** *** The plugin will 'combine' any Additional Apps that have the exact same Name AND App Path, and only display one of those. When you remove that "one", all occurrences (having the same Name and Path) will be removed. ***Example: You used the Bulk Add Additional Applications plugin to add an Additional App to 245 different games. You named it “My Run-Before App” and set the Application Path to “D:\MyApps\RunBefore.exe”. This plugin will only display it in the list once, instead of 245 times. (Because they all “have the exact same Name AND App Path”.) **** Once you click Remove, the apps you had selected will get removed/deleted forever. There is no undoing this once OK is clicked! (unless of course you have your backup file that was created with the LaunchBox built-in Automatic Backup feature.) Submitter JoeViking245 Submitted 05/08/2021 Category Third-party Apps and Plugins