LaunchBox 13.23 - Beta Thread

[faeran]

A beta is out that should fix crashing issues when entering Big Box for users that are using a 30-series graphics card (and other cards that have issues with certain types of unstable hardware decoding). It should also fix the issue some people were having with themes like CityHunter 2.

Once we have confirmation from enough users experiencing the crash that it fixed it for them, we will be releasing a hotfix just for that.

From there, we will continue down our next cycle, which will include smoothing out any rough edges.

[CliffordYuma]

3 hours ago, faeran said:

A beta is out that should fix crashing issues when entering Big Box for users that are using a 30-series graphics card (and other cards that have issues with certain types of unstable hardware decoding). It should also fix the issue some people were having with themes like CityHunter 2.

Once we have confirmation from enough users experiencing the crash that it fixed it for them, we will be releasing a hotfix just for that.

From there, we will continue down our next cycle, which will include smoothing out any rough edges.

Can confirm beta works for me. I was experiencing BigBox crashes and tried everything. Beta solved it. Setup:

 

Graphic card: Nvidia 3080 RTX 10GB

CPU: i7 12700F

RAM: 32 GB DDR4

Setup: Triple monitor

Codecs: FFmpeg and WMP. Both works fine, no crashes.

 

If you need more info, let me know

 

Thank you very much

Edited Saturday at 05:04 PM by CliffordYuma

[MB_CC_Manx]

Hi guys!

I´m on Launchbox 13.24 beta 1 and have the same problem with BigBox not starting.

I tried with WMP and FFMpeg but neither works. At least in Launchbox, videos works without problem.

My specs are:

Windows 10

Ryzen 3 3300X

RXT 3060 (I updated the drivers today)

16 GB RAM

I search for the logs in the event viewer from Windows but I dind´t found anyhting related with Launchbox or BigBox.

I'm ready to update with more info if you need and thanks for the work of searching the problem.

[NocturneRose]

No change for me on the Beta. BigBox still hangs and has to be forcibly closed.

Windows 11

RTX 3080 Ti

32GB RAM

I'd removed all the startup videos from the video folders and set Launchbox to use Windows Media Player

Fault bucket 1410739458890896977, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: BigBox.exe
P2: 13.24.0.1
P3: 67fe0000
P4: 3bc9
P5: 134217728
P6: 
P7: 
P8: 
P9: 
P10: 

 

Edited Saturday at 07:46 PM by NocturneRose

[faeran]

3 minutes ago, NocturneRose said:

No change for me on the Beta. BigBox still hangs and has to be forcibly closed.

Windows 11

RTX 3080 Ti

32GB RAM

I'd removed all the startup videos from the video folders and set Launchbox to use Windows Media Player

Fault bucket 1410739458890896977, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: BigBox.exe
P2: 13.24.0.1
P3: 67fe0000
P4: 3bc9
P5: 134217728
P6: 
P7: 
P8: 
P9: 
P10: 

 

That's unfortunately not the .NET error report. You'll find another report near this one that will provide a better picture of what's going on.

Also note setting LaunchBox to WMP is not setting Big Box to WMP, they are different settings.

2 hours ago, MB_CC_Manx said:

Hi guys!

I´m on Launchbox 13.24 beta 1 and have the same problem with BigBox not starting.

I tried with WMP and FFMpeg but neither works. At least in Launchbox, videos works without problem.

My specs are:

Windows 10

Ryzen 3 3300X

RXT 3060 (I updated the drivers today)

16 GB RAM

I search for the logs in the event viewer from Windows but I dind´t found anyhting related with Launchbox or BigBox.

I'm ready to update with more info if you need and thanks for the work of searching the problem.

We will need the Event Viewer report. Open Big Box, let it crash, then open Event Viewer, go into Windows Logs > Application, and you'll find about 3 reports related to the crash that you can post here. If you don't find any reports in there then the app isn't crashing and you may be experiencing something completely different.

[reflex33]

Weighing in on the network drive problem...

Windows 11 for me just like others. From what I can gather, if a settings file specifies a relative path to a specific file, then launch box will show it as a relative path. For example, I have attached a settings snippet for a game that shows that I have the rom specified as a relative path. And then you can see in launch box it shows it correctly. However, in the same game settings, you can then see that the video snap is showing a network path. I believe this is because this is an implicit path... meaning I don't have this in the settings anywhere and launch box is finding this video.

When it comes to the rom path specified for a platform, we don't specify a specific file, rather a folder. So next you can see an example platform I have where I have the rom path as a relative path.... but then launch box shows this a network path.

Finally, that same platform has a few image folders that I don't have in my settings file yet as I was just updating launch box, so it appears launch box shows a network path.

So... from what I can gather here we seem to have a problem in two scenarios.

1. The path is to a folder rather than a file
2. The path is a "derived" path rather than specified in the settings

The problem here is this wreaks havoc when I try to update a platform. If I scan for new roms, launch box tries to import all the games again.

[NocturneRose]

24 minutes ago, faeran said:

That's unfortunately not the .NET error report. You'll find another report near this one that will provide a better picture of what's going on.

Also note setting LaunchBox to WMP is not setting Big Box to WMP, they are different settings.

We will need the Event Viewer report. Open Big Box, let it crash, then open Event Viewer, go into Windows Logs > Application, and you'll find about 3 reports related to the crash that you can post here. If you don't find any reports in there then the app isn't crashing and you may be experiencing something completely different.

Thanks, 

I've double checked my BigBoxSettings and I've got    <VideoPlaybackEngine>Windows Media Player</VideoPlaybackEngine>

I've attached the error from event viewer, jsut seems to be in relation to it hanging though, I couldn't see anything else relevant (I barely know what I'm doing though, so sorry if I've missed something)

 

BBHangError.evtx

Edited Saturday at 08:19 PM by NocturneRose

[MB_CC_Manx]

1 hour ago, faeran said:

That's unfortunately not the .NET error report. You'll find another report near this one that will provide a better picture of what's going on.

Also note setting LaunchBox to WMP is not setting Big Box to WMP, they are different settings.

We will need the Event Viewer report. Open Big Box, let it crash, then open Event Viewer, go into Windows Logs > Application, and you'll find about 3 reports related to the crash that you can post here. If you don't find any reports in there then the app isn't crashing and you may be experiencing something completely different.

You are right. The app isn’t crashing neither opening. If I open the Task Manager, the BigBox process stays running but doesn’t crash.

I think that is related to the video player problem because when I had an startup video, nothing happened. But when I deleted it, at least shows the BigBox logo, but stays stuck with it in the screen. 

Is there some other way to make a logging that can help to trobuleshoot the problem? 

 

UPDATE: I resolved the problem. Ater I updated to Launchbox 12.24, I deleted the startup video while trobuleshooting the problem with BigBox not launching correctly. After that, I updated to Launchbox 12.24 beta 1, but doesn't restore the startup video, thinking that it would still cause problems.

Now I restored the startup video and BigBox works flawlessly. So I can confirm that the fix in the beta works.

Thakns for the help and the fast fix in the beta!

Edited Saturday at 09:26 PM by MB_CC_Manx
I'm dumb but found the solution

[NocturneRose]

1 hour ago, MB_CC_Manx said:

You are right. The app isn’t crashing neither opening. If I open the Task Manager, the BigBox process stays running but doesn’t crash.

I think that is related to the video player problem because when I had an startup video, nothing happened. But when I deleted it, at least shows the BigBox logo, but stays stuck with it in the screen. 

Is there some other way to make a logging that can help to trobuleshoot the problem? 

 

UPDATE: I resolved the problem. Ater I updated to Launchbox 12.24, I deleted the startup video while trobuleshooting the problem with BigBox not launching correctly. After that, I updated to Launchbox 12.24 beta 1, but doesn't restore the startup video, thinking that it would still cause problems.

Now I restored the startup video and BigBox works flawlessly. So I can confirm that the fix in the beta works.

Thakns for the help and the fast fix in the beta!

Did the same and restored the startup video to it's folder and that also worked for me

Edited Saturday at 09:38 PM by NocturneRose

[Jackdefjam]

1 hour ago, MB_CC_Manx said:

You are right. The app isn’t crashing neither opening. If I open the Task Manager, the BigBox process stays running but doesn’t crash.

I think that is related to the video player problem because when I had an startup video, nothing happened. But when I deleted it, at least shows the BigBox logo, but stays stuck with it in the screen. 

Is there some other way to make a logging that can help to trobuleshoot the problem? 

 

UPDATE: I resolved the problem. Ater I updated to Launchbox 12.24, I deleted the startup video while trobuleshooting the problem with BigBox not launching correctly. After that, I updated to Launchbox 12.24 beta 1, but doesn't restore the startup video, thinking that it would still cause problems.

Now I restored the startup video and BigBox works flawlessly. So I can confirm that the fix in the beta works.

Thakns for the help and the fast fix in the beta!

You're not alone in your dumbness haha. Restoring the startup Video fixed my issue as well. Can now confirm the new beta ist working for me too. Thank you very much for the fast fix - great work as always ! 

[sebas001]

Updated to the latest beta update. Can confirm that launching BigBox works again. Thanks guys!

[darreldearth]

Are we able to enable audio for the screensaver videos or use the games music?

Edited Sunday at 02:41 AM by darreldearth

[faeran]

5 minutes ago, darreldearth said:

Are we able to enable audio for the screensaver videos or use the games music?

Check under Sound options for something called: Idle Master Volume

[darreldearth]

7 minutes ago, faeran said:

Check under Sound options for something called: Idle Master Volume

thanks that was it 👍

[Cineaste]

Can confirm the new beta fixed Big Box running on a 3070. 

My thought process quite literally went like this in the span of 5 minutes:

 

[cenutrio351]

Last beta works for me, thanks!

[skizzosjt]

there is a problem that has been occurring since version 13.22 the official release. All betas and official releases since then reset game videos and animation type stuff happen when exiting any game from any platform. It's 100% recreatable every time. So for example I boot Contra from the Arcade platform. Upon exiting, the game video actually resets to the start. You can briefly see that it is paused right where it left off but then it resets instead of continuing where it left off. Then at the same time all the text and badge images, etc, the chunk of info in top right area of the default theme will re-animate as if you just entered the view. Seems like it's doing all the stuff it would do if you just went into the view, rather than returning from exiting a game. This is noticeable and 100% recreatable on every custom theme too. Both video resetting and other animations reoccurring at exit when they should not be running. 

If I reinstall v13.21 or earlier the problem is not there. I then reinstall v13.22 or anything newer and the problem exists. The problems exist on default and custom themes regardless of the media player I have selected. Video for reference using v13.24 beta 1....

 

 

 

 

 

 

[viajante]

BigBox now works with new Beta 13.24. Back to owrk and reconfigure BigBox menu, layouts, etc as messed up everything after many attempts to fix BigBox myself in the last week uninstalling LB couple times, even remove keys from Windows registry trying a clean reinstall and other try and errors. I disabled the automatic update on both of my cabinets as in the last 2 updates I faced crashes on BigBox. On past updates it was not an issue but now I must be careful before decide to update.

[zombiesruuun]

Had the same problems here with FFmpeg crashing and startup video woes, and the beta fixed it all. Windows 11 with a 3060 ti. Thanks for the fix!

[Boomerps2]

I'm just going to wait for 13.25 to play it safe.....I think