Jason Carr

Hi Keith, looking at that folder, you're missing the LaunchBox and Big Box startup files. So you'll need to run the installer and make sure you install exactly to that "LaunchBox (Not In Kodi)" folder. You may have to type it in, because the installer always appends "LaunchBox" to the end of any folder you browse to.

Yes, the License.xml file should not be shared with anyone. That is fairly typical for computers and applications. There are many files on your hard drive that shouldn't be shared with other people for privacy reasons. Is there a reason why it's a concern for you?

Thank you @Thanatos_Prime. All good suggestions, and noted.

@Rifter22 Unfortunately it sounds like something happened to corrupt lots of the LaunchBox data files on your machine. It's probably worth running chkdsk to make sure that you don't have any file system or hard drive issues. Otherwise, I don't know why else that would happen really. If your file system or hard drive is getting corrupted, then it's possible that the backups are corrupted as well. First things first, go ahead and run chkdsk to see if it finds any errors. https://www.tekrevue.com/tip/fix-hard-drives-chkdsk-windows-10/

I have seen that before on slower systems, but yes, it should always repaint and work properly after a few seconds at most. I haven't seen it in quite a while though, so I'm not sure if a video driver update fixed it a while back or if it's maybe just a performance issue. Regardless, it's a Windows/.NET rendering issue, so unfortunately there's probably not a lot I'm going to be able to do to fix it.

Not quite sure what could be causing that slowdown, but the first thing to try is to see if it's media-related. You can make a copy of your LaunchBox install without games and media, and see if it's quick that way.

Unfortunately no; that's a completely separate thing.

Hey all, the 9.2 release is now feature-complete, so it's time to jump in on the translations. I also made sure I got the change notes in there this time as well. If possible I'd like to get this release out either on Thursday or Friday, as I'd like to get it out before Christmas without pushing too far up onto Christmas day. As always, thank you all very, very much. @Opak @dukeemu @cyanjiang @Bardock @MajKSA @gamehacker @Cauptain @Kondorito

Beta 6 is out now with the following: New Feature: A new "Export/Copy ROM Files from Selected Games to New Folder" option is now available under the Tools menu in LaunchBox. This is helpful, for example, if you wanted to export a particular genre playlist of ROM files to an EverDrive or similar. Improvement: When LaunchBox is repopulating games or populating different games, the games lists will now fade out and disallow selecting a different game. This should both serve as a visual cue that LaunchBox is processing and also help to prevent selection confusion/misselections. @RULLUR @Mr.Laor @Omen Game-specific startup screen settings are now available under the Startup tab of the Edit Game window Default startup screen settings are now available for a handful of emulators. Existing settings will not be overwritten; default settings will only be applied when adding a new emulator or upgrading to a 9.2 beta or the official release for the first time. Sans for any potential bugs/issues, or issues with particular emulators (I have a few on my list that I need to play with), this completes my vision for the initial round of startup and shutdown screens. Depending on how testing and translations go, I'm hoping to put out the official release before the end of the week.

Yes, that is correct. Only games are allowed in the games database currently.

This is explained in detail in this thread:

@Omen Thank you for that explanation, and thanks for the videos guys. That does make sense. I think the problem is just that LaunchBox is multithreaded and it allows you to do stuff in the interface while it's still working in the background. I'll see if there's something I can do about that. It's a non-issue if your collection/hardware are handling things quickly, but I can see how it would be a problem otherwise.

Custom backgrounds have not yet been built for all of the genres and play modes available for the consoles, so currently it just uses the console background.

@Nyukki That looks to be some sort of odd Windows or video driver glitch. I'm sorry you're having that problem. I would first try making sure your video drivers are up to date and you have all the latest Windows updates.

Yeah, I'm aware of this issue. It's on my list so hopefully I can get it fixed before the official. I still haven't been able to replicate this and I don't believe I've heard about it anywhere else either, so I'm kind of lost with it. Can you maybe record a video of it happening? No, the intention is not to completely replace the design of Rocket Launcher. We do have plugin support of course, but for the startup screens, the goal is to make it simple and "just work", not to make it scriptable and endlessly complicated. I very much doubt we'll ever take that route.

Are you talking about using VLC 3.x in Big Box? There's currently no way to use VLC 3.x in Big Box. It always uses the built-in version that's located inside the LaunchBox folder.

Steam is particularly nasty to deal with because of the way that it launches games. I will play around with it a bit yet, but all in all it may honestly be impossible to do well for every game.

This is a good thing to note. I don't currently have a solution for this. I think, generally, it's mostly a non-issue for MAME games, but it becomes more of an issue when dealing with other arcade emulators. For now I guess I would recommend putting non-MAME arcade games for Sega Model 2, etc. in as separate platforms; that way you can best use the metadata from the database. I'll add this to my list to improve though.

I'm sorry you're not happy with them. Either way, Unified wouldn't work well for 4:3. Both the Default theme and the included version of CriticalZone v2 should work great in most of the views.

Sorry for the lack of responses here. Can you clarify what your questions are? I think maybe people are just having trouble figuring out what you mean.

I'm not following. What do you mean?

If you're using Rocket Launcher, I can imagine we're probably going to run into a lot of conflicts. You may just have to turn off the LaunchBox startup screens completely in that case. I figure if you already have Rocket Launcher configured, why use the LaunchBox startup screens?

Game-specific options are planned, so that should take care of it. I plan to get those implemented next week.

Great to hear. Have you tried checking the "hide all non-exclusive fullscreen mode windows" box for that emulator?

Bezels are being considered for a later date, but they're immensely more difficult to accomplish (and also immensely more error prone). The proper way to do bezels is for the emulator to implement them instead of the frontend. For the frontend to do it is a serious hack and will require separate implementations for each and every emulator. Between MAME and Retroarch, most systems should already be covered I think, so I'm calling bezels the least important of the three Rocket Launcher features: startup screens, pause screens, and bezels. Pause screens will be implemented next, and then bezels will be considered at a later date.