Jason Carr

Okay, good to know. Can you try putting that script in that I suggested?

Alright, I looked into this a little deeper. For beta 16, we added support for custom exit AutoHotkey scripts, so my best guess is that it's somehow related to that. Let's just test with Retroarch, since I do a lot of testing with it myself and I know it works on all my machines. If you edit the Retroarch emulator in LaunchBox, what do you have in the Exit AutoHotkey Script tab? Does it match mine? If so, try emptying it and adding a single line like this: Sleep 50 That will basically do nothing, but force it not to execute the default AutoHotkey script, so that should at least let us know if we're on the right track as to the problem. Thanks.

@MazJohn [Mr Arcade] Been waiting to put out the official 9.9 release, hoping we can figure this out and get it fixed. If you're around, let me know what emulators you're seeing this problem with.

It's the mame.ini file that contains your MAME settings, so that would be the file the back up and then delete.

I think this was originally done to fix a performance issue, though I agree that it's not ideal. I'll put it on the list. I see; is there a reason why Rocket Launcher would work properly with missing files? Sadly, that would be a mess to implement because every emulator of course implements save states differently. The best option would be to add (yet again) more AutoHotkey scripts for that, and they would end up being too complicated in most cases for people to come up with the scripts. We could take a guess whether a save state "worked" or not, but that would be iffy at best. Hehehe, not usually. I'm all good over here (actually didn't really work at all over the weekend). A lot of it was done late last week. Thanks all; I'm currently taking a couple of days to work on Music Box Alpha, which has metadata/tag editing just about done. Assuming this beta continues to go smoothly, we'll probably put out the official in the next day or two.

The first 9.9 beta is out:

Hey all, the first 9.9 beta is out with the following: Improvement: Launch With in LaunchBox is now in alphabetical order Improvement: Download metadata and media update media verbiage is now more clear Fixed: Several minor one-off/rare VLC errors Fixed: Rare music-related null reference exceptions Fixed: Pause Themes Manager in Big Box was not working correctly to apply new pause themes My plan is to put out a bugfix release here shortly. There's really nothing all that glaring, sans for the pause themes manager thing, which basically breaks the pause themes manager, so I figure it'd be best to get that fixed sooner rather than later. Let me know how this beta fares.

Ideally, if Retroarch launches successfully in 5 seconds, then you would set that startup screen time to 5 seconds instead of 20. That is a known issue, but if the emulator is properly configured, it really shouldn't be much of an issue. Regardless, I'll take a look at some point here to see if there's a way to handle that.

Alright, I'm still fairly lost here, I will admit. Unfortunately this situation somehow seems to be a one-off; I haven't had any other reports of similar issues, so figuring this one out is going to be difficult. That pretty much throws my previous suspicions out of the water. It shouldn't really be related to this at all. I guess you never know though. They're used in different scenarios, and it is assumed that if you set one up that you won't use the same buttons for the other. I suppose it could be related if you had bound them to the same buttons, but otherwise, I doubt that it has anything to do with the issue. What emulators are you using that you've noticed the issue with?

It's not really a matter of if your drivers are up to date and in order; every driver is different and some have miniscule little bugs that can cause issues like this. If you want to look at MAME settings, I would suggest backing up your settings and reverting to the default settings, as those are what are known to be working properly with the pause screens.

Happened in and around this code, so I made the change for the next beta.

Okay, thanks. Good to know.

Does it solve the issue permanently or does it come back?

This can be difficult to figure out, unfortunately. It's either related to a glitch with one of your system's drivers, or it could be a MAME setting somewhere. Regardless, that's one reason why that option is available. Does everything work properly with forceful activation enabled?

It'll be revisited when we believe there's something that we can add that generates significant interest. I'm thinking we should probably at least add scores though.

Okay, the strange thing about that log is that Big Box seems to be running through its exit process when the game is ending, which unless that's what you're telling it to do, isn't right. I think the errors are coming from the fact that Big Box is exiting while the game is exiting at the same time. Just a shot in the dark, what key do you have bound to Exit in Big Box? I wonder if that's the issue.

The monkey beat me to it.

Yes, we've spoken to them here on the forums. If they do end up coming forward with a way to implement live notifications, we'll implement it.

Okay, I looked into it deeper and the only additional thing I've found is that it could be because you need to install/repair both the 32-bit and 64-bit versions of the Visual C++ Redistributable. Other than that, I'm lost on this I think.

Gotcha. What version of MAME are you running? Do you have the "-keyboardprovider dinput" command-line parameters in the MAME emulator settings in LaunchBox? Per #3, all makes sense. Most likely there's something problematic with video drivers or something of that nature, and switching the renderer fixes it. It might be worth trying to update your video drivers to see if that helps as well.

Hopefully this is more clear now:

Are you on the 9.8 update then? Or still on 9.7?

Looking deeper, that error message looks to be a symptom and not the culprit. It's trying to exit LaunchBox\Big Box while the game shuts down, which probably means that there was a previous crash caused by the startup screens, which I still think is likely related to video drivers (we've seen similar things several times before). However, it may help to enable logging in the LaunchBox settings and provide me with the log.

It is somehow system specific, but it may be hard to figure out how, unfortunately. It's good to know that it's being caused by the startup screens though. Most likely, there's a driver glitch somewhere (maybe video drivers?) that is causing it. Can you look to see if there are any upgrades available for your video drivers?

At some point I have to stop spending time responding to things like this so that I can focus on development. I just ran a test to prove 100% that yes, it does download missing box front images even if you already have a different box front image in your collection for that game. I just tested with 8 Eyes for NES and it downloaded the missing box front image, despite the fact that I already had a different one in my collection. If you're testing and it's not downloading an image you're expecting it to download, it could be because of your region priority settings. I can see where your misunderstanding is coming from, but that's not a typo... "missing media" simply means just that, missing media, not "empty image categories in your collection". I understand that it could be phrased better though.