Jason Carr

After doing a bunch of testing, I've noticed that certain running background apps can interfere and cause issues like this. For example, on my system, for whatever reason if I have an RDP session (Remote Desktop) open, it will cause similar issues. Unfortunately I don't think there's anything I can do about that, because it seems to be either a Windows or a driver glitch. So I would suggest trying to close background apps to see if you can identify the issue. Unfortunately there's only so much I can do to get around those types of issues, so that kind of stuff I may not be able to solve. The pause screens work consistently well on the five machines I'm testing on, so long as the background environment is clean.

If you want to use the keyboard automation, you should remove it from the standard keyboard bindings and only use the keyboard automation settings.

Yes, that is correct. Keyboard automation works the same as controller automation, and requires the hold key pressed before the pause key will work. If you simply bind a key to the pause key, it will always work with just that key (while games are running).

Yes, I added the Arcade.xml file and also changed the Default.xml file to use different images. Box3DOrNormalImagePath attempts to grab a 3D box, and if not found, grabs a normal box front.

Yeah, I don't know of a solution to using Rocket Launcher with startup or pause screens. Guess it's a good thing we've been going around saying it's not supported. Lol, but really, I don't recommend trying to mix Rocket Launcher and LaunchBox startup/pause screens. It's mostly unnecessary and completely haphazard.

The Rocket Launcher way (making everything windowed) is still way more complicated and extremely finicky. I'm very glad we took the fullscreen exclusive mode approach. It's more performant and allows for a mostly generic approach, whereas Rocket Launcher's approach absolutely requires custom code and custom scripts for every single emulator, and they require changes more often. At least with this approach, unknown emulators have a good chance of working, even if I never code anything for them. It's a no brainer in my opinion. The one thing we can't do with this method is bezels for emulators that don't support them. But with Retroarch continually getting support for more and more cores, I don't see that as much of an issue, and I don't foresee us adding that any time soon.

Ah, I see what you mean. Yeah, I can see that being useful. Not sure it will make it in for this release though. We're honestly nowhere near it. Ultimately, it wouldn't be that hard to do, but nothing we've done so far is significant progress in that direction. There haven't been any changes that I'm aware of that should affect command-line parameters like that, at least not since the 9.7 official release.

Beta 14 is out now with the following: Pause screens default theme updated to show controls information images from EmuMovies for the Arcade platform and cart images for non-arcade Retro achievements added to pause screens Additional apps that use web URLs, JPGs, PNGs, or GIFs now show up and work on the pause screens as well Back key now exits pause screens, same as selecting Resume Game Added load and save states and reset game scripts for Sega Model 2 Emulator (will need to reset to default scripts in the emulator settings to use them) Updated the built-in Chromium web browser to the latest Updated Brazilian Portuguese and Simplified Chinese translations

Not currently.

It's probably because your Retroarch emulator is missing scripts for those. Check Edit Emulator and make sure that all the scripts are populated.

Hmm, pretty sure it's unrelated to removing the theme folder, but I'll look out for that fluke I guess. There is an AutoHotkey script option for resume, which I believe is what you're looking for (the same as pause exit). So that should already be there. If anyone gets a script together that works for RPCS3, let me know. I can add it in as a default. Honestly, that's such a complicated scenario that I have no idea. Pause screens are incredibly complicated and involved, so it would take major effort to figure that out. And with Rocket Launcher's screens competing with LaunchBox's, it's going to be a mess any way you look at it. For the moment, that's not an option. There is a menu key on the keyboard (to the left of Ctrl) that acts as a right-click.

I just tested for this and can't seem to replicate. All the options are showing up for me, even with startup screens off. I tried disabling the startup screens both via the emulator and the global setting, but neither seem to be making any difference. Can you re-test and provide further details?

Thank you guys. I have the zh-CHS and pt-BR translations in for the next beta release.

Unfortunately we'll have the same issues with BAT files, or anything that is not opened with the Chrome viewer. So that's a negative.

Thank you guys, I'll get the table updated. @bundangdon Can you list out what settings you're using for those emulators? Forceful on or off? It would help if you could test with both.

Unfortunately I think opening up a separate application is likely to screw with the pause screens and startup screens, so I won't be adding those options for this release. PDFs will always use the built-in reader on the pause screens. It's using the Chrome web engine to display them, so we could support any type of document supported by Chrome, but unfortunately things like EXEs are not going to work.

I'll see if we can display those images in the default theme. Either way, it's easy to modify a theme to show those arcade panel images. Per the PDFs locking up, that's a new one that I haven't experienced or heard of. Has anyone else experienced lockups while viewing PDFs? What platform were those games on?

Not a bad idea. I'll look to see if that's easy to pull off.

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?