LaunchBox 13.28 Beta Thread

[jiboreid]

This new beta feels incredibly good in BigBox. A very noticable change in performance in various views and VLC is working great for me. Thanks for all the hard work!

[Jabb3rJaw]

Just updated to the latest version and videos are playing again. I will run my machine for a while and check on the random crashes in Bigbox also. Thanks for the fix!  
 

** is there a way to turn off the text on the loading and exit screen. This must be new. “Waiting for game to load”…..

Edited Saturday at 04:39 PM by Jabb3rJaw

[Rimpy69]

I am experiencing an issue on the 13.28 Beta5 and game startup screen for MAME only. After starting a game and then exiting, Bigbox will not start another game. Clicking Play does nothing. I have rolled back to 13.27 and confirmed the issue isn't there and if I turn off the game startup screen option it also works fine. Other Platforms seem to be fine, it just seems to be something with the beta 5 and Mame game startup screen.

Also, the thirdscreen plugin UI now has an error once you open it and then try to close (see screenshot). Once opened you cannot save or close the UI and have to exit bigbox which then won't save your changes. Again, rolling back the build to 13.27 fixes the issue.

Edited Sunday at 01:29 AM by Rimpy69
Added another issue

[crusadeRGP]

Right click on the Retro points text at the top only works for me when I use the default theme and not my current Omni theme.

[Jabb3rJaw]

After some testing i can confirm videos are back to playing and the scrolling in Bigbox is smooth. The random crash still happens which confuses me. Using VLC I had my machine running Bigbox for 8-9 hours yesterday no problem. Today it ran for about 30 minutes and it crashed back to desktop running Bigbox. No changes were made in between both instances so I’m really confused what’s causing the crashes. 

[JaredN]

Hello,

Yes, like @Jabb3rJaw, I had the same issue today with BigBox crashing without an error message after running for about an hour.
Much to my surprise.
I thought I was finally rid of this problem with the return of VLC... 😵‍💫

BB 13.28 beta 5.evtx

[Heartless1Riku]

Following up on my earlier report that transitions no longer play using VLC in big box (critical zonev2 theme). It also appears the the video stutters initially and the audio is cut off or does not come in fast enough causing some of the beginning audio of videos to be lost. Here is a comparison of 13.9 VLC vs Beta 5 VLC showing the lack of sliding transitions and the loss of sound (2 less words at the start of the video) and stuttering at the beginning of the video themes. Also using the VLC player causes the video to restart when going from the game view to the game details view in big box compared to when going from game details and backing out to game view in which case the player continues the video from the same point smoothly. Not sure if that is by design. 

Big Box 13.9 VLC

 

 

Big Box 13.28 Beta 5 VLC

 

 

 

[MysterNybble]

7 hours ago, Heartless1Riku said:

Big Box 13.28 Beta 5 VLC

 

Would you be able to turn on debug logging for this exact test and send over the 3 log files it will make? This is odd and hoping to see something in those logs. Thanks!

[MysterNybble]

On 7/26/2026 at 11:01 AM, JaredN said:

Yes, like @Jabb3rJaw, I had the same issue today with BigBox crashing without an error message after running for about an hour.
Much to my surprise.
I thought I was finally rid of this problem with the return of VLC... 😵‍💫

 

On 7/26/2026 at 10:30 AM, Jabb3rJaw said:

After some testing i can confirm videos are back to playing and the scrolling in Bigbox is smooth. The random crash still happens which confuses me. Using VLC I had my machine running Bigbox for 8-9 hours yesterday no problem. Today it ran for about 30 minutes and it crashed back to desktop running Bigbox. No changes were made in between both instances so I’m really confused what’s causing the crashes. 

In addition, the Windows crash dump could be useful if you're willing. Please look for a .wer file along with a .dmp, .mdmp, or .hdmp file from the time of the crash in any or some of these folders:

• C:\ProgramData\Microsoft\Windows\WER\ReportArchive (or ReportQueue)
• C:\Users\<you>\AppData\Local\Microsoft\Windows\WER\ReportArchive (or ReportQueue)
• C:\Users\<you>\AppData\Local\CrashDumps for a BigBox*dmp file

The crash dump is the important file. If none exists we may need to enable dump tracking in windows. Which you can do by:

1. Open regedit

2. Create the key/folder "BigBox.exe" in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BigBox.exe

3. Create the DWORD value "DumpType" with a value of 2.

Then if you can get it to crash again, look for the above files. The crash dump can contain personal data so you may want to send it to us private via email, DM, or featurebase bug report but collect the .wer, the .*dmp, and the log files in the launchbox logs folder.

[JaredN]

1 hour ago, MysterNybble said:

 

In addition, the Windows crash dump could be useful if you're willing. Please look for a .wer file along with a .dmp, .mdmp, or .hdmp file from the time of the crash in any or some of these folders:

• C:\ProgramData\Microsoft\Windows\WER\ReportArchive (or ReportQueue)
• C:\Users\<you>\AppData\Local\Microsoft\Windows\WER\ReportArchive (or ReportQueue)
• C:\Users\<you>\AppData\Local\CrashDumps for a BigBox*dmp file

The crash dump is the important file. If none exists we may need to enable dump tracking in windows. Which you can do by:

1. Open regedit

2. Create the key/folder "BigBox.exe" in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BigBox.exe

3. Create the DWORD value "DumpType" with a value of 2.

Then if you can get it to crash again, look for the above files. The crash dump can contain personal data so you may want to send it to us private via email, DM, or featurebase bug report but collect the .wer, the .*dmp, and the log files in the launchbox logs folder.

Thanks @MysterNybble !

I do have the .wer file, but tracking dump wasn't enabled. It is now.
The next time it crashes, I'll send it to you! 👍

[fianovale@hotmail.com]

For me the "DEL" key to delete rom, doesn't work after update to 13.28. And sometimes the font of the console list automatically put on BOLD font.

[AstroBob]

2 hours ago, fianovale@hotmail.com said:

For me the "DEL" key to delete rom, doesn't work after update to 13.28

Thanks, this is already fixed and will be in beta-6

 

2 hours ago, fianovale@hotmail.com said:

And sometimes the font of the console list automatically put on BOLD font.

Could you elaborate on this, does it happen all the time, or only within certain sections? If you have a screenshot handy showing it that would be very useful. 

Cheers,

[Heartless1Riku]

9 hours ago, MysterNybble said:

Would you be able to turn on debug logging for this exact test and send over the 3 log files it will make? This is odd and hoping to see something in those logs. Thanks!

Here you go, let me know if you need anything else.

Debug 2026-07-27 08-31-06 PM.log Debug 2026-07-27 08-31-27 PM.log Debug 2026-07-27 08-32-01 PM.log

[JaredN]

3 hours ago, AstroBob said:

Thanks, this is already fixed and will be in beta-6

 

Could you elaborate on this, does it happen all the time, or only within certain sections? If you have a screenshot handy showing it that would be very useful. 

Cheers,

Hi @AstroBob and @fianovale@hotmail.com

That bold font display has happened to me once or twice in LB as well. But I can't say more about it because it didn't persist after a restart, and I haven't identified any specific conditions that trigger it.