Jump to content
LaunchBox Community Forums

MrSco

Members
  • Posts

    102
  • Joined

  • Last visited

Everything posted by MrSco

  1. Adding a delay of 5 seconds in a ahk script that launches demulshooter instead of launching the exe directly from additional apps fixes the issue.
  2. did you ever find a fix for this? I'm having a similar issue but it seems to happen randomly and almost every time if I launch demulshooter as an additional app before the emulator... no demulshooter and black screen issue never happens
  3. After I kill launchbox and big box, I can just start them again and it works without having to restart the computer
  4. Oh I completely understand. Besides that the software is amazing and I recommend it to everyone. The crashing is the one pain point and stands out for me since everything else works so great. one thing that seems more unique to my crashes then others is 95% of the time when it crashes there is no error message. Others seem to get an error message. I’ve had error messages and Event log entries and posted them in this thread above I believe. But most of the time, The bigbox process just locks up and all videos freeze and controls are unresponsive. I have to kill from task manager.
  5. Default theme. As you can see from the multiple threads, many people are having the same issue for a very long time now.
  6. Yep. On latest version of everything. Including launchbox 13.14 and using VLC as video setting. Coming up on a decade of this issue persisting. Something is fundamentally broken with continuous videos playing in bigbox. I smell memory leaks or a race condition. But from what I’ve tested my library isn’t the issue. BigBox software is.
  7. I'm on default theme now on a brand new computer with brand new windows install on a nvme ssd. I renamed my Videos folder to Videos_disabled and ran attract mode for 3 days no problems with images only.... but with videos playing i'm lucky if i get 8 - 12 hours. I also ran all my video files through ffprobe and moviepy with a python script to check for bad video files and no errors thrown... import os import subprocess from moviepy.editor import VideoFileClip # Replace 'folder_path' with the path to the folder you want to check folder_path = 'H:/Arcade/LaunchBox/Videos_disabled' def check_video_files(folder_path): print('starting...') for root, dirs, files in os.walk(folder_path): for file in files: if file.endswith(('.mp4', '.avi', '.mkv')): file_path = os.path.join(root, file) try: clip = VideoFileClip(file_path) except Exception as e: print(f'******Corrupted video file: {file_path}******') else: clip.close() result = subprocess.run(['ffprobe', '-v', 'error', '-show_entries', 'format=bit_rate', '-of', 'default=noprint_wrappers=1:nokey=1', file_path], capture_output=True) if result.returncode != 0: print(f'******Corrupted video file: {file_path}******') check_video_files(folder_path) so it seems like bigbox attract mode fails playing video files after some random amount of time. but we already knew that... for years now. I wish it would be fixed. I think @Jason Carr mentioned he did attract mode stress testing with videos playing, but not sure how long
  8. I believe I tried images only years ago. Probably in the thread above somewhere. It’s almost definitely related to the videos playing. That’s the only reason I run attract mode is for the videos. I even tried deleting all the media and having launchbox redownload it all fresh. I even setup a webcam to watch the screen so I could capture when it was dying but it was always a different video/game. It shouldn’t be a mystery to get a bunch of videos to play continuously in shuffle. Wtf
  9. Yep. It’s super lame that bigbox can even run attract mode for a day. It’s just playing videos. I even upgraded the entire computer to an amd 7840hs with 32gb of ram and an nvme 4TB ssd. Computer is a beast but bigbox dies trying to do attract mode for an extended period of time. It’s been like this for years. 6 years or more. @Jason Carr doesn’t seem interested in fixing it.
  10. Thanks. That must be a new setting. Me likey.
  11. I’m having this issue now with the newest version of launchbox. All audio settings are correct and all audio works until after the first game gets switched away from. Then no more sound until I hit a button to stop attract mode and then sound from videos play again.
  12. i spoke too soon... just got a crash... at least there's an error message now? also when it crashed RAM usage was around 12gb out of 16gb and after it was around 4gb used out of the 16gb total. so it looks like a memory leak. I recently upgraded the nuc to have 16gb of ram (instead of 8gb)... Value cannot be null. (Parameter 'obj') App: Big Box Version: 11.11 Type: System.ArgumentNullException Site: Int32 GetGeneration(System.Object) Source: System.Private.CoreLib at System.GC.GetGeneration(Object obj) at Meta.Vlc.Wpf.VideoDisplayContext.Dispose(Boolean disposing) at Meta.Vlc.Wpf.VlcPlayer.<>c__DisplayClass123_0.<VideoFormatCallback>b__0() 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) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(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) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Threading.Dispatcher.Run() at Meta.Vlc.Wpf.ThreadSeparatedImage.<>c.<get_CommonDispatcher>b__8_0() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() Recent Log: 8:48:44 AM Exception
  13. Same here. No crashes in 48 hours. Could be .11 or removing the .flv files. well done sir on identifying the flv! I’ve been dealing with this for 2 years! I was able to remove the relaunch loop from my startup script! thanks to everyone on this thread for their ideas and help and especially to @JohnnyK for figuring it out and @Jason Carr for making the most epic front end software evar!
  14. i went back to check what video file types i have for Ninento Satellaview when i got this crash recorded happening in real-time, but they are all .mp4 ... so i'm not sure its it... but maybe its queuing them up in the background?
  15. quite... i have about 142 .flv video files out of 18,000+ total videos... so that indeed would be random AF if .flv causes the crashes
  16. @JohnnyK here ya go... #SingleInstance ignore SetWorkingDir, H:\Arcade\LaunchBox\ ;get the exe we should run. launchbox or bigbox target := A_Args[1] if (target = "") { target = LaunchBox } targetExe := ".\" . target . ".exe" targetName := target . ".exe" Launcher: ;launch the frontend and wait til it closes to continue RunWait, %targetExe% Process, WaitClose, %targetName% if (target = "BigBox") { Gui, Font, s18 Gui, Add, Text, x10, Relaunching BigBox in... Gui, Font, s32 Gui, Add, Text, vCountdown_text x160, 5 Gui, Font, s14 Gui, Add, Progress, vMyProgress x10 w300 Range0-5 Gui, Font, s24 Gui, Add, Button, w300 h75 Center, Cancel Gui, Show, w320 h240, Relaunching BigBox while (A_Index <= 10) { GuiControl,, MyProgress, %A_Index% GuiControl,, Countdown_text, % 11-A_Index Sleep 1000 } Gui, Destroy Relaunch: ;launch the frontend and wait til it closes to continue goto Launcher } GuiClose: ButtonCancel: if (target = "BigBox") { Gui, Destroy } RunWait, %comspec% /c taskkill /F /IM autohotkey.exe, , Hide ExitApp
  17. If you look in the earlier posts in this thread I posted an older version of my script. I’ll try and post my updated script when I get back home later. most likely you’ll need to customize it for the startup apps you are launching but the relaunch feature is in there and you can rip out the rest
  18. Yep. It’s definitely the videos for me too. Something with how launchbox handles loading and unloading video files. It eventually just can’t keep up. Doesn’t matter how much computer hardware you throw at it. It’s software. to work around the issue my bigbox launcher runs an ahk script that just keeps relaunching bigbox when it’s closed (or crashes) with a cancel button to keep it closed if that’s what you meant. I can share the script if you want to try it. I just gave up trying to have non-crashing software. At least bigbox is infinitely easier to setup then hyperspin ... it just is a super performance hog unfortunately
  19. It seems to only happens when videos are used (maybe just fullscreen video) and it doesn't matter what theme is used (unless the theme view has fullscreen video?)
  20. Nice, I plan on adding a 2TB m.2 ssd one day. It should help with the bigbox wheel responsiveness hopefully. I'm running off a usb 3.0 external 2tb and loading new wheel images can sometimes lag blank for a few seconds. My 6th gen NUC actually can handle KI also, but I have to crank the resolution down to 720p and then some particle effects can cause a stutter. But still amazing for such a dated lil machine!
  21. Ah ya! Sinden! i can't wait! I ordered 2 recoil guns. Super stoked! Ya, your NUC is a beast with the radeon graphics! bigbox should be child's play running off m.2 ssd drives.
  22. I have a feeling BigBox doesn’t like onboard graphics like the intel iris the NUC has. jason, do you ever test with low end gpu? These retro emulators, even up to PlayStation 2, run pretty well on these intel gpus, so they should have plenty of horsepower to run bigbox. megashub, you running bigbox from external drive? Or on those m.2 ssd? your NUC is 2gens newer then mine so should be more then capable of playing even some of the latest AAA games
  23. Unfortunately it’s still crashing Just the same. About four times since I updated in the span of 24 hours.
  24. I tested with latest beta starting last night around 9pm and got a crash this morning at 630am
  25. another crash this time on 11.6 on the NUC (last crash after removing 'bogus' images was on my 8700 i7/1080ti rig)... Faulting application name: BigBox.exe, version: 11.6.0.0, time stamp: 0x5ee99cfc Faulting module name: ntdll.dll, version: 10.0.18362.1049, time stamp: 0xb5beef21 Exception code: 0xc0000374 Fault offset: 0x00000000000f9229 Faulting process id: 0x2ac0 Faulting application start time: 0x01d68e967776e434 Faulting application path: H:\Arcade\LaunchBox\Core\BigBox.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 2d7a28a5-9bc9-4653-bfa9-97617a9974dc Faulting package full name: Faulting package-relative application ID: there was a fault bucket error in the log just after. i attached it as well Report.wer
×
×
  • Create New...