Jump to content
LaunchBox Community Forums

JoeViking245

Moderators
  • Posts

    4,856
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by JoeViking245

  1. In the one I downloaded from your earlier post, you had it set to Category. "Microphone" is fine because that's what you called it when you added it in Manage Game Controllers. Where your screenshot shows "partial support", that going to make the plugin look for only Category="Microphone" AND Support="Partial Support". So not sure if you want to remove that latter part. In the C# code section, with the latter part it will show in there somewhere something like && Value.Equals("Partial Support"). You'd want to remove that part if you only want to check if the Category="Microphone".
  2. Hmm... worked here using the method described above. (13.25) v13.21 Do you have any folders or images under \Images\Media Packs\Badges\? Where are your default badge images located? (e.g. Steam, Achievements etc.) Media Packs - LaunchBox
  3. Version 6.1.1-beta-1 Improvement: Newly imported games' Application Path will now be saved as relative paths, keeping LaunchBox truly portable. ImportMameSoftwareLists (v6.1.1-beta-1).7z @Tsik RE: hash folder location: A quick test shows that (with LaunchBox not running) if you manually edit the file swlFolders.xml located in this plugins folder and set the <hash> value to a relative location [and save it], when opening the plugin and clicking the 1st "Next" button, the hash files will populate. <?xml version="1.0" encoding="utf-8"?> <folders> <source /> <destination /> <hash>..\Emulators\MAME\hash</hash> <emulator>MAME</emulator> </folders> Note: If you click Browse on that 1st page and set a new location, it will get saved as an absolute path. If all goes well with the ROM's relative application paths, I'll look at saving the Folders paths as relative paths as well in the next plugins official release.
  4. If they're MAME type ROMs (I presume, since using Arcade), try checking this box
  5. Could also try -f true or --fullscreen true from the command-line parameters.
  6. Sorry. I don't know anything about the plugins. But I do know is that using -loadiso will load a .chd file.
  7. If you read the documentation in the emulators "docs" folder, you'll see they don't even have a -loadbin command line parameter [anymore?]. But they do show a -loadiso.
  8. Stick with the default Image Group Boxes and download Advertisement Flyer-Front images.
  9. This is a perpetual issue where HLTB periodically makes changes with how data is retrieved. aka, the plugin is broken. Again. Thanks for bringing this to my attention. I'll see if I can figure out a(nother) fix. No. It will not show there. The Plugin Manager is only for integrated plugins created by the LaunchBox developers.
  10. One thing the plugin does when importing is "clean up" the games title by moving anything in parenthesis to its Version field. You probably found the one scenario where this feature is NOT a good thing. One solution could be: This assumes the ROM set you're working from is a non-merged set. Select a new (temporary) platform to import Under ROM location set the Destination to an empty temporary folder set the Source to where your ROM set is When importing, the plugin will copy those ROMs to the temp folder When done, delete the (temp) platform just created In Windows Explorer, go to the folder the ROMs were copied into Drag & drop those files onto LaunchBox to start the import process for just-those-ROMs This will now grab the correct metadata When done (optional. You decide) Select all games in that platform Then go to Tools < File Management < Change ROMs Folder Path for Selected Games... Change the path to where your [original] full set is located You can now delete the temporary "Destination" folder.
  11. In the Associated Platforms section [of your screenshot], on the line that has your Sony Playstation platform, check the box Default Emulator. Click Ok to save and close. It should ask you if you want to make this you default emulator for Sony Playstation. Yes. Edit: guess I type slower than Tsik does.
  12. Share some screenshots of exactly how you're launching/starting the script. Is it set as a game's application path? A games Additional app? Do you have AutoHotkey installed on your system? Or are you pointing to the exe under the ThridParty folder?
  13. You're getting a bit too off topic from your original post. This makes it harder for other community members to be able search if they have the same/similar questions. Please keep your posts on topic (or at least close to it). Otherwise, if after you've done your due diligence in researching and are still unable to find an answer, feel free to start a new topic/post.
  14. Select None of the above when you import files that don't need an emulator.
  15. As someone stated... "Lumping everything in as "arcade" is a mess and simply not workable IMO." I agree. I'd say the developers thought of that, and in turn thought about people like us (and I'd imagine themselves) who individually manage our "Arcade platforms". vs. lumping everything into one large unruly, unmanageable Arcade platform. You know, "keeping it real" and leaving technicalities aside.
  16. Yes. The dll is just a Badge plugin. Nothing more. Then, add Microphone as a supported controller to your games. That folder didn't already exist?? What version of LaunchBox are you on?
  17. I can't answer that. It's not that I won't. It's that I can't. Ok. Arcade has a lot of clones. And those get added as Additional Apps. Which is what you see when you select Play Version If you really want to check your counts, from the Tools menu, Audit the platform. Look in the Additional Apps column and count up all the numbers of apps it shows. Add those to the number of games the platform shows.
  18. Go to and check View < Badges < Game Attributes < Enable Multiple Versions Do any of your games show the Multiple Versions badge? Right click one of those games that do and select Play Version. There you'll see some of the "missing games".
  19. The LaunchBox Custom Badge plugin support is [still] partially broken (since at least LB version 13.21). A bug report for it was submitted July 2025. The good news is that it does work. You just need to manually add the badge image to the proper folder and name it correctly. place your dll file in the /Plugins/ folder. place you image file in \Images\Media Packs\Badges\Nostalgic Platform Badges\ The image file needs to be named the same as the UniqueID you gave it in the plugin. mic.png One thing I noticed with the plugin you created is that for the individual games, the Support value has to be blank (or select "(Empty)"). Otherwise it will not show. Not sure if that was intended but thought I'd mention it.
  20. It tells you what the problem is. "Specifically" on the line the ---> is pointing to (Line # "011"). It can't find the file "Lightgun.exe" inside the folder "D:\Gun Build\Tools\Sinden Lightgun V2.01 beta\" Change the file path on line 11 in you script to where it actually is.
  21. Can you share the .dll file you created? What folder exactly did you put the image in?
  22. That's very odd, because the importer doesn't really "look" at your ROMs other than 'counting' them to see that you have at close to a full set and their location to set the ROM path. It then uses the xml to get/set all the game names/titles and then import them based on that and the filters you set. Regardless, well done. Sounds like it's now working.
  23. I should have also asked what version of LaunchBox are you on? Since you keep getting the error, I assume you kept retrying the Full Set Import Wizard and kept trying to have LaunchBox install/setup MAME for you. At this point, it may be easiest to have you install it yourself. Look in your /LaunchBox/Emulators/ folder and remove any MAME subfolders. Check in Tools - Manage - Emulators and see if you have multiple installs there. If so, remove them all. Now add a New Emulator, start typing in "MAME" for the name. To the right should appear a globe icon. Click it to go to MAMEDev's site. Download and install the revision that matches the revision of your MAME ROM set. The 2 MUST match! Alternately install it yourself somewhere. Either way, next point the Application Path to your "new" mame.exe file. Click OK to save and close. Start the Full Set Wizard again. When you get to the 'set the emulator', select the Manually Set up... (worded something like that) option. You'll get a "Warning", click passed it and select the emulator you just installed. Hopefully this time you won't get the error. The Error: During the Full Set import, LaunchBox will use your mame.exe along with the parameter "-listxml" top create an xml file of all the games that specific revision of mame.exe emulates. LB then parses the xml to get all the games' info. The error is [I believe] indicating there was an error in the xml file. Possibly got corrupted somewhere along the way. If you still get the error, report back with your LaunchBox version and the revision (version) of MAME you installed. Also add a screenshot of the error (if it's not the exact same as in your OP).
  24. It's a couple years old but should still be valid.
  25. Where/how (what are you doing different) are you seeing those 2 different [expanded] lists? I assume when you're in Platform Category view, and you expand the Arcade Category icon , you see the 'shorter' (last image) list of Playlists. And the (middle image) 'longer' list you're seeing is on someone else's, or a different LaunchBox build you have? To get the "missing Playlists, you can right-click the [other] Arcade Platform icon and select Create Missing Arcade/MAME Playlists and follow the prompts.
×
×
  • Create New...