Jason Carr

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).

It may be still saving other platforms at that point, so it might require just waiting. A debug log might help to figure out what's going on though. It looks like the error is related to "The given path's format is not supported." That means that somehow there's an invalid path in there somewhere (at least that's my best guess). It could also be that somewhere there's a path that is longer than 255 characters, which could be causing the problem. Unfortunately diving in deeper to find the exact path that is problem likely isn't going to be easy. The error appears to be happening with images though. Are you using any super-long paths for images? Are they on a network path or a local path?

Thanks Retro, unfortunately though we'll need to tackle each issue individually, because so often with these things we find that they are separate, unrelated issues. So unfortunately we can't assume that you and @MrSco are running into the same issue. Can you provide me with a debug log when it crashes (or several)? That should help to figure it out.

Watching the video, it looks like maybe it's a performance issue. I have seen Big Box crash eventually after a few hours when the system can't quite keep up with the attract mode. What are the system specs? Have you looked to see how much RAM is in use?

If you check the box to remove rough-duplicate images, it will be slower than 10.15.

Yikes, thanks Cid. Surprised that didn't come up in the betas. We're planning on fixing this and some other more minor things on Monday. Probably look to put 11.1 soon after.

I might try using the latest MAME core instead. I'm honestly not familiar with that core, so I can't help much there.

@catfer Not really sure why you're arguing here. To be honest, the only reason it's not a rule in the database is because it never came up before (it was pretty much assumed). Screenshot images with filters is not something that we have a lot of anywhere else in our database. We created this rule because it was the first time we've noticed that it was a problem. We've explained why it's a problem, and any further arguing (or continuing to upload images with filters) will be grounds for a ban.