Jason Carr

I can't replicate that freezing issue with MAME, so I'm guessing maybe there's a MAME setting that's causing it. Can you try testing with a fresh install of MAME with default settings? It has to be either a MAME settings discrepancy or a driver issue.

Thanks, updated. We did have one report of FX2 not working properly with the pause screens, so I've marked that as conflicted.

Yes, a while back we added logic to send additional apps PDFs to the built-in PDF reader. Let me know if that's not working. I think there might be a setting for it in Big Box.

Alright, beta 10 is out now with fixes for the following bugs from beta 9: When disabling forceful pause screen activation on an emulator in Big Box (MAME for example), the pause screen was not always showing and hiding properly After exiting games in Big Box, the game startup screens were not always exiting properly

FYI, hold off on testing. Found a couple bugs. New beta will be out shortly.

Thanks, I'm hoping this is fixed in beta 9.

Hmmmmm...I'm seeing some minor issues with pause screens when startup screens are disabled. So FYI...for folks having issues, that could be the problem. I'll need to address that separately.

Alright, beta 9 is out now with the following: Fix for the game pause keyboard key not updating until restart of LaunchBox New game pause screen setting on emulators for "Suspend Emulator Process While Paused". Previously, this was always happening. Unchecking the box will stop LaunchBox/Big Box from suspending the emulator's process during pause, but then you'll need to use the AutoHotkey script to pause the emulator, or it won't really pause. There may be some emulators that require this, as the suspend process may not work for all of them. New game pause screen setting on emulators for "Forceful Pause Screen Activation". This was previously always happening as well, but I figured out that for MAME, it's a much smoother process if I remove a bunch of the steps to activate the pause screens that some of the other emulators require. At least on my system, unchecking it for MAME results in much faster transitions. Emulator pause screen settings will be reset with this new beta, so you may have to make any customizations again. This of course won't happen after the official release.

Yes, that is the plan.

If you are able to record a quick video of the slow transition, that would probably help me to figure out what's going on. I do get an audio stutter (which I can probably handle just by muting eventually), but it's rather brief. It would help to know the specific error, so please post it here if you get it again. Depending on the emulator, the flashing windows might be something we just have to deal with here. We're treading in new waters and with fullscreen exclusive mode, some things just aren't possible. Full-screen exclusive mode requires some sort of an Alt-Tab in order to switch between the pause screens and the emulator, and there's nothing at all that we can do about that if it's a dirty process because of the way the emulator's built. One thing to look for: make sure that your emulator is using your desktop resolution. Neither the startup screens nor the pause screens will ever work ideally unless you're using the desktop resolution in the emulator.

Not sure if that is performance-related or not. All my testing with MAME has resulted in very quick transitions. Are you running Windows 7 or 10? What are your hardware specs? I'll look into the LaunchBox button issue.

The pause screens are entirely emulator-specific. So I'll need details on what game or emulator it is, first and foremost.

I had to give myself a break from pause screens today. Beta 8 is out now with a new Import Installed GOG Games Wizard. Per the name, it only imports installed GOG games. There's a plugin out that imports games via GOG's API, but it takes a very different approach, importing all a user's games and launching them via GOG Galaxy. So I guess now you get to choose. The new built-in importer takes advantage of the fact that GOG puts "Launch Game Name" Windows shortcuts into the game folder of every game. So you just give it the root folder of your GOG games, and it finds all the shortcut files and imports them. Any additional shortcut files are added as additional apps on the games as well. Previously you could import GOG games via the Windows import, which just found games in the Start menu, but this works a lot better.

Cool, updated.

Unfortunately Malwarebytes has a history of being overzealous. So it's yet another anti-virus program that acts like the boy who cried wolf, and ends up being untrustworthy as a result. My recommendation continues to be just to use the tried and true Windows Defender that comes with Windows, and uninstalling third party virus protection, as most are unnecessary, significantly slow down your system, and cause issues like these.

FYI, pause screens for DOSBox have been fixed for beta 7 (at least for me) with an AutoHotkey script. DOSBox's problem was that it automatically exits fullscreen mode when leaving the window, so I simply added a script to press Alt+Enter to put it back in fullscreen mode on resume. If anyone else can test to ensure it works on their systems as well, I'd appreciate it. It should work both for built-in DOSBox support and if you create a DOSBox emulator. I'm afraid it probably won't work for eXoDOS yet though since it uses batch files. It's also worth noting that this might be the issue for some other emulators, so you could try putting in a script to send key the fullscreen keyboard combination on resume. Let us know if you find something that works.

Awesome, all updated.

Thanks guys; all updated.

Table updated.

Beta 7 is out now with the following: New global pause screen options for disabling or changing the pause theme (separate options for both LaunchBox and Big Box) New option to set a pause key in LaunchBox - Tools > Options > Game Pause New emulator-specific options for enabling as well as custom AutoHotkey scripts for pause and resume - Add/Edit Emulator > Game Pause Screen tab Updated pt-BR and ru-RU translations Fixed: Keyboard automation now ignores zero for key values (was causing weirdness with Xbox controller guide buttons) Fixed: Pause theme folder not being created properly on Big Box startup Fixed: While in Big Box, the shutdown themes were using the LaunchBox startup theme setting instead of the Big Box one Fixed: Rare threading error with hiding mouse cursors Fixed: Possible null reference error while auto-generating child playlists This should get us a lot closer, at least. The custom AutoHotkey scripts should hopefully allow us to start fixing some of the emulator-specific issues. Feel free to experiment, and let me know if anyone solves any of them and gets them working. Also, just a reminder: we're working through emulator coverage over here:

Why do you continue to argue with us? It will work if you actually do what we're telling you to do in order to fix it. You're misunderstanding a number of things, so honestly, I'm doubting that that's what really happened in the past. Regardless, we gave you the solution.

If you add a line to the Retroarch associated platforms that matches the platform name, and set it up to the right core, it will work. If that's not working, put up some screenshots and I'll review.

My guess? It didn't and you're confused. LaunchBox doesn't just forget things, change settings, or stop working out of the blue. I understand that it can feel that way, but if there is an underlying issue, we're never going to find it until you at least understand how to set it up correctly.

It looks like you're missing the NEC TurboGrafx-CD platform from the Associated Platforms list in the Retroarch emulator. That's what's causing it.

Awesome, thanks guys. Updated the table. Trying to get confirmations from three different people for each one before we go ahead and call it official.