Jason Carr

That would certainly be easiest.

1. This is by design, as it helps to find the mouse faster after playing games. It feels awkward to me to have to wait until the shutdown screen is closed to find the mouse cursor and start using it. 2. Both use game fanart as backgrounds. It falls back to platform fanart if there is no game fanart. Can be easily changed by modifying the theme if necessary. 3. Ah, I'll look into this. It might be a glitch. 4. Currently there is no way to speed up or slow down the fades. I'll see if that's a common request and add that to the list if so. Not really following what you're trying to do with launching MAME. There's always a way to do something like that, but it won't be easy. You'd probably have to use a third-party program. AutoHotkey should be able to do it, but I don't know when or where you want to do it. Timing the playback, I'm not sure. There are ways to use timers with animations, but I'm not sure if you can hook them up to MediaElement.

There are only four variables available: %romfile% - What it spits out depends on the emulator settings. By default, it spits out the full path to the ROM file including quotes, as it should. If "don't use quotes" is checked, then it won't use quotes. If "use file name only without file extension or folder path" is checked, then it will do exactly that. The only reason this was added was to support odd emulators that don't allow you to put the ROM file last. If it's omitted, the ROM file will always be put at the end of the command-line parameters. %platform% - Spits out the game's platform (was originally added for Rocket Launcher). %launchboxorbigboxexepath% - Spits out the full path to LaunchBox.exe or BigBox.exe, depending on which is running (was originally added for Rocket Launcher). %gameid% - Spits out the game's ID from the XML data (this was added for a plugin of some sort, but not sure when or why). Custom fields are not currently supported, nor are any other fields.

Beta 13 is out now with the following: Pause screens now fade (with an option to disable in the global LaunchBox or Big Box Game Pause options) Pause screens now mute audio during transitions (with an option to disable in the global LaunchBox or Big Box Game Pause options) Added an exit game option to pause screens Fixed save and load states and reset game pause screen functionality for MAME (new default scripts and forced keyboardprovider dinput) Fixed Retroarch game reset AutoHotkey script using incorrect default key Added default pause screen settings for Steem, Hatari, and ePSXe (no scripts yet though) Here's what's left on my hopeful to-do list before the official release (note that they are not at all guaranteed): Game-specific pause screen settings Improved emulator compatibility Additional emulator AutoHotkey scripts for save and load game states and reset game Add retro achievements to pause screens Add disc swapping to pause screens Save PDF browsing location for next time Add themes manager for pause themes Not sure if all of those will be possible, but that's what I'm shooting for. Thanks all; let me know how this beta fares.

I see. I'd need to better understand the whole bezel project in order to answer this, I guess. Of course the XML files are all freely accessible by external programs. But I haven't studied this stuff, so I really don't know what would be required.

I agree that it would be a good thing to have. It just comes down to priorities and time, as usual. So it will hopefully happen eventually, but not before the official release.

I'm honestly not following there, though I'm pretty out of the loop in this thread. Can you explain?

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.