slickrickstyles

Any responsiveness issues i had prior to 12.14 are now completely gone. There seemed to be lag going from the main menu (bannerbox) to the platforms (coverbox) and the screen would sit on the console splash for a noticeable time (w10, 750ti, 16gb ram) as well as slowdown with the startup of video clips...This is completely gone and it truly feels like it is now running from the SSD as prior there wasn't much of a differential between mechanical or otherwise. Going on roughly three years as a customer now (i pay the yearly fee to continue to support) and I can say this may be the best BigBox update yet. I have now tested it on two other windows builds with lesser specs and it's just as snappy. Great job guys and thank you!

Came here for the same thing. I was starting to trip out since the audio returns once you interact with the cabinet. haha. Glad I find this post.

Amazing thank you! I will certainly revisit then...We truly appreciate your hard work!

Dang okay thanks was really hoping to be able to use this one.

Please excuse me if this has been asked elsewhere but is there anyway to change the time to a US style 12hr format instead of the universal military/24hr format?

Have been watching this thread for over a year now...I as well hope this is added in the future if a work around hasn't been found.

if i posted in the incorrect thread i apologize.

After the newest update I have had bigbox.exe crash while idling/in attract a few times. Here is the latest information from event viewer. I have **** the PC name in the listing for privacy. Faulting application name: BigBox.exe, version: 11.8.0.0, time stamp: 0x5f3ed523 Faulting module name: coreclr.dll, version: 4.700.20.26901, time stamp: 0x5ec48a29 Exception code: 0xc00000fd Fault offset: 0x000000000004b14f Faulting process id: 0x2350 Faulting application start time: 0x01d6c6a67597d380 Faulting application path: C:\Users\****\LaunchBox\Core\BigBox.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\coreclr.dll Report Id: b317b775-c34c-4f59-9ac5-347f5b927d0d Faulting package full name: Faulting package-relative application ID:

Stoked that you fixed the marquee issue. I thought i was going crazy haha. Thanks as always

Yeah it’s strange. Dropping back to 11.6 restores functionality of the marquee in multiple themes and platforms. It’s not an issue with marquee placement either. The program does not identify the second monitor as a marquee for me on 11.7 B6. I have not tried a fresh install though. I’m sure that will fix it was just sharing that it was odd especially considering the program will recognize it if you change the primary option.

I posted this in the wrong beta post. Sorry about that Updated to 11.7 B6 and the marquee screen option no longer works at all. Strangely enough the primary screen option above it does and allows me to switch the secondary screen (cabinet marquee screen) to primary. The screen used for marquee never changes when BigBox is open from the desktop background to the previously set marquee images. Changing the marquee screen option from 1 to 2 to none has no effect. This issue did not take place before the update from 11.6. -- issue was quickly resolved by reinstalling 11.6 from the updates folder.

I face the same issue after exiting in BigBox where bigbox.exe has to be closed manually before it or launchbox can be reopened

After upgrading I am now receiving the following error on BigBox startup but after alt-tabing and closing the error things seem to function. I did not see this particular error mentioned Index was outside the bounds of the array. App: Big Box Version: 11.6 Type: System.IndexOutOfRangeException Site: Void cVuPEeTrIQ(System.Object, System.EventArgs) Source: BigBox at Unbroken.LaunchBox.Windows.BigBox.Views.MainView.cVuPEeTrIQ(Object , EventArgs ) at System.Windows.Window.OnActivated(EventArgs e) at System.Windows.Window.HandleActivate(Boolean windowActivated) at System.Windows.Window.WmActivate(IntPtr wParam) at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) Recent Log: 10:47:23 AM Exception

Okay I will start poking around in the xaml's and see what I can find. Thank you for responding

Bueller? @faeran lol just kidding. Hopefully what I am asking about makes sense though.