Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    4,020
  • Joined

  • Last visited

  • Days Won

    33

Everything posted by JoeViking245

  1. I think what you'll end up doing is to set up dual inputs for each player. Assuming your control panel is connected through something like an I-Pac encoder and the buttons correspond to keyboard keys (i.e. Player-1 Button-1 = Ctrl, Button-2 = Alt, 3 = Space, and so on) and the controllers are all X-Input... you'd have something like (generally speaking): Player-1 Button-1 = Ctrl OR Controller-1 Button-1 Player-2 Button-1 = "A" OR Controller-2 Button-1 These will need to be setup on a per emulator basis. Which at first will seem daunting as well, but it's really not that bad.
  2. Any chance you're actually importing them into separate "Platforms"? You need to setup each Platform for the emulator (in LaunchBox). Go to Tools, Manage Emulators, select RetroArch and Edit. Then go to the Associated Platforms tab. (As you've done so far). It sounds like you already have Atari 2600 in there. You need to add the 'other' Associated Platform(s). And they need to be named EXACTLY as you have them named. "Atari 2600 PAL", "Atari 2600 NTCS", etc. Scroll to the bottom of the list of Associated Platforms to the blank/empty cell. Click the 1st, left cell once, and start typing the name of the Platform you want to add. When you type, for example "a", it will show a list of the Platforms you have that start with "a". Select the one you want to add. i.e. "Atari 2600 PAL". Next select the appropriate core you want to use. i.e. "stella_libretro". Add any Extra Command-Line Parameters you want. i.e. "-f" ([without quotes] to load RA in Full Screen). Next check the box for Default Emulator. Do that for any other Platforms that may be missing, then click OK, then Close.
  3. The 1st video on the 1st post of this thread shows how to set it up in MAMEUI (which is the same process as regular MAME).
  4. Sounds like your default.cfg is dialed in nicely for all your regular games. But changes need to be made when loading ArcadeStick. You might want to first combine these to files similar to what @sundogak shows in his 'example controller file' in the 1st reply above. Which will look a lot like this.. ArcadeStick.cfg Next, figure out exactly which "inputs are messed up a bit" and change those in ArcadeStick.cfg. I don't think you can simply load ArcadeStick, make your input changes and have it save to "ArcadeStick.cfg". Not really sure how that part works. I'm going to take a wild guess that the joystick works, but some of the buttons are in the wrong order or don't work at all. If you look at the file I attached (which is your 2, combined) and scroll down to where the "P1_BUTTON..." section starts, you have: Button-1 reassigned to Button-3. Button-2 to Button-1. Button-3 to Button-2. (4, 5, and 6 ok). Button-7 is reassigned to the "left trigger". And so on. I've no idea what the button assignments are on the Real Arcade Pro 3. I've only seen pictures (and didn't see any "triggers" ).
  5. If you've created your 2 controller configuration files, then yes. Let's say you have your default one "Controls.cfg" that you created. This one has your Joy1 thru 3, and Arcade Stick as Joy4. This will be the one you have set in your mame.ini for all games. Now create one (let's call it "ArcadeStick.cfg") that has your Arcade Stick as Joy1 and then the others as Joy2 thru 4. Then for the games you want to use the alternate controls [ArcadeStick.cfg] for, I see 2 options: Option 1: Edit the games. Under Emulation, check Use Custom Command-Line Parameters: and type in -keyboardprovider dinput -ctrlr ArcadeStick That said, I'd recommend Option 2. Option 2: Download and install this.. Then in LaunchBox, in the upper left, select Playlist and then select Arcade Fighting Games. (assuming you have this playlist) Click on one of the games, hit Ctrl+A (selecting all games), then right click and select Bulk Command Line Editor. Fill in the above command-line and click Finish. Should be simple enough.
  6. According to the Arcade Database, there are 18, [up to] four-concurrent-players, "Working" (vs "Working and imperfect" or "Imperfect") Fighter [genre] games in MAME. This is Parent roms only. But on the upside, there are only 18. (Unless you want all clones too. Then there's like 105.)
  7. Try deleting missile.cfg if you have it (basically start fresh for that game). Then start the game and go into the configuration for inputs and check that up/down left/right analog is set to mouse (x and y respectively). At least that's how the trackball on my cab is working. When you're in analog controls for the game, you should be able to adjust the sensitivity up to make it more responsive/reactive.
  8. Replaced the download with one that works with LaunchBox versions 10.14 and newer. At least it should. Let me know if you have any issues.
  9. I'm thinking just add 5 lines right before parsing list.xml: string listXML = @"D:\Emulators\MAME\ui\list.xml"; XDocument doc = XDocument.Load(listXML); var machineORgame = (string) doc.Element("mame").Element("machine"); //1 Look for "machine" if (!string.IsNullOrEmpty(machineORgame)) //2 If it's there.. machineORgame = "machine"; //3 We have a winner else //4 machineORgame = "game"; //5 Otherwise it must be "game" var allRoms = from r in doc.Descendants(machineORgame) // And whatever it was, use it select new { Rom = r.Attribute("name").Value, Title = r.Element("description").Value //..... //.... };
  10. When MAME and MESS became a single emulator (release 0.162 - May, 2015), they changed how they store the data. But only for what they call the rom file. I assume this was to create a better distinction between softlists (MESS) and arcade (MAME). Prior to 0.162, individual [Arcade] rom information/data was stored under "game". Starting with release 0.162 they are stored under "machine". So with 0.159, the Mame.xml would have its data listed under "game", and the importer is looking for "machine". Anything from MAME release 0.162 to current should work with LaunchBox's built in importing tools. As always, be sure your version of the MAME executable and the romeset you are using, match.
  11. v4 is out. (less than 17 days [this time] from re-asking. ) New feature: Import only rom Titles that exist in your Source Folder. When you check the "Import only games that exist in the ROMs Source Folder" box, only those Titles will be imported. This will not remove any existing entries in LaunchBox. Only add new ones or modify existing ones (per MAME changes in the hash file). Did some minor testing with this. But no major 'stress-testing'. Please let me know if you come across any issues.
  12. Change the "Y" (wye) to a "v" and always use lowercase letters. Send, ^!v And make sure the always-running script is using lowercase as well.
  13. I'm assuming when you say 'Virtual Pinball' you're talking about Visual Pinball X. If not, just change the exe filename you're waiting for to close. One possibility.. have your Running AutoHotkey script for your VPX emulator be: [not tested] Run, "d:\arcade\Pixelcade\curl.exe" "http://localhost:8080/quit" , d:\arcade\Pixelcade\, Hide Sleep, 10000 Process, WaitClose, vpinballx.exe Run, d:\arcade\Pixelcade\pixelweb.exe, d:\arcade\Pixelcade\, Hide I put in a 10 second delay (that probably doesn't need to be that long) to give VPX time to fully load before Waiting for it to Close. And I trust if you're playing a table, you be playing at least that long.
  14. OK. My bad. I apologize. I built it using LaunchBox v11.10 beta 3. I deleted the original file and replaced it with one that will work with LaunchBox v11.8 and newer.
  15. Then LaunchBox is not [completely] loading it. This is usually because the plugin file (the dll file) is blocked. But you indicated you unblocked it. Can you attach a LaunchBox debug log for me? (if you would please, drag and drop the file in here rather than copy and pasting its' contents.)
  16. Forgive me, but I'm not following what you're saying.
  17. Another possible option is to use this plugin. Although the nice thing about JayJay's AHK method, it's easier to change the AHK script then to redo Additional Apps. (Assuming you're comfortable with AutoHotkey.) But always like to (well, try to) give options.
  18. (Bulk) Add Additional Applications View File (Bulk) Add Additional Applications A.K.A. (Bulk) Add Run Before/After Main Application The intent of this plugin to add the same Additional Application to more than one game, all at one time. More specifically, it is to add an Additional Application you want to run Before and/or After the selected games. *Works with LaunchBox versions 10.14 and newer.* Setup: Download and extract "Bulk Run Before-After.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: Select more than one game (or all of them) in your Platform. Right click on one of the selected games and select "Bulk Run Before/After Main Application". Fill in the Application Name, Path to the program, any necessary Command Line Parameters and then check the appropriate box if you want it to run Before or After (or both or none) the Main Application. Click OK You should probably test this on only 2 or 3 games first BEFORE you decide to do your entire Platform. There is no [bulk] undo (See Additional Notes). Additional Notes: Once you click "OK", the Additional Application is added to each game you had selected. There is no Bulk Edit or Bulk Remove**Additional Application(s). (at least by me) It does require that you give it an Application Name and an Application Path. It will verify that your Application Path points to an existing file but it will not check if there's an existing Additional Application with the same Name. **If you clicked OK when you should have clicked Cancel, you can remove them with this plugin: (Bulk) Remove Additional Applications Submitter JoeViking245 Submitted 03/12/2021 Category Third-party Apps and Plugins  
  19. Version 2.0

    775 downloads

    (Bulk) Add Additional Applications A.K.A. (Bulk) Add Run Before/After Main Application (July 10, 2023) This plugin is no longer supported. But [for now] still works. Please see its successor: Bulk Add/Remove Additional Applications The intent of this plugin to add the same Additional Application to more than one game, all at one time. More specifically, it is to add an Additional Application you want to run Before and/or After the selected games. *Works with LaunchBox versions 10.14 and newer.* Setup: Download and extract "Bulk Run Before-After.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: Select more than one game (or all of them) in your Platform. Right click on one of the selected games and select "Bulk Run Before/After Main Application". Fill in the Application Name, Path to the program, any necessary Command Line Parameters and then check the appropriate box if you want it to run Before or After (or both or none) the Main Application. Click OK You should probably test this on only 2 or 3 games first BEFORE you decide to do your entire Platform. There is no [bulk] undo (See Additional Notes). Additional Notes: Once you click "OK", the Additional Application is added to each game you had selected. There is no Bulk Edit or Bulk Remove**Additional Application(s). (at least by me) It does require that you give it an Application Name and an Application Path. It will verify that your Application Path points to an existing file but it will not check if there's an existing Additional Application with the same Name. **If you clicked OK when you should have clicked Cancel, you can remove them with this plugin: (Bulk) Remove Additional Applications
  20. If you created and compiled a script, you can edit the game and create an additional app to Automatically Run Before Main Application. If you'd rather not compile it, you can set it up similar to [the 1st part of] this post. You will (probably) need another script setup to Automatically Run After Main Application to Exit/Close the 1st script.
  21. You can. But your games' title would be something like "lordmon" instead of "Lord Monarch". Which really, is the whole reason this plugin was created. But then ya, the command line thing you'd need to do also.
  22. What would make that nice is if there were categorized ini files like MAME does for Arcade Machines. Like genre, controls, number of players etc.. But I just haven't seen anything like that for softlists.
  23. To be honest, no. And to add some brutality to that, I haven't even put any thought into the importing of a curated set. Have you tried LaunchBox's built-in Scan for Removed ROMs? I'm thinking that's going to be your golden ticket for what you're wanting to do. It's a little less direct, but makes good use of existing tools. So use this Importer (setting the Destination Folder to your update folder), then Scan for Removed ROMs. For "updating", that was done in release 3.0. 17 days after my quote about "beyond the intent of the plugin". Where it scans your existing Platform [during the Import process] against the 'new' MAME updated xml and renames titles and roms as necessary (and of course, adding new roms).
  24. Do you have it turned? Tools, Options
×
×
  • Create New...