JoeViking245

To run MAME's software list consoles from the command prompt, you need to add the system name and the media flag (as well as the ROM name). Atari 2600 Example: mame.exe a2600 -cart1 adventur Since you chose to "Copy the files into my LaunchBox games folder" (which is fine), the ROMs aren't in MAME's default /roms/ subfolder. So MAME doesn't know specifically where to find the ROM. So now you need to tell MAME exactly where the ROM is. You also need to give the full filename.ext. mame.exe a2600 -cart1 "D:\LaunchBox\Games\Atari 2600\adventur.zip" The problem with this is, to do that in LaunchBox you need to uncheck the boxes "Remove quotes" and "Remove File Extension" in your [edit] MAME emulator. This can potentially mess up your Arcade platform (depending on how you installed its ROMs). To get around this, you can add the command-line parameter -rompath. mame.exe a2600 -cart1 adventur -rompath "D:\LaunchBox\Games\Atari 2600" Now to put all that in LaunchBox. Edit you MAME emulator. Go into Associated Platforms and for Atari 2600, add the Default Command-line Parameters -rompath %romlocation% a2600 -cart1. If all goes well, you'll be good to go. As for Apple II, that can be a bit more convoluted to get running. But it CAN be done. There're several topics here on the forums regarding setting up this console to use MAME. Also, for consoles that require BIOS and Device files (a2600 doesn't require any), those should be placed in the same folder as their ROMs so MAME can find them too. If you plan to import a bunch of MAME's softlists, you may want to look into adding the MAME Software List Import Plugin to your LaunchBox setup. It'll help get the games named properly in LaunchBox and attempt to add the required Default Command-line parameters. Assuming you're using MAME's Software List ROMs. ROMs from ither sources may not be accommodated.

Yes. That would be how you exit the game and return to BigBox. Then just select a different game and play it [for however long] and use the mapped button(s) (again) and return to BigBox.

Oh. The thread was about not having the GUI show when exiting PCSX2. To exit a game using your controller, you need to map the controller button(s) in LaunchBox Premium and [separately] in BigBox. You can map any button or button combination you like. Just make sure it's not a button(s) that's assigned to something else. LaunchBox: Tools - Options- Game Controllers - Mappings. Then map to Exit Game. BigBox: System Menu - Options - Controller Mappings. Then map to Close the active Window (Not Exit. That's to completely exit BigBox).

Try the Default Command-line Parameters: -nogui. This assumes you're using PCSX2-qt. I believe by default, the Confirm Shutdown is checked by default (in PCSX2 Settings). So make sure that's un-checked.

Though it's in the LB Database and inside /Metadata/Metadata.xml, it doesn't have an associated database ID # (at least not in the xml that LB automatically updates). <Game> <Name>The Thaumaturge</Name> <ReleaseDate>2024-03-03T00:00:00-08:00</ReleaseDate> <Overview>The Thaumaturge is an isometric, etc. etc. etc.</Overview> <MaxPlayers>1</MaxPlayers> <ReleaseType>Released</ReleaseType> <Cooperative>false</Cooperative> <VideoURL>https://www.youtube.com/watch?v=RfX-iKz2hKU</VideoURL> <WikipediaURL>https://en.wikipedia.org/wiki/The_Thaumaturge</WikipediaURL> <Platform>Windows</Platform> <ESRB>RP - Rating Pending</ESRB> <CommunityRatingCount>0</CommunityRatingCount> <Genres>Adventure; Role-Playing</Genres> <Developer>Fool's Theory</Developer> <Publisher>11 bit studios</Publisher> </Game> Then next game in the xml does have an ID# As to why it doesn't have an associated ID yet, that's above my paygrade. But at least we know it is there. Mostly.

You're very welcome! Rumor has it, you can alternately add the AHK commands to start RA in the emulator's (Model2 in this case) Running Script. Run, "D:\Emulators\RetroArch\retroarch.exe" -L "D:\Emulators\RetroArch\cores\wgc_libretro.dll" -f "D:\Emulators\WindowCast\SegaModel2.txt" Process,Wait,retroarch.exe WinActivate This will launch the game 'normally' (using the M2 emulator and the games .zip file), and at the same time, start RA.. loading the core and the txt file holding all the game names for that platform. Courtesy in part by @SpoonyOrbit via Discord.

Glad it was a simple fix. You may still want to try the official release (if you haven't already). But I suppose "if it ain't broke..."

Since you're posting in this thread, I presume you're testing with this depreciated beta release. You might try the official release that's linked on the 1st page. Or just click here. If you're still having issues... Do you have your Windows display settings scale set to something other than 100%? Try setting it 100% (right click on your desktop and select Display Settings. Also, from your screen shot, you will want to size the orange frame around both the top and bottom 3DS screens. If you're still having issues with the official release, please post them in its' thread via the link above.

This isn't an end-all, cure-all solution. More of a process of elimination. Disable game Startup Screens. In LaunchBox, edit the emulator and uncheck the box Enable Game Startup Screen. There're also options in BigBox. System Menu - Options - Game Startup

That definitely helps. Thanks. So, (correct me if I'm wrong) the process as I see it is: Launch the game via its emulator ("Behind Enemy lines" - "emulator_multiplecpu.exe" (The M2 emulator)) Then, launch RA Because of the name of the text file you passed to RA, along with the contents of the text file, RA know to look for 'that games' window'. For all that to work, you create a text file for each game (ROMname.txt). And in the text file is the name of that game. Or?, it's one text file with all the game names for that platform, and that text file is copied and renamed to each of the ROM's ROMname.txt. (Doesn't really matter. "A bunch of .txt files need to be created".) And this is so you can add a bezel [and shader] to emulators that don't support them? Or does it do more than that? I ask because, if it's just for bezels and shaders, I hear there's a plugin called BezelLauncher that can do that. Without having to have two emulators running at the same time and without the need to create text files. All that aside, and not to get out of more work for me , I believe you can do what you want with the existing options. For example: Let me know if this method works. If it does, and you stick with the RA + actual emulator (i.e. emulator_multicpu.exe) route, you won't even have to add these 'extra' emulators to LB. (Just a thought. )

I'm not familiar with WindowCast (but I have heard 'of' it). Can you share some screenshots of how you set it up? Edit game, then the Details, Launching, Emulator, and Additional apps sections, and also if you need to add something in one of the other tabs of the [Edit] additional app. I don't need any of the configurations from inside RA itself. Just what's needed to launch all that (RA, the game and emulator) stuff from LB. Please. Just want to get a visual of what's all involved if I do add the 'Emulator' option, is case something else is necessary too. Thanks.

I can't attest to eXoDOS menu items being added, but the right-click menu items shown in your link is from an older version of LaunchBox. Those items are still there, they've just been stylishly moved into submenus. Namely Edit, Media, and File Management. Are there specific items you'd like to see when right-clicking a game that aren't available?

Of course it would be 'possible'. But can you give me some examples of additional apps that you'd want to add in-bulk to existing games, that require an emulator? Good to hear. Thanks for the feedback!

Bulk Remove Custom Fields View File Bulk clear Custom Fields Values or remove the Custom Field entirely from LaunchBox. Inspired in part by this BitBucket ticket (and the rest out of boredom) https://bitbucket.org/jasondavidcarr/launchbox/issues/8475/mass-delete-remove-custom-fields Notes about Custom Fields: Custom Fileds are comprised of a Name and a Value. When you edit a game and look in the Custom Fields section, every Custom Field [Name] in your entire LaunchBox collection will be available. Whether a Value is assigned to it for that game, or not. Only Custom Fields that have a Value assigned to it somewhere in your LaunchBox collection will actually exist. aka, if you're seeing a Custom Field Name, something somewhere in your collection has a Value assigned to it. Installing: Download and unblock the zip file. Copy the contents of the zip into /LaunchBox/Plugins/ i.e. D:\LauncBox\Plugins\BulkRemoveCustomFields\BulkRemoveCustomFields.dll How to use: Start LaunchBox, click Tools and select Bulk Remove Custom Fields Select a Platform to get a list of all Custom Fields [that have an associated Value] for that platform. Or check Select All to get a list of all Custom Fields from all Platforms. Example #1: To remove all Custom Fields whose Name is "Has Bezel" and their Value is "yes" (lowercase "y") Check Show All [to show ALL distinct Custom Field Names and Values] Check the box next to "Has Bezel" "yes" Click Delete Selected Example #2: To remove all Custom Fields whose Name is "Has Bezel", regardless of their Value Un-Check Show All [to show ONLY the Custom Field Name] Check the box next to "Has Bezel" Click Delete Selected To remove a Custom Field entirely from LaunchBox, check Select All and follow Example #2. Options: Select All Show all Custom Fields for every Platform Show All Show Custom Fields Names and Values CAUTION: If you click Delete Selected and then click Yes, those selected are now GONE! Reprise: If you had LaunchBox's Automatic Backup feature enabled, you can use the Restore Data Backup to bring them back. Q: Why is it listing the same Custom Field more than once? A: It's not. Custom Fields are CasE sENsiTiVe. A Custom Field with the Name Saves High Scores is different from Saves high scores. Same goes for Custom Field Values. True is not the same as true. Submitter JoeViking245 Submitted 03/04/2024 Category Third-party Apps and Plugins  

./simple64-gui --help Usage: ./simple64-gui [options] ROM Options: -h, --help Displays help on commandline options. --help-all Displays help including Qt specific options. -v, --verbose Verbose mode. Prints out more information to log. --nogui Disable GUI elements. --test <number_of_frames> Run debug tests. Arguments: ROM ROM to open. Try adding the --nogui option to the command-line parameters.

Is your platform set to scrape as Nintendo Entertainment System? In the left pane, right-click on your NES Platform and select Edit. Make sure Scrape As is properly set.

This plugin should help you with the 2-minute loading issue you mentioned with BBH-Pro. However, it will not fix issues with games/emulators that use a loader to [then] launch a game, such as Steam as mentioned by the OP.

Startup Screen Load Delay: greater than 30 seconds View File Breaking the 30 second Startup Load Delay barrier. Description: This plugin allows you to set the Startup Screen load delay time to greater than 30 seconds. You can set it for a single game, multiple games (in bulk) or per emulator. Installing: With LaunchBox not running, download and unblock the zip file. Copy the contents of the file to /LaunchBox/Plugins/ i.e. D:\LaunchBox\Plugins\StartupScreenTime\StartupScreenTime.dll Using: Single game - Right-click a game and select Custom Startup Screen Time Check Override and Use Startup Screen Set the Delay Amount to the desired duration. Click OK to save the changes. Multiple games - Select multiple games Right-click and select Custom Startup Screen Time Check Override and Use Startup Screen Set the Delay Amount to the desired duration. Click OK to save the changes. An emulator - Click Tools and select Emulator Custom StartupScreen Time Select an emulator Check Use Startup Screen Set the Delay Amount to the desired duration. Click OK to save the changes. Limitations: - Max load delay time is 5 minutes (300 seconds) - This WILL NOT fix issues with games/emulators that use a 'loader' to start a game. The Startup Screen will still go away after the launched executable exits. Here's showing a games' load delay time set to 3 minutes and 12 seconds. Submitter JoeViking245 Submitted 03/02/2024 Category Third-party Apps and Plugins  

Guessing you're not on LaunchBox 13.12-beta-3. 😊 This was actually my fault for not rolling back the dependencies. Version beta-6a will work with LB v13.3 and newer. lol. Good. Was about to question the integrity of your xml sources.

The issue came down to: it was only comparing the game's Title & ROM name and not taking into account the games Version. Fixed in beta-6. Also (not mentioned in the description), the plugin will now add the Version data when importing regular games (vs. just additional apps). Which bring us to: you may still have an issue with your imported game Boulder Dash [cbdash.zip]. The "Version" of that game per your xml file is "(Zombie Cassette) (US)". In the MAME official builds (since release 0.179), the version is "(DECO Cassette) (US)". So if when getting metadata from LaunchBox and it updates the version field, reimporting via that xml file (or source of the file) may make for unexpected results. (or maybe they will be 'expected' because of what I just mentioned. )