Jason Carr

Is it possible that one of those buttons is bound to the menu in MAME? I'm guessing that's what's going on.

@sundogak That is tremendously helpful; thank you. I'll get the list updated, and I can use your details on the forceful setting to help with defaults in the app.

Is there a reason you're looking for a separate AutoHotkey script? I was thinking just using the same code we have in place for controller and keyboard automation exiting.

Pretty sure if people just wanted to exit...they would exit. But I can probably put that in. Just suggesting that it's the main feature people want is pretty far off lol.

@DOS76 pointed out that if you change MAME's keyboardprovider setting to dinput in the MAME.ini file, then AutoHotkey will be able to send key presses to MAME, so that's a win. You can also send that setting from the command-line, so unless anyone knows of any good reason not to, I'll probably force that setting to dinput so that the AutoHotkey stuff works, and that will solve it for MAME.

Beta 12 is out now with the following: Pause screens now have a menu You can now view manuals from pause screen menus You can now view additional application PDFs from pause screen menus You can now save and load states from pause screen menus (for correctly configured emulators only) You can now reset games from pause screen menus (for correctly configured emulators only) Hopeful fix for a keyboard automation culture issue where certain keys were causing errors Per the new saving and loading states and resetting games features, they require emulator-specific AutoHotkey scripts for them to work properly. I have added working scripts for Retroarch, Project64, and Dolphin, and they all seem to work great. However, unfortunately MAME is being a nightmare because of it's odd refusal to accept any virtual key presses, so MAME does not yet support save states or game resets. Rocket Launcher apparently gets around this issue by using LUA scripts, which is a scripting/plugin interface of sorts for MAME, so we may have to do the same in order to get MAME working. Per other emulators, generally, all that is needed is to figure out the keyboard shortcuts for saving and loading states and resetting games, and then mimic the existing scripts using the new keyboard shortcuts. It should be relatively easy to set up for other emulators. If you do get other emulators working, please let us know here and I can include new default scripts for them. At this point, other than bugs, emulator compatibility, and stuff like that, I'm looking at pause screens as functionally complete. I have a few plans in my head for ways to clean them up a bit (such as strategically muting audio), but for the emulators that are working, I'd say it's where I was hoping it would be. Let me know if you have any additional features that you want to see in the pause screens; I can't make any promises of course, but I will consider them before release.

You'd be on your own tweaking the XAML to do it, but it's certainly possible.

I still haven't played with GameLoader RH, but I'll give it a shot at some point before the official release.

We can add that eventually, but I have to stick with pause screens for now.

This looks to be a culture issue of some sort. I believe I've fixed it for the next beta.

@cyanjiang I'm noticing that the Simplified Chinese language code changed from zh-CHS to zh-CN. I'm planning to rename the files back to *.zh-CHS.resx, as otherwise we'd have two different Simplified Chinese translations. Is there a reason for the language code change?

Yay! Welcome back, and thanks for your work. I have these both in for the next beta.

Yeah, this would be a good addition. I could be wrong, but I'm pretty sure it's been on a poll before and just didn't get enough votes. I'll put it on the next poll.

Controller Automation actually sends different keys depending on the emulator/game that is focused, but in most cases it just sends Escape. If it's DOSBox, it will send Ctrl+F9, since that's the key combo that DOSBox requires. Also, if after pressing Escape the emulator has not closed, it will try Alt+F4. Basically, if the emulator isn't recognized (which is what will happen with GameLoader), it will send Escape, wait half a second, check if LaunchBox is focused, and if not then send Alt+F4. Regardless, I know there are some stubborn applications (MAME, for example), that refuse to accept the virtual keypresses that we send. For some reason they will only accept hardware key presses, so maybe that's what's going on? In the future I'm sure we can expand it, but it'll probably be a while yet.

I haven't experienced any lockups with Dolphin, and we've had quite a few reports of it working without issues. Same with Retroarch. Sadly I'm wondering if maybe it's bad drivers on your end, or something of that nature. Are you running Windows 7 or 10?

What's happening? What do you need help with?

If you read the instructions in the wizard, it tells you how to get an API key. Your email will not work. What do you need help with? What's the issue?

It makes just as much sense to fix titles if they're updated as it does any other field. So we'd have to add granular options for each and every field if we wanted the option to keep one, like title, when choosing replace. Regardless, what might make sense to do instead (eventually) is to use the Japanese alternate title from the database if it matches, instead of the default name. I'll add that to my list.

Great, updated. Yeah, forceful activation enabled does seem to be the best bet, and it's the default for unknown emulators. It's best to try it that way first, and if it doesn't work (locks up the emulator or something like that), try turning it off.

I just marked Sega Model 2 Emulator, Project64, and VisualBoyAdvance-M as fully working in the table, as they all work great now with the new option to disable forceful activation. Going forward, when reporting testing results, if you can report whether you're using forceful activation or not, that would be helpful. Thanks guys.

Thanks much, all updated. Per PPSSPP, we probably just need to add an AutoHotkey script on resume to call whatever key combination puts the emulator back into fullscreen mode. Also, I've already had two reports that RPCS3 is working properly with the pause screens, so try playing with the settings a bit to see if you can get it working, and let me know if you can. I've marked it as Conflicted Reports in the table in the mean time.

Beta 11 is out now with minor emulator compatibility/default settings updates. I figured out that a lot of the emulators that were previously not working with the pause screens now work great if you uncheck the "Forceful Activation" setting in the emulator pause screen options. So I think we're getting pretty close to ready to go with the pause screen showing and hiding functionality. Next week I can focus on game-specific pause screen settings and actually make the pause screens useful. I'm marking Project 64, Sega Model 2 Emulator, and VisualBoyAdvance-M as fully working with this release. We can really use some more help testing various emulators in the Emulator Coverage thread here: Going forward, if an emulator isn't working with the pause screens, please try unchecking/checking the "Forceful Automation" box in the emulator pause screen settings, and let us know which setting you're using when you report an emulator as working or broken. Thanks all.

Whoops. So I added it in, but forgot to add it to the interface itself. Fixed that for the next beta.

@wallmachine If you check Japan in your region priorities as the third one, does it still rename the Japanese games on import? The generally recommended way is to leave the Combine Games with Matching Titles box checked, which would then put the Japanese version in as an additional app, so that's the reason why it's working the way it is, I guess. I can see how that could be improved though if you don't want to combine your games. Per the update wizard, it makes sense that the replace option would rename the title, but I would hope that the don't overwrite option does not. So I suppose that's one way that should work to do what you want to do; just import without searching for metadata, and then run the update wizard and tell it not to replace.

Awesome, updated.