Jason Carr

Oic, so you were manually browsing for the same video for two different games? To be honest, I didn't even know people did that. We'll take a look to see if we can support that. It may be more trouble than it's worth though, to be honest, considering that you can just duplicate the video on the rare occasions that you've got that particular situation.

Yes, we're aware of that. Please see my response here:

Beta 2 is out now with the following: Game titles are now trimmed properly Browsing for an additional app will now default to the game's directory Fixes for the new auto-complete functionality with the multi-select drop downs in the add/edit window (auto-complete now works for all items in the list instead of just the last item) The plan is to put an official 11.1 fix release out tomorrow. Let me know if anyone finds any more bugs with the 11.0, beta 1, or beta 2 releases. Thanks y'all.

The games view will repopulate after closing the Options screen. I'm guessing it just was going to take a bit longer to populate. That's an interesting idea, but honestly I don't think it would have mass appeal. Thanks, we've fixed this for beta 2. So the previous functionality here was more of a by accident thing than a by design one. We've changed videos to behave exactly like images do now. We need the ability to use different videos for games with the same titles, so that is the reason for the GUID text being appended to the end. Still, if you want to force LaunchBox to use the same video for multiple games, you should be able to just manually rename the file to the game's title, and I think both games should pick it up.

FYI, 11.1-beta-1 is out and should fix some of the above issues. That said, videos should not have disappeared with the 11.0 release. Let me know if anyone would like to dive in with details on that.

For anyone having issues with the screenshot capturing in LaunchBox 11, please update to 11.1-beta-1 and give it a test for us. We're hoping it resolves any issues.

Not seeing any issues that I can replicate. Launched NES, SNES, Genesis, and N64 all without issues. What exactly is happening for you?

I'll have @C-Beats review it. Unfortunately, though, it may just be an issue with Epic's API.

We're hoping this is all fixed with the beta release.

The first 11.1 beta is out with the following: Improvement: Auto-complete is now available in the multi-select drop downs of the new Add/Edit screen by pressing the up or down arrow keys Fixed: Addressed several issues with the Audit form introduced in version 11.0 Fixed: Multiple custom fields with the same name were not saving properly in the new add/edit screen Fixed: Media file parsing issues for game titles ending with a dash and a number Fixed: Incorrectly finding Retroarch screenshots that weren't taken while the last game was being played Fixed: Errors on the Image and Video Priority options pages when moving priorities up and down The plan is to put out a bugfix release in a couple days.

Hmm, hard to know exactly what's going on. I don't see any of those errors in my debug logs in my testing, but those errors don't necessarily indicate an issue (or THE issue). It could be there's an issue with the 2004 version of Windows though, not sure. I checked and it looks like I'm still on 1903 on my systems. Supposedly it's not pre-release anymore though. Has anyone else seen any stability issues pressing OK on the add/edit dialog?

It also may help to update the Theme Creator and re-export the theme. I believe y2guru did fix some possible memory leaks recently.

I'm sorry to say that the Android version was discontinued. See here:

Gotcha. What theme is it specifically? This log does very much suggest that there's some sort of a memory leak, which I suspect is related to the theme.

What emulator(s) is it happening with? Have you checked to see what keys or controller buttons are bound to the new screen capture features?

No worries @Kondorito; I'll get this into a beta. We plan to release 11.1 here in a few days anyways to address some issues.

Might also be worth running chkdsk to make sure that you don't have any drive or file system issues.

Sorry for the delay here @PiperCalls. Feels like the issues are stacking up here, which is odd. It's possible that your backup files are corrupted, but that would be the first time that I've ever heard of that. I wonder if maybe you're having file permissions issues with the LaunchBox folder?

You can enable debug logs under Tools > Options > Debug in LaunchBox, and then the debug logs will show up under LaunchBox\Logs. That should help us going forward to figure it out. The mechanical USB hard drive might actually end up being the culprit here, because I really don't do any testing that way currently (maybe I should). The four systems that I test on regularly all use internal SATA SSDs and/or mechanical drives. They're all stable and can run for days on end, so that may be the difference.

What are the screenshots of? Are they of the game you were playing?

I'm confused here; what is the exact issue you're running into with the cores in Retroarch (other than the phantom screenshots)? Per the phantom screenshots, have you looked to see what the images actually are? Are they proper screenshots of the game?

What is the error you're getting?

Okay, but I haven't heard about the specs of the other machines. I'm not saying we don't have an issue, but I can't fix it if I don't know what it is. I need debug logs, and as much information as possible for each machine. No need to get combative, because that's just not helpful.

Again, please stop assuming that the issues are the same, because I'm pretty sure they're not. From what I can tell, @MrSco's issue is that the hardware is having trouble keeping up with attract mode (which makes sense on an Intel Nuc). I don't have any better method of monitoring RAM usage, other than keeping Task Manager open (you can set Task Manager to Always on Top which can help). It may not be a RAM issue though (could be more of a CPU issue). It might help to pre-populate the image cache if you haven't already.

Honestly we haven't tested it with the Rockstar Launcher at all. If it's working with other games/apps and not that one, it is possible that there's an incompatibility. We use Windows' built-in screenshot capture functionality though, so unfortunately if there's an issue with a particular game, there's not likely anything we can do about it (though that should certainly be rare).