Jason Carr

What's it doing exactly? Ah, yes. I'll look into that. I also just realized that I haven't yet updated the details line on the boxes to change based on the arrange by. That's coming as well.

Just put out beta 10 folks with Arrange By finally implemented in LaunchBox.Next. We're getting very close to the end; the only major thing I can think of that we're missing is controller features (game controller automation and being able to control LaunchBox.Next itself with the controller). Hopefully that won't prove to be very difficult and we can prep for the next official release by the end of next week. If there are any features other than this that you can identify as missing from the original LaunchBox, please let me know. I know there are some minor tweaking things that are missing, such as font and spacing controls, but other than that I think we're getting pretty close. I will look to add some additional options as far as displaying the boxes and such once we have everything else tackled. Oh, Jaron is working on getting the column hiding and ordering working in the list view, so there's that as well.

Sure, I'll make a note to reduce that minimum width. It needs a minimum width of some sort in order to prevent things from going haywire, but it looks like we have some room to spare.

Hi @alnyden, that's a strange one indeed. I haven't changed Big Box at all in any of the latest betas, so I'm doubtful that it has to do with the code in the betas. What theme are you using? Does it happen with the Default theme?

Hi @Dan, if you edit that game, what is listed in the Video field under the Other tab?

Though it may not seem like it due to all the added fancy graphics (which do require more hardware resources), Big Box is already on par with LaunchBox.Next performance-wise.

Put out betas 8 and 9 earlier to further test and troubleshoot the out of order sidebar items issue, which still wasn't fixed for some people believe it or not. It does appear to be thankfully finally fixed in beta 9.

Hi @Alulabxxx, Big Box has not been changed at all in the latest beta, so unfortunately I'm guessing the issue isn't directly related to the update. Can you try reinstalling the official release over top to see if it resolves the issue?

Just fixed the Twitter image as well as the dark-on-dark text in the user drop down menu at the top (for the dark theme). Let me know if you guys spot any other issues.

Thanks @Agent47. Looks to be an issue with the forums upgrade.

Thank you guys. Appreciate the positive feedback.

Beta 7 is out now guys with the following: - Improvement: Options to disable side bar counts or not right align them have been implemented in LaunchBox.Next - Improvement: LaunchBox.Next side bar drop down scroll bar styles have been themed - Improvement: Color themes are now available in LaunchBox.Next I've also made "refresh selected images" threaded so that it doesn't lock up the interface and hopefully fixed the side bar sorting bug (*hopefully*). Let me know how this one fares. Here's a quick screenie of the new LaunchBox.Next NES color theme:

You're the king, @Grila. Nice work here. I'll look into adding custom hotkeys here soon. Game selection within a particular view might be more tricky but I'll look into it.

You can use the sidebar to filter by Rating, and then select None in the list (may have to enable the None option in settings). Then just Ctrl+A to select them all.

We might be able to add an option for that in the future @Rincewind, but the main issue is that there's a difference between a game being "Not Rated" by the ESRB, or the rating just not being specified or unknown in LaunchBox (blank). In the mean time you should be able to batch edit them to be Not Rated.

Based on the video posted, it does look like it is a bug, but it's not something that I've seen before, nor is it something that everyone experiences (or it could be specific to a particular emulator, I'm not sure). Regardless, I will be tackling it soon enough, but it's not what I would consider top priority considering that it's not affecting everyone. Anyways, yes, let's please move on from this topic.

We are using UI technology that was new to Windows Vista at the time it came out (the aero stuff), but it's all supposed to work fine on up through Windows 10 of course. We're not using classic theme functionality, no.

Definitely sounds like an overzealous antivirus. Hard to know without seeing it but I believe I've heard of that exact scenario several times before.

There is a DebugLog setting in the Settings.xml that you can manually enable, but honestly I don't think it's likely to help here. It is possible that Windows 10 1803 (the latest major Windows rollout) has some kind of debilitating glitch with your particular hardware. That would suck, but there are always issues like that occasionally with the Windows updates. I'm not sure if you can still downgrade at this point, but it honestly might be worth a shot. Have you tried any other .NET software on the machine?

Gotcha. I'm guessing there's some kind of strange driver conflict or configuration issue on that machine, unfortunately. The code that is throwing that error hasn't changed in a very long time so I don't think it's anything that we've changed or added recently. I would first try making sure you're 100% up to date on Windows updates and video drivers.

Beta 6 is out now with the implementation of the list view in LaunchBox.Next. Remembering column orders and visibility will be coming in a future beta.

See my post at the top of this page. I'll probably end up adding a way to auto-populate the cache at some point as well.

@Romfrosk That's an odd one. Can you test to make 100% sure that this error does not show up when using LaunchBox instead of LaunchBox.Next? What's odd is that the code there for the import dialog is exactly the same between LaunchBox and LaunchBox.Next.

Thanks @dbalcar. I am able to replicate this on my cab, so a fix is coming.

Okay, I'll just have to implement something similar to the outline method in the original LaunchBox as an option, I guess. I've gotten a lot of negative feedback on that approach over the years, but I guess to each his own. And yes, there will eventually be an option to disable the box coloring.