JoeViking245

You need to be in cocktail mode. The upright cabinet only has (and can read) one set of controls. However, the cocktail cabinet does have 2 sets of controls in which the defined player 2 inputs would be [then] recognize.

Looks like the 5-year-old plugin Steam Tools is causing issues. With LaunchBox closed, remove the plugin from the /LaunchBox/Plugins/ folder and restart LaunchBox. See if the issue goes away.

The references are asked for in the xmlns: lines. What they asked for can be found in the LaunchBox/Core/ folder. But I always get an error when trying to add them. If you figure it out, please do share.

I might suggest trying an emulator that's been updated a little more recently (less than 16 years?). Here you can learn about one and how to set it up in LaunchBox.

No problem. It's what we do. Your Game is pointing to "punisheru.zip" (the USA version) and you show the zip for "punisher.zip" (The World version). Do you have "punisheru.zip" in that folder? If not, you can try to point to the World version (in the Launching section [just remove the last "u"]) and see if that works when launching from LaunchBox.

I was always told all required files are in the games zip file in a non-merged set. Checking one of the CPS1 games, they're not. I'd assume your titles.clones folder held a complete set, which should also have the file "qsound_hle.zip". Is that in Device file in there? Edit: I stand corrected. The file inside of qsound_hle.zip ("dl-1425.bin") is inside the CPS1 ROMs that require it [in a non-merged set].

Had to ask. Can you share some screenshots of a game's settings for one that isn't working through LaunchBox? Edit the game and show one of the Launching section and the Emulation section.

A non-merged set will have all the necessary file inside the respective games zip file (including BIOS). I would open stand-alone MAME, go to one of the CPS1 games and try to launch it. It'll tell you what the error is if it doesn't start.

Are your ROMs actually located in a folder on the D drive called titles.clones? Seems an odd folder name.

It doesn't sound like BigBox is "losing focus" because 'tapping a key' makes everything happy again. Now if you did a mouse click on the BB window, or Alt+Tabbed to the window, then I'd say yes. It sounds more like the USB port (or hub?) your I-Pac is plugged into is going to sleep.

In short 'BigBox'. My cab originally had Maximus Arcade frontend (long out-of-support). It was great and served it's intended purpose. But I wanted a little more 'flash'. Not really knowing anything about these things called "frontends", I spent about 3 weeks researching looking and testing what was available. Found 1 that seemed to check all the boxes and spent a day trying to set it up. After that day of frustration [and not really even getting it going] I searched some more and came across LaunchBox. After quickly being able to get it up and running and then spending some time seeing what all it has to offer, I was convinced and bought a 1-year license (just-in-case, because that's how-I-roll). Along with several other enhancements, the license also opened up BigBox. Within a few months, I knew I was going to upgrade to the lifetime license when the year was up. This was about 7 years ago. Once you get LaunchBox/BigBox all setup to your liking, BigBox has a feature you can enable to boot directly to it when the computer (cab) is turned on. And no, it doesn't just add BigBox.exe to your Windows startup folder. But that's just my experience/observation/opinion.

Before the 'Send' line, try adding SetKeyDelay, 125, 50 Edit: Or longhand like LaunchBox does it from the Pause Menu ; RetroArch loads state with F4 key by default Send {F4 down} Sleep 50 Send {F4 up}

Here's one way you can do it: Create an AutoHotkey script and save the file [somewhere] as KillXpadderAfterLB-BBcloses.ahk. (you can name the file whatever you want, as long as it has the file extension .ahk. Just be sure that it doesn't save as filename.ahk.txt) The script is just a text file with the .ahk file extension. In the script, put: boxes := ["LaunchBox.exe", "BigBox.exe"] Sleep 10000 Loop % boxes.length() { if (WinExist("ahk_exe " boxes[A_Index])) { Process WaitClose, % boxes[A_Index] Process, Close, "Xpadder.exe" Break } } ExitApp In LaunchBox, go to Tools, Options, Startup Applications. Click Add Application. For the Application Path, navigate to and select: /LaunchBox/ThirdParty/AutoHotkey/AutoHotkey.exe For the Command Line Parameters, put (inside of quotes) the full path to the file you created above. i.e. "D:\Misc\KillXpadderAfterLB-BBcloses.ahk" This works for both LaunchBox and BigBox. So select Start With Both. Click OK to save and close. Restart LaunchBox for it to take affect. Note: I don't use Xpadder, but I'm pretty sure the 'Process, Close' method is how it gets shutdown.

View game specific commands from MAME's command.dat View File Inspired from MAME's built in feature in the main UI (and via their in-game Tab menu) and Ben Baker's CPWizard. View information from MAME's command.dat to show: CONTROLS CHEATS HOW TO PLAY COMMON COMMANDS SECRET CHARACTERS Included in the plugin is a "MAME Command" Custom Badge (LaunchBox Only [unless someone figures out how to show Custom Badges in BigBox]) This will show the badge for games included in command.dat Installing the plugin Download and open the file using 7zip. if you don't use 7zip, first unblock the file (Right click, select Properties, and click Unblock) then open it as you normally would. Extract the main folder from inside the zip file into ..\LaunchBox\Plugins\ i.e. D:\LaunchBox\Plugins\MAMEConmmandDat\ (the main folder "MAMEConmmandDat" and all its subfolders are required for the plugin to work!) Start LaunchBox or BigBox Enabling the Custom Badge In LaunchBox, click Badges, Plugin Badges, "MAME Command" You can change the badges image by replacing the image ../LaunchBox/Images/Badges/MAMEcommands.png Using the plugin LaunchBox: Right-click on a game and select MAME Commands. BigBox: In the Game Details screen, scroll to the bottom on the list and select MAME Commands. To scroll through the page, use your keyboard Up/Down arrow keys, mouse wheel or your controller's left joystick (or DPad) Up/Down. To close the window, press Escape, or on your controller press your mapped Exit Game (LaunchBox) or Close Active Window (BigBox) button(s). Version 0.262 of command.dat is included. Future updates can be found here: https://www.progettosnaps.net/command). Just replace the existing file located in the plugins /Data/ subfolder. As always, all thoughts, views, opinions, suggestions, comments and accolades are welcome. 😎 Submitter JoeViking245 Submitted 04/15/2024 Category Third-party Apps and Plugins  

That being a premium feature was an something that I almost forgot about. There are quite a few quality-of-life enhancements (visual and function) with the paid version. But if what you have works for your needs, you're probably good-to-go. Just one request, once you do add all your systems, don't forget to actually play the games too, Always glad to help. 😎

If you have LaunchBox premium, they'll appear when you restart the program. If you don't have a premium license, I believe they will never show.

Copy those images into the Platforms folder. Then make sure they're the same Name as the actual Platform. i.e. Capcom Play System I.

If indeed the CPS2 games all work directly from within MAME (from their 'new' ROM location)... You most likely have all the paths (to the regular ROMs, CPS1, CPS2, CPS3...) listed in mame.ini's 'rompath' (good job for doing that. ). What's happening is that LaunchBox is overriding mame.ini rompath with [only] the folder that the ROM your launching is actually in, via the Command-line Parameter (-rompath %romlocation%). And you probably don't have "qsound_hle.zip" in with the CPS2 ROMs. IF your rompath is indeed setup as it should be in mame.ini (to include all the different ROM folder locations), you can safely remove the last part of the Command-line Parameters (-rompath %romlocation%). Alternately, you can just copy "qsound_hle.zip" into your CPS2 ROMs folder.