LaunchBox 13.28 Beta Thread

[christhed]

Like a lot of people have already pointed out, Launchbox is acting pretty weird for me with this beta.

The most frustrating issue I have is that my box images take forever to load in, and disappear as soon as I scroll by. I started the screen recording about 5 minutes after starting up launchbox and as you can see, images are not all showing.

• Windows 11
• AMD Ryzen 7700x
• AMD 7800XT
• 32gb ram
• Launchbox and all media is on a SSD

 

 

Edited Wednesday at 06:44 PM by christhed

[crusadeRGP]

When I open a game manual from the pause screen it stays hidden and does not show in the foreground.

 

Using PauseShift game pause screen

[Retrofrogg]

On 6/15/2026 at 10:10 AM, Retrofrogg said:

I find that the current beta often gets stuck on "loading interface" and won't open Launchbox. This happens intermittenly, maybe one out of 4 times. 

This seems to happen more when you do something else on your PC whilst Launchbox is loading. If you don't do anything else, the problem is less likely to happen. And sometimes it just seems to take a lot longer than usual before starting. 

[JoeViking245]

7 hours ago, crusadeRGP said:

When I open a game manual from the pause screen it stays hidden and does not show in the foreground.

I'm seeing the same thing with the Default Pause Theme.

 

My findings:
The LaunchBox Reader is opening, but the pause screen forces focus back onto itself (with the Reader sitting at the bottom Z).  You can Alt+Tab to the Reader to have it be the 'active' window, but the Pause Menu is still forced on top (top Z order).

With the Reader as the active window, you can Win+Shift+Left (or Right) and move the Reader to a second monitor and use it as normal.

With the Reader being left open (whether sitting on the bottom Z, or just not 'Escaped' to close it), when exiting the game, it stays open when exiting the game.  Maybe that's a "feature".  

[JoeViking245]

On 6/15/2026 at 2:10 AM, Retrofrogg said:

I find that the current beta often gets stuck on "loading interface" and won't open Launchbox. This happens intermittenly, maybe one out of 4 times. 

Though possibly not the same thing, another user had a similar issue.

• Start LaunchBox. No issues
• Exit/restart LaunchBox
  • it gets stuck on Loading Interface
• Restart the PC
• Start LaunchBox. No issues
• Exit/restart LaunchBox
  • it gets stuck on Loading Interface
• wash/rinse/repeat

Turns out (in this situation) their C-drive was near maxed out. Full. In-the-red. Note, their LaunchBox install was on their E-drive.

Freeing up space on the C-drive completely resolved the issue.

[Retrofrogg]

20 hours ago, JoeViking245 said:

Turns out (in this situation) their C-drive was near maxed out. Full. In-the-red. Note, their LaunchBox install was on their E-drive.

Freeing up space on the C-drive completely resolved the issue.

All my drives are blue, i.e. not nearing full - so I don't think that's the issue here.

[AstroBob]

Hi Folks,

Thanks for all the continued reports here. We wanted to provide an update on where we’re at with this beta.

First, we want to acknowledge the rocky start to beta-2. We really appreciate all the reports, but apologies that many more folks than usual seem to be having issues, particularly around performance. This beta updated some of our core services under the hood, but a lot of issues appear to be largely stem from our new grid implementation.

For some context, we completely rebuilt the grid view for this beta with a focus on much snappier responses when quickly scrolling through incredibly large libraries. To get to this point, we had to make the decision to use a fixed grid size (which you can adjust on a per-section basis). While our performance tests have been largely positive compared to the old grid, we are seeing reports of unintended side effects, particularly around images loading into the grid and issues with surrounding elements like badges, which gives the perception of decreased performance. We know that’s not the only related issue, but we initially had trouble reproducing it internally on one of our many builds, as it appeared to be largely library-dependent.

That said, after much trial and error, we’ve now managed to recreate a build exhibiting similar issues and already have several fixes in place to help mitigate them. We also want to acknowledge other issues such as the large number of reports around controller issues in Big Box, which have also been fixed internally.

We know this only scratches the surface of what people have been reporting, and we’ve been following your feedback closely. Beta-3 includes a number of changes aimed at addressing the biggest issues we’ve seen so far. We may not have fixed everything just yet, but we’re hopeful it will eliminate the major pain points so we can focus on what’s left.

Thank you all for helping us test this. We know this beta has been a bit rockier than usual given the scope of the changes, but your reports have been invaluable in helping us identify and address the biggest performance issues, along with a variety of other fixes.

We’re hoping to have beta-3 available as soon as possible so you can probably halt with the beta-2 reports for now, but we’d love to hear whether those who experienced issues with beta-2 notice improvements. We’ll keep you all posted once it’s ready.

[kobaturtle]

Thanks for the feedback! That's what betas are here for, right? I'll speak for myself, take all the time you need to cook a good beta3!  And again, this new game grid looks promising.

 

[dukdukgoos]

Great, looking forward to Beta 3. On a positive note, in my build I've not seen any performance problems with Beta 2. Scrolling speed of image grid is very snappy.

[izzishor]

Any way to get a notification when Beta 3 drops? Because there's no way of knowing if you're updating to Beta 2 or Beta 3, atm.

Thank you for the development, looking forward to the release.

[JoeViking245]

1 hour ago, izzishor said:

Any way to get a notification when Beta 3 drops? Because there's no way of knowing if you're updating to Beta 2 or Beta 3, atm.

If you have betas enabled (Tools < Options < General < Updates - Update to beta releases), you'll get a notification that an update is available. It won't tell you the beta #, but if you're on beta-1, it will be beta-2. If on beta-2, it will be beta-3. etc. 

With the feature enabled, you can't choose to skip a beta.  Unless you installed beta-1, then disabled beta updates, then you will not get notified [from within LB].  If you've opted out of betas, you can click Follow (near the top of this page) and select how frequently you'd like to get notification about this thread.  But you'll get notifications for every post to this thread. Then at some point, one of those will be from Admin stating beta-3 is out.

Another option could be to bookmark this thread and periodically check the 1st post as that will get updated with new beta release information.

[izzishor]

17 minutes ago, JoeViking245 said:

If you have betas enabled (Tools < Options < General < Updates - Update to beta releases), you'll get a notification that an update is available. It won't tell you the beta #, but if you're on beta-1, it will be beta-2. If on beta-2, it will be beta-3. etc. 

With the feature enabled, you can't choose to skip a beta.  Unless you installed beta-1, then disabled beta updates, then you will not get notified [from within LB].  If you've opted out of betas, you can click Follow (near the top of this page) and select how frequently you'd like to get notification about this thread.  But you'll get notifications for every post to this thread. Then at some point, one of those will be from Admin stating beta-3 is out.

Another option could be to bookmark this thread and periodically check the 1st post as that will get updated with new beta release information.

Thank you for the answer, but you just explained exactly the UX issue I asked to be fixed.

The notification says 'New Beta Version', not 'Version xxx Available' to download. You never KNOW what version you're downloading untill the install screen, which is set to AUTOINSTALL, as well, so no way of cancelling it.

Meaning, if I download the beta version and it's still Beta 2 in this case, it will be broken again, and I will have to remove plugin, reinstall beta 1 manually from the update folder. Which I've done 4-5 times so far.

What I was asking for was a VERSION NUMBER before you download, to actually understand what it is you're downloading so you can ignore it if it's a bad version.

The fix should be very easy to implement, since you only need to show the download filename before you download it, which has the version number before the file extension.

That's all, ty for taking the time to answer, and big up on all the updates and optimizations 👑

Edited 2 hours ago by izzishor
Grammar

[JoeViking245]

9 minutes ago, izzishor said:

What I was asking for was a VERSION NUMBER before you download, to actually understand what it is you're downloading so you can ignore it if it's a bad version.

Apologies. I may have missed a prior post or didn't read deeper into the last post.  Just merely replied to 'how to get notified of the beta-3 release'. 😊

So you are on beta-1 and (I presume) have Automatically Download Updates in the Background un-checked (disabled).   And just want the Update Available notification to be more specific.

Though I want to say it's not really a beta issue but more of a Feature Request, for this particular release series I can see how it would be super helpful.  

However, I believe this would be something that could only be available from a future release, as the notification toast verbiage comes from the currently installed version/release.  So I don't think [in this case] you'll be able to see 'a beta-3 update is available'.  (which sort of brings back to the latter part of my previous post.)

Again, sorry for my confusion.