Jason Carr

Beta 16 is now out, with some hopeful fixes for various issues. To be honest, some of these bugs have been truly nasty to fix; I'm having nightmares hearkening back to the days of the Big Box VLC stability issues. Anyways, here's what I've changed/fixed for this beta: Added LaunchBox.Next support for "minimize on game launch" and "restore on game exit" options Fixed LaunchBox.Next side bar combo box and search box not sizing properly for custom fonts Added significant debug logging information for .Next window events (to provide better debugging information for freezing issues on some systems) Changed the debug logging to use a timestamp instead of a GUID in the file names (for easier navigation in debug logs) Forcing debug logs to be enabled for all beta versions (see below) Added a missing, thought-to-be-unused DLL reference, which could possibly be causing the stability issues (though that's a shot in the dark) As described above, I've made some minor changes to the debug logging system, as well as force-enabled it for beta versions. This means that a new LaunchBox\Logs folder will show up that logs various debugging information that can help when troubleshooting things like crashes. Each time LaunchBox, Big Box, or .Next are started up, a new file will show up in the LaunchBox\Logs folder with a timestamp on it, so you can easily find the latest file. In the future, if you experience a crash with a beta release, please post your debug log file here in addition to any other error messages that you have. Thanks all, please let me know how this beta fares; specifically, I'm most interested in any crashes that you get.

Unfortunately the issues that I'm working on having nothing to do with having a 4K monitor. I wish it was that easy lol. Great to hear.

Awesome to hear. Very excited about a notifications API thing.

It's not over $20. He got the $20 back. It's over $0.

You do whatever you wish. You've been refunded. Good day.

Your purchase has been refunded. I have not found any other purchases of yours other than the $20 purchase, so I can guarantee you that you have not been charged for any additional purchases.

I'm sorry we couldn't help you. I will refund your $20 purchase. If you did make a purchase earlier, please let me know the email that you used and I will refund that one as well.

I am happy to refund you. Did you use the same email on the first purchase?

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.