Jason Carr

Internet connections are really finicky things, unfortunately, especially now with Internet neutrality abolished in the US (what a ridiculous mess that is). I've already proven that the LaunchBox traffic is being throttled by ISPs, so I wouldn't be surprised if EmuMovies traffic was as well. It sucks to have to pay money for a VPN, but that may be worth trying, as that gets around ISP sniffing and throttling. If only big corporations weren't screwing everybody over...

Yeah, per Neil, the first thing to try is to select all your arcade games, and then right click and Edit. Then select the emulator field to update it. This will make sure that all your arcade games are using that Arcade copy of Retroarch. My guess is that's the likely problem.

That is correct.

It's a very simple solution currenty, which should work well for most users. Currently there's only one save state accessible and it always saves and loads that state. We may come back to it at some point in the future to add extra functionality, but it's not an immediate priority. Unfortunately more extensive solutions will be a major challenge due to all the differences between the emulators. Yes, this is certainly possible, but it is still a challenge, so it's not something I plan to tackle immediately. I'll take note that you guys want this feature expanded though. It may end up on the next community poll.

I know this can be a problem for multi-frontend compatibility. It doesn't come up often but it is on my list to add an option for. Currently there's not really any way to prevent media files from being renamed when renaming games. It shouldn't be an issue though except for in that specific scenario.

Makes sense. I can see that being useful; I'll add it to the list.

Can you explain this? What settings is it unchecking exactly? In LaunchBox or Big Box? Once you create a save state, you'll never run into a situation where a save state doesn't exist again, so it's not much of an issue. Regardless, there's no good way to tap into all emulators to retrieve this information generically, and with some emulators, it would be impossible. It's not nearly as crucial of a feature as you're implying here. You can turn them off on a per-emulator basis. Just edit the emulators. For PC and non-emulator platforms, you can batch edit the games.

I just put out the 9.9 official release. I definitely advise updating sooner rather than later, as I noticed that I did break some startup and pause screen things with the previous beta.

Yeah, that probably has a good chance of fixing the issue. One last question before you do that though; are you running any anti-virus/anti-malware apps?

Oic, duh. Currently there's no way to set up a script to use a different slot unless the emulator has a UI for that.

Probably not. Have you tried installing a completely fresh version of LaunchBox to a brand new folder? I'm fairly lost at this point. I know that 9.8 works perfectly fine on Windows 7 (tested it myself and lots of other users are using it as well).

No problem! Thank you very much. I'm currently in the middle of putting out a bugfix release, so I can't really put it in right away, but I'll put it into the next beta after that.

Okay, so weird. It seems like AutoHotkey scripts are just not detecting windows like they should on your system. Doesn't really make much sense to me. We could spend all year troubleshooting AutoHotkey scripts, but I don't see much benefit to that since we can't really fix AutoHotkey itself anyways. At least we know a script that works. But the problem is, if I remove everything else from the default script, it will break the exit functionality for other emulators that is currently working for other folks out of the box. So I guess for now, we'll just have to go with what we have, and you can change your emulators to use the minimal script that worked.

I see. I believe there should be ways to get all those systems working with actual valid files in LaunchBox (per @neil9000), but I can see that option being useful. I'll add it to my list, but it might be a while before I get to it.

I don't understand his question at the end though: But anyways, you can change the scripts to match different keys of course, but that would be a manual process.

Not fully following you here. Can you re-explain?

Somewhere along in that update process, we did update to the 4.7 version of the .NET framework. That error message suggests that somehow the .NET Framework install is corrupted. So I think what you'll need to do is uninstall the .NET Framework 4.7 and then re-install it.

Beta 2 is out now to attempt to fix an issue with the updated game exit AutoHotkey script. It's only been reported by one user so far, but it's a major issue for @MazJohn [Mr Arcade]. The issue is detailed in this thread: Hopefully this beta fixes it and we can go forward with the 9.9 release.

Just put out beta 2. You can test by resetting to the default exit script for Retroarch. If everything works, I'll go ahead and put out the official.

Alright, well, I'm not exactly sure why forceful activation is required for you, but that's why we added it. All I can figure is that it's somehow related to your system's drivers, or something of that nature. Edit: The only other thing to try (other than updating drivers) would be to try closing any apps you have running in the background. I've seen Remote Desktop sessions of all things cause conflicts before.

Yeah, we've been plagued by users missing that back button for years, unfortunately. It's just how the wizard system we have in place (originally based on Vista) works. It'd be a lot of effort to switch it out.

Hmm, okay. Did you copy and paste it? Maybe the forums messed up the quotes. I'll put a beta to test.

Awesome, okay, that confirms that it's the default AutoHotkey script that's causing the problem. Can you try the below script to see if it fixes it? If so, I can update the default script: SetTitleMatchMode, 2 If WinActive(""DOSBox"") { Send {Ctrl down} Sleep 50 Send {F9 down} Sleep 50 Send {F9 up} Sleep 50 Send {Ctrl up} Exit } If WinActive(""Project64"") { Process, Close, Project64.exe Exit } If WinActive(""redream"") { Send {Alt down} Sleep 50 Send {F4 down} Sleep 50 Send {F4 up} Sleep 50 Send {Alt up} Exit } Send {Escape down} Sleep 50 Send {Escape up} Sleep 500 If WinActive(""LaunchBox"") { Exit } If WinActive(""Fusion"") { Exit } Send {Alt down} Sleep 50 If WinActive(""LaunchBox"") { Exit } If WinActive(""Fusion"") { Exit } Send {F4 down} Sleep 50 If WinActive(""LaunchBox"") { Exit } If WinActive(""Fusion"") { Exit } Send {F4 up} Sleep 50 If WinActive(""LaunchBox"") { Exit } If WinActive(""Fusion"") { Exit } Send {Alt up} Exit

It sounds like the issue is somehow caused by the AutoHotkey script then, which is what I figured. The default AutoHotkey script is this: SetTitleMatchMode, 2 If WinActive(""DOSBox"") { Send {Ctrl down} Sleep 50 Send {F9 down} Sleep 50 Send {F9 up} Sleep 50 Send {Ctrl up} Exit } If WinActive(""Project64"") { Process, Close, Project64.exe Exit } If WinActive(""redream"") { Send {Alt down} Sleep 50 Send {F4 down} Sleep 50 Send {F4 up} Sleep 50 Send {Alt up} Exit } Send {Escape down} Sleep 50 Send {Escape up} Sleep 500 If WinActive(""LaunchBox"") { Exit } If WinActive(""Fusion"") { Exit } Send {Alt down} Sleep 50 Send {F4 down} Sleep 50 Send {F4 up} Sleep 50 Send {Alt up} Exit It seems like something in that script is causing the issue. Try replacing the Retroarch AutoHotkey script with the below: Send {Escape down} Sleep 50 Send {Escape up}

Okay, thanks for that testing. What happens if you use Escape to exit Retroarch instead of controller automation?