JoeViking245

Give this a read and see if it sheds any light. The location for the icons has changed in LaunchBox v13.21. And while not assuming anything, custom platform Icons does require a premium subscription. Creating Platform Clear Logo Media Packs for LaunchBox and Big Box - LaunchBox

Th instructions should be fairly straight forward. What exactly is not working? After selecting a game (or games), does the plugin appear when you right-click one of the selected games? When you click it, does the plugins UI appear? Do you have Pixelcade installed? Which folder was it installed into?

Check the Image Group menu for the selected image type to show. Note, it can be set on a per platform basis. (e.g. platform A uses "Boxes", platform B uses Steam "Banners") When you edit a game and look in its Images section, there are no images (showing [when there should be]? If that is correct, check the Metadata section of that game verify the Platform it's assigned to doublecheck that in your /Images/ folder, the platform name is spelled the same (In the image type subfolder below that platform) the games image filename is the exact same as the games' Title or ROM name noting that -01 is appended to the filename and that invalid filename characters are replace with an _ (underscore) If that all pans out, back in the Images section of that game, click Add Image and navigate to one of those image files for that game and select it. Click OK to save and close, press F5 to refresh the image for that game and see if it now appears. The progress bar you see is (pretty sure) refreshing the image cache for the selected platform. LaunchBox doesn't keep a database-of-sorts of your images (nor videos). They are captured on-the-fly, on-the-go, as-needed... you get the idea. When selecting the platform, the cache is populated (or at least does a quick check, which if it's "good" is when you may not see the progress bar). When switching games in that platform, it's reading from just the cache. Thus the occasional need to refresh images. When you resize the images with the slider, ("I think") it does a repopulate of the cache. I do know it needs to repopulate it when you change the image type to show for that platform.

I think what you're after is... Tools < File Management < Export/Copy ROM Files from Selected Games to New Folder...

If the single ROM file inside the zip is named differently than the zip, it may cause the issue. (but I'm not for sure on that). In the end, those ROMs are small to begin with, so having them zipped has no substantial gains. Glad you got it working.

Nope! If it works, stick with it. Like the audible beep idea.

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.