JoeViking245

Ahh... The ol' exit from the Pause Menu routine. You've got several options, but the easiest one to convey is (not tested, but "looks good in print"....) In the Exit Script section of the emulator, add: WinClose, MyScript.ahk - AutoHotkey Change MyScript.ahk to the actual name of your script.ahk

I know there's a few emulators that LB will see what "it" (the emulator) has installed, and import then per that. But I don't believe that was implemented for Switch emulators. (I could be wrong) I'm not for certain on how or where it looks for "new games" for this particular platform. You should be able to turn off the auto import feature for the platform.

If the script is placed in the Running Script section for the emulator, the escape routine is not necessary [in this case]. When the emulator exits, the 'running script' is abandoned/forced closed, or as you say, killed. . In your case, I'm guessing it's an additional app to those games, set to Run Before.... You can use: $Esc:: { WinClose, ahk_exe mame.exe ExitApp }

Some emulators need a more "literal" or "defined" key press. Can try adding to the top if the script SetKeyDelay, 0, 50

Try LCtrl instead of LControl

"Microsoft.DotNet.DesignTools.Server" related error. Never seen this one before. Are your plugins (or one or more you have installed) using WinForms instead of WPF? It looks like that is what this is relating to. Maybe the version being used is not compatible with .NET 9? No idea, really. "Unable to read data from the transport connection". I consider that to be "just a thing". Only because I don't know what exactly is, and doesn't appear to actually cause issues. Functionally or performance wise. (and it always shows) I recently [finally] replaced my 16-year-old antique PC (i7 something, 8GB RAM, video card not-worth-mentioning and a 13yo HDD) to an i5 14400F, RTX5060 8GB, 16GB RAM and an NVMe SSD. Both Visual Studio and LB are on SSD's. Debugging startup time went from close-to-a-minute+ to 15ish seconds.

It depends on which files you're referring to. If it's game ROMs and they're not in game-individual subfolders, you can use Tools < File Management < Change ROMs Folder Path for Selected Games...

In the link given, click "Continue Reading" to see "Temporary Workarounds".

Since it (0.12.25) was just released about 14 hours ago, you may want to inquire on their Git Issues page. Specifically, about running it from the command prompt. Once it can be ran successfully from it, there should be no issues getting it to run via LaunchBox.

Read here: https://feedback.launchbox.gg/help/articles/8736968-launchbox-licensing-faq#l3q0zx8fdyd

When you get to the Options screen, try checking "Force using MAME metadata...". Assuming your using MAME type ROMs.

The error indicates there's an issue with your LaunchBox license file. All license issues need to be directed to: support@unbrokensoftware.com.

Give this article a once over and see if something in there sheds some light on the issue. Managing Storefront Games in LaunchBox - LaunchBox

Are you sure it's the same exact issue? The OP's error appears to be related to something with the theme's window sizing or an error with the actual image(s) downloaded. And also from 16 releases ago. (Unless you're also on release 13.8 and the message reads the same) There is an unrelated known issue with Steam downloads that has been resolved with the current beat release. If you could share the error message you're getting, that would be most helpful. If there by chance is a file that got corrupted, restoring a backup using the built-in feature would resolve it. The (potentially) corrupted file would be one that's in the Data folder (which is what/where the backup/restore feature works off of).

Batch files can't "press keys". For an AutoHotkey script, it would be Send, !{Enter}. If using this in the emulator's Running Script, you'll need to add a pause before sending the key presses. e.g. Sleep 5000 to pause for 5 seconds [before pressing Alt+Enter]. Alternately (and possibly more reliable), you could use the method noted above. I personally can't attest to either of these methods because I don't use this emulator (game engine).

For troubleshooting purposes, double/triple check your LaunchBox settings for the platform and maybe share some screenshots. In LB, edit the emulator and share a screenshot of the main Details section and also the Associated Platforms section (where your N64 platform is visible). Verify that Default Emulator is checked. Verify that Extract ROMs is un-checked. You already verified the correct core is selected. Edit one of the N64 games and show the Launching section (verify it's pointing to an n64, bin, or whatever format you ROMs are in). Also show the Emulation section (verifying that RA is the set emulator and that there are no overrides set). If your ROMs are zipped (for some reason), confirm there's just 1 file inside it. (In this case, Extract ROMs [mentioned above] would be checked). If there's more than one file inside the zip, the wrong one may be being send to RA. If your ROMs are zipped, (for testing purposes) try extracting one of them, point that game to the extracted file (making sure extract ROMs in unchecked in the emulator) and try launching it from LB that way.

I don't know about creating a "fake ROMs list" for the Community Theme Creator 3rd party app as I don't use it. But there is this that may (or may not) do something similar, towards what you're after. It doesn't create ROM "files", but will add game "placeholders" to your collection for missing games (games available in the LaunchBox Games Database that aren't in your collection.

This is a known issue which can be resolved by updating to the latest beta release. See more details here:

Umm... it shouldn't. e.g. Consoles (Category) Nintendo (Category) Nintendo Entertainment System (Platform) Super Nintendo Entertainment System (Platform) Nintendo Wii (Platform) Sony (Category) Playstation (Platform) Playstation 2 (Platform) If you delete the Nintendo Entertainment System (Platform), the other 2 should stay there. (leaving the NES platform nowhere to be found. And any playlists looking for games in NES, at a loss) But if you delete Nintendo (Category), then yes. All 3 of its platforms will be discombobulated. If deleting the Nintendo Entertainment System (Platform) affects the other platforms within the Nintendo (Category), then it sounds like a Bug Report needs to be filed. I'm volunteering remotely for the next week, so am unable to test it myself. Just be sure that we're talking apples to apples. Platform vs. Platform Category (aka Category) vs. Playlist. Also, physically deleting the Platform vs. just removing it from under a [Platform] Category.

Oops. Guess I've only ever "looked" on there from this laptop and never actually logged on from here. I see it now. Thanks.

Just checked the Feedback page and it seems fine here. However the Games Database page shows something similar to what you're showing. Admin has been apprised of this issue and are working towards getting it resolved.

Ah, ya. If you delete a Category, other platforms that were in that category can't be in that [now] non-existent category. To remove a platform from being in/under a certain category (which I think is what you're actually after), right-click that platform and select Edit. Go to the Parents tab and there you can check/un-check Categories they will be nested under.

Right-click it in the left panel and select Delete.

There're several factors that can affect load time. Hopefully this article can shed some light on how to improve it. Troubleshooting LaunchBox & Big Box Performance - LaunchBox