MysterNybble

I'll try to confirm myself, but if you did get a debug log on this, might be useful to compare against

First off thanks for all the details :). That said, not sure what you mean by this? https://feedback.launchbox-app.com/ is the official bug reporting form for live builds. I can take note of them from this thread as well (though if I don't get it addressed, please submit something official). Can you confirm Joe's suggestion, I think he's right. If that doesn't pan out, do you recall when this last seemed to work ok so I can compare the code? I shall take a look; debug logs might be useful here if you can provide them. Might point me to where the time goes. Debug logs most likely will help me here, if you can provide them that would help. I'll ruminate on these and if any make sense for this next beta I'll see what I can do.

Great to hear. Selfishly this speeds up all my testing :-P. I'll try to get this in for the 14.1 release as it should be a relatively small one now that I got the rest in place. Stay tuned!

Why? Do ones after that fail or limited for another reason? For your first attempts when you say it isn't working, does it literally do nothing? Double click and nada? Might check the windows application log to see if anything is in there.

I didn't get a chance to reply as I was focused on getting the beta done. If you are still seeing this in beta 2 please send me the debug logs so I can dive in.

You are correct, I think when we wrote that plugin they didn't have a stable release or strongly discouraged people from using it so we went with nightly. Probably time to revisit and use the 2.x stable. I did add the plumbing to support configurable release channels for these just didn't have enough time to finish and make it usable for this release. Great to hear!

Beta 2 is here! Thanks to everyone who poked at Beta 1. A large portion of what's in this one came straight from your reports and feedback. The overall focus was making Beta 1's big changes behave better, plus a few things I was unable to finish up for that. tl;dr; reconnect your games database account once (it's an Unbroken Account sign-in now, keep an eye out for wizzy), LaunchBox and Big Box start and close hopefully a bit faster, less crashing/leaving things running, MAME high scores got a big upgrade, and the usual pile of fixes HIGHLIGHTS LaunchBox Games Database features (cloud sync, ratings, and MAME high scores) now sign in with your Unbroken Account (basically your GamesDB account but differently named). You will need to reconnect once after upgrading since we moved to OAuth. LaunchBox and Big Box start, save, and close faster. Hopefully with less memory (especially on larger libraries) and I removed a bunch of redundant file writes. Closing now waits for saves and cleanup instead of crashing or lingering and handle problems during close more gracefully (especially for your controller only setups). Introducing LaunchBox Game Pulse our modern replacement for hi2txt, with almost a thousand more games supported, leaderboards for a bunch of clones/regional versions, and all while running a fair bit faster. It also moved to the Plugin Manager so we can update game definitions without having to release a new version of LaunchBox. Leaderboards card has a new My High Scores link as well. EmuMovies added to automatic imports. Options > Automated Imports Media, pick the EmuMovies images, videos, manuals, and music you want downloaded for automatically imported games. Existing media is left alone. Games whose files are unavailable now show as Missing instead of Installed, and the Game Details button sends you to Steam to install or repair them. Smoother Big Box wheel animations and leaving game lists, Discovery pages, or videos is a bit tidier and doesn't leave as much stuff running in the background. Please retest any issue you saw in beta 1 as well as these new features. The full testing list and changelog are in the Beta Spotlight (and I'll update the original post as well. Same rules as before. Read, follow instructions, provide DETAILS. MORE DETAILS MEANS MORE FIXES :). Thanks so much for the beta 1 testing, hopefully beta 2 goes just as well. Beta 3 will be limited to related issues you report, small fixes, small QoL improvements, and some more minor performance tweaks. If that goes well, we might do a full release or a small beta 4.

I think I've already got the achievement issue fixed for the next beta, so stay tuned for that. For the stuck emulator it's possible that it's related to the achievement issue. Since when we "pause" the game we literally suspend the process and if BB crashes before it has a chance to resume it, it may not recover. So hopefully beta 2 fixes that for you as well, If you think it's something else, debug logs *might* help, maybe.

Thanks - and if you want me to help poke at it, DM me the exo plugin you are using, and I might be able to see if it's us or them :).

Thanks, I'll see what I can find.

That's a good idea, I'll think about this some more and see what I can come up with.

Thanks, that helps. I'll see what I can find, I'll let you know if I have any more questions.

The only things that might help me out further are... Are you seeing this in LB and BB or just one of them? As always, debug logs may be helpful, so send me what you got! Thanks though, will do some investigation to see what I can find.

You are a beast with the testing - I can't tell you how helpful all of this has been, thanks, thanks and thanks once more. I got some ideas, some guesses, and some fixes on the way for beta 2 to hopefully help out some of these things, aiming for early next week on that.

Would you do me a favor and... Test with the Default theme and Default pause theme, so we can know if it's in our theme code versus deeper down in Big Box itself Any specific game/emulator/store you remember testing that was causing the unresponsive window Once you can get Big Box closed, send me up some of your debug logs so I can see if anything is useful in there Thanks so much!

I'm printing off your comment and will ask my mom to put it on the fridge... Thanks for the positive feedback and your specific successes. That windowed full screen is a game changer for sure.

I have something in the works for the translators to hopefully make it easier. Things are pretty volatile right now with the language so I'm not quite ready yet to ask for your help, but I'll be sure to let you know. You'll know more probably toward the end of next week.

Thanks - do you mean 14.0.1 (the hotfix released a month ago) or this beta? That's said, it's odd, because I don't see anything in the code that would reset it for mame/emulators games. Can you close LB/BB, temporarily disable your plugins (just move the folders under \Plugins somewhere else for now), and then test again? I'm not confident it's a plugin issue, but worth ruling out. If that fixes, then you'll need to systematically bring back in your plugins to see which is causing it. The issue may still be on our side, but without knowing if it's a plugin (and which one) not much for me to look at yet. I am going to add a "view my highscores" like thing to Beta 2, so stay tuned for that. Alternatively, just get better at the game and get into the top 100 😜

Now we're getting somewhere, thanks! What I can see is: Big Box was technically ready in about 37s Your startup video was 97s and Big Box naturally plays to the end, you can of course skip this but you already know that A mysterious 48s delay before you even see the video (plus the 97s to watch) account for most of the apparent delay. This is my main area of concern but neither the logs or diagnostics tell me very much. I THINK if you removed/disabled your startup video BB would load "much faster" but that doesn't fix the issue, of course. I will likely need to add some better logging/diagnostics to beta 2 to get to the bottom of this.

Can you clarify a couple things for me... "double control" - when it happens, does one button press move twice inside Big Box, or do Big Box and the window your other screen both react to the controller? Would you mind sharing what other window you have that isn't the game or Big Box? Big Box intentionally tries to ignore controller inputs when it does not have focus EXCEPT for bound hotkeys (exit game, pause screen, volume, screenshot, bring BB back up front). Are you asking for this to be different?

That's certainly not ideal. Can you send me: The debug logs from one (or more) of these slow starts so I can see what's going on Which storefronts you have enabled and what their import setting is (all, installed, none) Do you happen to see any games being imported multiple times, perhaps from the storefronts? Also, it would help if you enabled and repeated startup test: Options -> General -> Share optional performance diagnostic Separate to the above, if you disable Options -> General -> Automataed Imports does startup improve dramatically? This will help out a lot, thanks!

It might be worth looking at your setting for (from LaunchBox) Options -> General -> "Share optional performance diagnostics" and checking it if it isn't. Restart LB/BB and then relaunch - this does have special capture for startup timings and can help us find patterns.

Thanks a few observations: Big Box naturally waits for your startup video (TRON something or other) and according to these logs it's seems long - 96 seconds - does that seem right? This might muddle the logs a little bit, so can you repeat this by pressing some keys/buttons during startup to "skip" the video? Make sure LaunchBox/Big Box are completely closed when you pull the logs the Debug log especially looks cut off (only 5 lines which I'd expect many, many more) Can you try the Default theme for the stutter issue? Want to confirm it's a Big Box issue or somethings specific to that theme. Let me know if Default behaves the same, worse, or better than what you're seeing in your preferred theme. Thanks again!

Thanks for noticing - really trying over here to do good for all of you :).

The requested details from the original post would be useful here, especially your logs, specs, Windows version/build, which theme/view you're showing in the videos, and which plugins you're using (so basically all of it). Also how does it compares to 14.0 if you used that as well. same? worse? better?