Jason Carr

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.

Because moderators aren't perfect, nor are humans... I believe this is at least the second time you've gone off on this tangent, and that's just what I've seen. We really could use less pot stirring around here, in all honesty.

As small as that is, that is exactly what is ideal for screenshots of those systems.

Ideally screenshots of retro systems should be represented in the original resolution (easiest way), or if you want to blow them up, you should preserve the pixelated nature of the screenshots. But even some blurring (like most emulators default too) would be fine, and would be an improvement over the filters used above. My recommendation though would be to upload screenshots in the original resolution. Yes, the aspect ratio is not quite right, but the entirety of the original screenshot from the game is still captured that way.

It does look like those screenshots have heavy filters on them, so I can understand why the community is rejecting them. The voting system is made so that only a consensus of three or more accepts or rejects (or three more accepts than rejects or vice versa) will result in the final acceptance or rejection, and it is generally designed so that the moderation community can decide. In my personal opinion, this is a rough decision because screenshots should definitely not have such heavy filters applied. That said, any screenshot is better than no screenshot, but in my opinion the filters are really ruining things. I'm not sure if this screenshot below is you as well @catfer, but it's an example of how badly screenshots can be ruined by filters. I guess what I'm trying to say is that I don't completely fault those moderators for rejecting those screenshots. Like I said, any screenshot is better than nothing, but the filters really get in the way of representing the game properly.

MalwareBytes is probably the problem. That software has been a nightmare for us in the past, and in my personal opinion it's garbage because of all of the false positives.

We'll need to know what core you're trying to use in Retroarch. If you're not using MAME, that's what you probably need.

Usually if it crashes on initializing, it's having some kind of issue extracting and writing the necessary files. It could be disk corruption, could be a permissions issue, or an app conflict. So first off, try closing any background apps, including anti-virus. Then try chkdsk to see if you have any disk issues. Then try deleting the ThirdParty folder and then re-installing over top.

Noted the request about moving instead of copying. OBS does have volume controls, but as it's recording your system audio, it could be affected by your system volume. I'm not sure why that would be. We haven't seen any difference between 10.15 and 11.0 in our testing.

Thanks guys, we'll look into the videos and manuals issue with the audit screen here shortly.

There should be no difference in performance anywhere really. Perhaps @mcfilmmakers is referring to the delays that were in the old betas? We'll look into this. It sounds like you've set it up incorrectly, I think. The OBS videos folder setting should be pointed at the folder that OBS puts recordings into, not the destination that videos should end up in. Once associated, videos will end up in the platform's videos folder for the game that was run.

Not exactly sure what's happening, but there is an option in the wizard to look in subfolders, or not. So do make sure that that option is set to look in subfolders. Beyond that, anything can be imported easily using Windows search. For example, you could just go into your NTSC-J folder in Windows explorer, and use the search box in the upper right. Type in *.iso, and that will show all the games in all the subfolders. Then just select them all, and drag them onto the LaunchBox interface to import them.

I see, of course, sorry. Easiest way then would be to just delete the Settings.xml file (or move it out of your data folder). Then you can restore from a backup if you want.

If it's just the settings file, you could always just delete the LaunchBox\Data\Settings.xml file and all you'll lose is any custom settings. Otherwise, you can use the Tools > Restore Data Backup option to restore your data to a previous working state (but that will restore all of your data).

The release is live now, if anyone hasn't noticed. Let me know if anyone runs into any serious bugs with the 11.0 release.

Hi @JoJoJuJu59, it is possible with a custom theme, but that would be the only way to do it currently. Could just copy the default theme and tweak it to make it whatever you want it to be.

Should be fixed in beta 7, which just went out.

Beta 7 is out now with the following: The game details sidebar in LaunchBox now populates correctly after closing the Add/Edit dialog When cancelling the Add/Edit dialog, some validation errors were still being shown In the add/edit dialog, pressing Enter while focused on the Title text box was not working properly Hopeful fix for legacy video paths not being used in all situations When manually adding a game, the Title text box is now populated automatically when browsing for the ROM or startup EXE file (like the old dialog) New games are now selected after adding them (if they show up in the current platform/filter) Link (.lnk) files are no longer de-referenced when browsing them in add/edit (and a few other places as well)

Correct. Especially if a game does not have screenshots already, we should not be rejecting images over picky resolution issues.