ZeSystem

I don't expect beta versions to be flawless or without issues. I don't mind it being unstable . If it's a minor convenience, I can report it, and still use it until it gets fixed, or if it's a major problem I can use the stable version until then. Not sure why you still want to force it on every beta user without giving an option to turn the logging off because this just discourages more users like me to even test them out and provide feedback. You can simply turn it on by default and still give us an option to turn it off. I don't really see the downside to this approach and it only brings flexibility and more positive experience for concerned users like me. It's not the performance impact I'm worried about. I highly doubt it would have any impact on my 5GHZ 8700k + SSD, but I don't like the app writing whatever you decided to log (note that I'm not worried about nor trying to raise an issue about telemetry at all) every time I use it on my SSD, and gradually increase the file count. Sure, I can delete it, but this is just unnecessary inconvenience. As a software developer myself, I completely understand how important it is for bug tracking, but it's never late for users to enable it whenever they want to reproduce it before reporting it. If they bothered reporting it, you would still prefer them to provide how they encountered the bug so the users should be fine going back to turn the logging on (for those who had it off) then, and reproduce it to provide more concise information on their report. If they can't reproduce it (which I believe is an incredibly rare case, if anything) and had the option turned off, then it's the user's fault. LaunchBox navigation and usage isn't all that complicated and it would be hard to forget how the issue you experienced happened and not be able to reproduce it again.

How about forcing the logging by default for beta versions, but still provide an option to turn it off? I have everything installed on SSD, and I really would rather not have them logging since my beta experiences have been always great without problems worth reporting.

Even though there is a plenty of space on row 3 and for two more items on the row 2, items don't list until i further scroll down. It seems to happen on some views (zoom settings). Spacing and everything is set to default (although I don't think they work on .NEXT yet).

I abuse BigBox pretty bad with aggressive browsing and keep it running for a long time 24/7 and it's pretty stable. I don't see how it could trigger blue screen. Are you sure it's BigBox that's causing it? What's the error message on the blue screen? It should be easier to track down the cause from there.

Thanks a lot, this worked!

Yeah, but that's not my preferred way of emulating NES.

Currently considered as the best NES emulator by many, mesen command-line options do not work (loading roms) if you have default command-line parameters before the rom path. Please allow us to put the command-line parameters AFTER the rom path. Thanks!

Man LB launches within a second. What a crazy improvement we got recently. I wish this was the case for BigBox too :'(

If you mean LaunchBox.Next, just press the button that says "LaunchBox.Next" on the LaunchBox UI. It's located at the top right of the window besides the "BigBox" launch button.

Just tried this tonight. I absolutely love the look and how snappy it is (assuming once the functions are added it would stay that way). My main usage is BigBox, but during maintenance I use LaunchBox. This is a very unexpected surprise! Great work! Looking forward to this.

If you are just running through your library one game by one, yeah my system runs smooth. If I'm aggressively skimming through the library by jumping through letters, yeah it has a minor stutter. I wouldn't say it's performance issues. It's just loading the logos and videos for the first time. It's a minor strutter, but enough for me to feel guilty to say "it runs fine". I also stand by my statement that I'm sure my system is perfectly fine. You just probably don't browse aggressively as I do. Good for you it runs fine on your weaker systems. I look forward to more consistent performance from BigBox in the future.

Perhaps your definition of "perfectly fine" and mine are different. BigBox doesn't run well when I'm browsing through my library once per app launch. My library consists of thousands of games with videos and I make a good use of fast fingers for browsing and skipping through letters. When I browse through them, it stutters a bit. Everything is installed on SSD. The stutter goes away once I have browsed through them once (per app launch). I'm sure my system is perfectly fine. I run daily maintenance and monitor them while I use them. Thank you very much.

BigBox doesn't run well on old PCs. It doesn't even run well on my 5ghz 8700k + 980 Ti + NVMe SSD setup. It struggles to run smooth on my 2 year old IBM laptop. I highly doubt it runs well on older PCs. I've seen many of budget arcade setups (older PCs, Pi, linux, etc.) from other communities, but none of their specs could run BigBox. Don't get me wrong. Optimization is a great thing, but I agree with DOS76 here. "Most of the time LaunchBox (or BigBox) is used for projects like turning old PCs into Arcade Cabinets" is a BIG assumption without any basis.

That's understandable. Thanks for clearing that up!

Hi @Jason Carr , I noticed scripts don't call OnExit function (https://autohotkey.com/docs/commands/OnExit.htm#function). Is this because Launchbox just kills the script process? Would you be able to fix it to have the script app (autohotkey) is closed properly so it calls the OnExit function?

Thanks!

Cancel closes the window.

Like, random game videos in a custom playlist? Where can I find his latest plugin?

Ah, yes that's what it was. Thanks a lot! I'm super glad it also made the cut !!

Hey @Jason Carr! This has the highest vote https://bitbucket.org/jasondavidcarr/launchbox/issues/534/option-to-create-custom-submenus-and at the moment, so I'm assuming it was in the votes, but my not so vivid memory suggests I didn't see it. Was this feature part of the "sub-folders" or any other entry, or was it not included?

Wow, this was a nice surprise. I've always wanted the easing option. As a person who consistently updates their library with custom clear logos, I happily welcome that delete function! Also, I'm not seeing much difference with easing enabled. Is this because I set the speed to 100ms or 200ms?

Ah, I see. Makes sense since it's probably as fast as it can get (8700k 5ghz + NVMe SSD). LaunchBox still loads faster so that's a huge plus.

Jason said he reverted the change because it was causing performance issues. My BigBox loaded 8 seconds before, and then it used to load in 5 seconds until it went back to 8 seconds when he reverted the change. I think Launchbox still loads faster than before, though, so only no loading speed changes with BigBox.

LaunchBox and Big Box startup times have been significantly reduced Time to remove this from the feature notes, sadly.

Loading speed for BigBox has increased back to 8~9 seconds (may be beta9 or beta10) from 5 seconds (beta8 and below) on subsequent runs. Everything installed on SSD (including videos and pretty much everything BigBox loads)