MysterNybble

I have low confidence in this actually helping, but I was able to give this a go ... but I don't think it's quite there yet (which is why it's not even in the change log), but I added something I'd like you to test for me: You'll need to restart your app for it to go into effect. It may actually make playback worse (but will apply to both big box and launchbox), but curious if you can try this out to compare and let me know what you see/feel. The long of it is that WPF (the UI technology LaunchBox and Big Box are built on) can naturally reach 40 fps (on my machine) for custom rendering, but it offers a lower-level option, that this experiment is trying to replicate. It was a bit of a rush job, and I had mixed results on my very capable machine, so I may not keep it as much more than an experiment until I can figure out what else I can do to improve it.

Good news is beta 6 (coming soon, likely tomorrow) should restore missing video transitions and fix the vlc thumbnail flash. We've also improved the startup handling to be more resilient (not confident this will fix your issue, but it could, and if it doesn't, it should produce better diagnostics to help us figure it out). I am also looking into your fps report for vlc to see what we can do there, likely not in time for beta 6 but maybe before release if I can figure it out. Thanks for all of the reports, videos, and logs, they really do help us find issues or at least find limitations in our diagnostics.

Thanks so much for pulling this - super helpful, and apologies for missing these when you reported them in 13.27. Good news: this crash seems to align with one that we saw and should be in beta 6 (which should be out "soon"). Of course, with software, fixing one thing may just highlight something else, but progress is progress. Thanks again.

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: Open regedit Create the key/folder "BigBox.exe" in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\BigBox.exe 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.

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!

Thanks for the video. If you had debug logging enabled, can you share those files (there should be 3 per run) as well? If not, can you turn it on and recreate a short session similar to your video, showing that the videos aren't loading in, then wait on one of them to see how long it takes to load, and then go back to just navigating around (but try to do all this in 30s so the logs don't get too confusing)? At least do this with the VLC video engine selected, and if you have time, repeat the same test (closing and reopening between each test so we can get clean logs). Doing WMP as well might be useful as well, but please close/open Big Box between the tests to create separate log files. Thanks for helping us out!

Super helpful! Thanks so much. If you relaunch your Beta 3, it should tell you to update the media engine plugin (should update to 1.0.5), then restart when it prompts you to, and cross your fingers, and it should fix this issue with VLC playback (and has a strong chance of fixing the related issue with WMP/ffmpeg as well, but I haven't confirmed that yet).

Would love to see the debug log files if you can recreate this for me. Enable debug logging in LaunchBox's options, then recreate the issue. This will create 3 files in the Logs folder: the normal log and 2 media-engine logs. The media engine handles background music irrespective of which video player you choose, so seeing these logs will be useful. Good to hear. We're hoping to lean into this VLC player/media engine as *the* video/audio playback solution across the board once we iron out all the wrinkles.

Can you help me understand this better? How long does it take to gobble up all that memory, and how are you using it? Screenshots of task manager would be useful (before/after/timing) More interestingly, what *exactly* do you mean by "never gives it back"? Does BigBox.exe stay running (according to task manager) or... where does the memory go? Would love to fix this for you (and everyone). (also read faeran's post above for other information that is useful for us to have)

Thanks! We do a manual merge so any/all changes should be seen

It's been longer than usual since the last beta, but Beta 3 is here with the following changes: New Premium Feature: You can now rearrange and remove filter sections in the Side Bar - Tools > Options > Visuals > Filters Side Bar > Section Management Improvement: The Edit Game window now includes Next/Previous buttons, allowing you to quickly navigate through the list you opened it from Improvement: Progress automation now supports a customizable whitelist of allowed values for finer control Improvement: The Side Bar quick filter now supports additional options for more convenient filtering Improvement: Improved cloud sync accuracy Fixed: Improved date handling to prevent crashes in certain locale-specific calendar scenarios Fixed: Restored Steam trailer downloads and resolved associated crashes. In addition to a usual round of bug squashing from things reported here, the feedback site. The Beta Spotlight has been updated with some additional details on where and how to focus, so be sure to check that out. Not exactly an item worthy of a bullet, but this build is also our first to be digitally signed with our new EV Code Signing Certificate. This helps improve our reputation with the Microsoft SmartScreen filter (as well as other systems) and should reduce warnings when downloading LaunchBox from our website. You likely will not notice anything, as LaunchBox handles the installation for you, but we wanted to note this for posterity. We are also considering this release largely feature-complete for the upcoming version. Beyond some final polish and looking at anything uncovered for your feedback on this beta release, we're in great shape to push out an official release soon. As always, your participation in this is beyond valuable. Thank you for all your help and feedback!

I pushed a hopeful fix for this a few minutes ago (works on my machine ™). Can you give it a spin when you have a chance? Please double-check that it's working by reviewing your 'changes status' screen, as I think some of your edits never made it to the database 😢. I am not 100% sure when this was introduced, as it appears to be downstream from an unpinned package version🤬.

approvals should be going through and the random gateway/server errors should hopefully be better as well, thanks all!

I hope the bad gateway is now a good gateway. I think I got to the bottom of this issue and pushed out a fix. and @launchretrogirl2562 your pending changes should start going away throughout the day as the system catches up. Thanks all for your help reporting these issues!

I put a pretty noticeable speed improvement in place for the search feature - how does it feel for you now?

Figured it out and fixed - please confirm, thanks :)!

For those that care this migration was indeed quite a bit: .net 6 -> .net 9 mssql -> PostgreSQL windows/iis -> linux/docker/traefik manual deployments -> automatic deployments/migrations insanity -> sanity I go sleep now 😛

Hmm, are you still getting this? I know we had some side effects of the DNS updates we had to make causing intermittent outages like this, can you confirm? :crosses_fingers:

Thanks for these reports :). These issues should be fixed. The approval queue was backlogged due to an error which has been fixed. It is catching up, and should be done in the next 10-15 minutes. The edit page should also populate those fields correctly as well. @C-Beats is correct that we are on a brand new/different DBMS, which means we have to redo a number of the performance tweaks we made over the years on the old system. Stay tuned - should be pushing out more of these fixes in the next few days :).

Thanks for the heads up - all fixed now, I hope. Let me know if not.

This should be fixed, btw! Thanks for reporting. We found the issue - turns out it was broken! I can't say who made a mistake (it was me), but someone made a mistake (again, it was me), and I have heard a rumor that they fixed it (I did this too). Your guess was mostly right; there was a discrepancy between the thing that determined how many results we have (to show the paging) and the thing actually showing the results (the grid). They are now the same.

🤔 If anyone sees this issue again, post a screenshot. It might be helpful for us to figure it out. Thanks!

Would you be willing to produce a crash dump that we could analyze? If so, download this https://learn.microsoft.com/sysinternals/downloads/procdump From an admin elevated command prompt from where you placed procdump, run procdump -e -ma Path\To\LaunchBox\Core\LaunchBox.exe Then go and make LaunchBox crash - that should create a file from wherever you ran procdump from - then, using your favorite secure file sharing service, send us a link to support@ email or through our bug report system at https://feedback.launchbox.gg/ I'm not confident we'll see anything useful, but without any other errors from your machine, I'm hopeful 🤞 (let me know if you need any help with the above steps / command)

@superrob3000 well done! I'm glad you found some inspiration during the stream - all ideas are free; you did the important bit, getting it done 😂. It's really cool to see the NFC stuff come to life.

It's just how I do it - not sure why or when I started ! I just push my keyboard back where I reach it from resting most of my forearms on my arms on my desk, then wherever my hand ends up when I rotate at my elbow toward my chest is where the mouse goes. For me, it feels more natural than having to go the other way, but I have been doing this for ... ever. I mean, laptops kind of do it this way too... (I say defending myself because I know it's weird) Insane... or brilliant?! Thanks!