JoeViking245

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

There "should be" no difference in how LB vs. BB uploads scores. Showing the ones (for the same ROMs/games) where LB uploaded the scores may be helpful. May not be relevant, but one thing to note is that, even though your 'current score' made the MAME hiscore, only your highest score will prevail. e.g. Playing in LB, you got 1st (as shown above), then playing via BB you made the board in 3rd, it's not "your" highest score. So doesn't 'report'. Another thing to note is only changes to the hi file (or nvram) are referenced. LB/BB reads the respective file before you start playing "that game" and then again after exiting the game and notes any changes. If there's no changes, there's no upload. Even if e.g. 184,300 is higher that's what's shown on the LB Leaderboard, if you didn't "just get it", it won't upload. I only mention this because in your log, all references to dragnblz showed the exact same scores. For s1945, I can see score changes, but around the 4th and 5th place ranking. If (e.g.) the 4th place "new score" was higher than what's shown on the leaderboard, then that may be an issue.

And if you revert the $ change, does that error not come up? (granted, when exiting the game, BorderlessGaming (BG) still wouldn't close) And if doesn't come up after reverting, (manually close BG and...) change it back to a $ to confirm (or not), that indeed what's causing the error. (then back-and-forth again for a triple/quadruple confirmation). aka: absolute process-of-elimination. Some thoughts: Run the script from outside of LaunchBox to eliminate LB as the issue (which I'm doubting it is). Make sure not to have both Esc sequences in the script at the same time. The "return" at the end of the escape sequence shouldn't be necessary It may be keeping the script open/running after escaping/exiting the game Though may not be an issue when using SingleInstance Force There's no need to have it continue to run. However harmless. Maybe create (and test) a script that starts BG, pauses 5 seconds or so, and then [attempts] to close BG to confirm that it's even possible with the methods used. Run, "C:\Program Files (x86)\Borderless Gaming\BorderlessGaming.exe" Sleep, 5000 Process, Close, BorderlessGaming.exe MsgBox Borderless Gaming should be closed now (when copying/pasting that 1st line, noticed you have 2 double-quotes at the end of the line. Removed one of them in my example) If Process, Close doesn't work, then try it with the Run, TaskKill... line. Don't need both of them in there. Only the one-that-works.

When you have LaunchBox update itself (e.g. Tools - Options - check for updates), it adds and/or updates its files necessary to run, in the Core folder (as well as others). The Data folder holds settings files necessary to run, as well as data for systems and emulators you've added to your collection. If one or more of these setting files are missing, LB will create them on next launch. Help is available to work towards resolving whatever "isn't working great". However that does not extend to pre-built LaunchBox installations, as we've no idea, nor care to figure out, how all they did what they did when they installed it (additions, changes, third party add-ons etc.).

That's not an AutoHotkey error. So the $ change wouldn't have caused that. Doesn't look like a LaunchBox error. Which leaves us with a TP or BorderlessGaming error. ? maybe one or the other was still running in the background and you ran the script [again]? ? (speculating)

Can you share what the error was?

Process, Close, {{{StartupEXE}}} won't work in your script because (I'm pretty sure) {{{StartupEXE}}} is a LaunchBox parameter (vs. an actual AHK parameter). In your original script, you may try replacing ~Esc with $Esc

This article should help give some insight. After following through, report back if you're still having issues. "Could not install MAME because the archive could not be extracted" Error - LaunchBox