Jason Carr

Okay, so I only see one purchase from you, which is the $20 purchase you just made @shawn. If you were getting the A5623 error, unfortunately you were using a pirated license. You can fix the issue by just replacing the pirated License.xml file in your LaunchBox folder with the one you just purchased. Let me know if you have any further issues.

Please let me know the exact error message. I have nothing to go by to explain what's happening. I need details, please.

I just sent you the license that you just purchased, via the automated email and also via a personal email message to make sure that you receive it. If you still get an error, please let me know the exact error message and I will get it fixed.

What is the exact error message?

@shawn I'm sorry for the confusion here. I'm not sure how the conversation got here but we will help you solve your problem, and if not, we will get you a refund. I'm not quite sure what's going on, but I'm gonna look this up and get you your license.

My best guess is that this is related to a stray game controller. Try disabling game controllers completely to see if that fixes the issue.

Locking this thread as it really doesn't need any further discussion, and seems to be cause for drama.

For anyone curious, James has unfortunately moved on (he did a while ago). He's doing some sneaking around (amongst other things), and hasn't exactly responded positively in a number of situations, so we've decided that it's best to make it a clean break.

Gotcha, thanks. I really appreciate it. Don't worry about testing 4K. I'm going to put together a test build for you test, if you can, to see if it fixes the issue.

I see; what is your desktop resolution?

What about the change in resolution? Does it happen only when the resolution is changed?

Ah, glad I asked for confirmation, because I misunderstood the first time. So the crash only happens when maximized for you, and minimizing it makes it work again.

Okay, thanks. So you've confirmed that it *only* happens when the resolution is changed? What do you mean by "minimize Next from fullscreen in MAME"?

Calling all beta testers: please let me know if you are experiencing freezes/crashes of any kind with .Next, and where. I've been wracking my brain trying to fix the freezes when launching games as of late, but the problem is that it's so difficult to replicate, and every time I think I have a solution I can't replicate the original issue. It also seems to be machine-specific. Any details anyone has on how to replicate crashes or freezes is appreciated. I also have a test build I can send over to further help if you're interested. Per the crashes when launching games, I do have two additional immediate questions: Does the crash happen when the window is NOT maximized? (resize it to be a small part of the screen) Does the crash only happen when the screen resolution is changed?

I've actually had this fixed for a while, but haven't put out a beta because I'm still trying to resolve the freezing issues. Yeah, agreed. We can come back to this at some point.

@FlightRisk Most likely that's happening because of the uniformity of the boxes, but I do know that that algorithm can use some tweaking. The goal is to get the most prominent color out of the artwork and fade it out to use as the background, but that's often very difficult to do. It can just be turned off for now if it's not working well for you.

Unfortunately reordering the game details is not currently possible.

It's a complicated algorithm. Every image should be providing a color when that setting is on, though some colors are less obvious than others.

The MainForm one will fix it in OG LaunchBox but not in .Next. I'm not sure if the issue exists in .Next as well though.

It should be the Strings file I believe.

@wantwon @RULLUR I'll look into those errors. Both issues above are by design, and will disappear once .Next replaces OG. These options will be coming in some form soon, but not as a priority for the next release.

Is this happening strictly with Windows Media Player as the video playback engine? I know that certain users have stated that it's an issue with Big Box on their systems, but it's been so long since I heard about it that I forgot it was a thing. I think it must be some sort of system-specific issue. That said, I've heard about it quite a bit for .Next, so I'll be looking into it to see what I can do.

I'm guessing this is because you have "Colorize Backgrounds to Match Images" enabled in the .Next options, under Boxes.

This is still on my list to address.

Thank you all for the bug reports/sleuthing. @MadK9, that is especially helpful to know. I think there must be some kind of weird video conflict between .Next and various applications that use video acceleration in some cases, at least that's my guess. I would call it just an MS bug, but obviously it's not an issue with Big Box, so there has to be something causing it. I'm still trying to figure it out. I'm holding off on the next official release until I can get these various bugs solved. They're a challenge because most of them are very difficult to reproduce (if I can reproduce them at all), but I'll get it all worked out. Hopefully we'll see the next official release some time next week.