Jason Carr

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.

Per Big Box, the reason why nothing is displaying is that you have playlists as your startup view, and you have the box to hide auto-generated playlists checked under Options > Views, so there are no playlists to display.

If you have any way to record a video of what's happening, that might help. As of yet I'm stumped because I've just never seen that happen before. Hmmm, actually...I have a guess at least. Maybe you have something on your system (either a keyboard or a game controller, or a virtual version of one) that is sending key or button presses, which would interrupt attract mode. I would suggest trying to unplug all game controllers and any additional input devices other than your mouse and keyboard to see if that helps. Also try stopping any other running programs.

Thank you guys; I've updated the table with everyone's testing results. Actually it means whether or not LaunchBox has the emulator pre-configured via the drop down list in Add/Edit Emulator. I'd rather keep this more simple; I'm not looking to create an end-all list of emulators, though I'm sure it could be adapted in another thread. Startup settings can vary based on the emulator's configuration, so while there are usually good default settings, they're not always guaranteed. We do have some conflicting feedback on the Cemu startup screens; I've had at least one person tell me that they weren't working. It was probably a settings issue though I'm guessing. Can anyone else test Cemu?

Thank you Retro. Per Model 3, do you mean Supermodel? Did you test the startup screens for those as well?

In beta testing is fine. Not the new thread I created.

I've create a big list of emulators that we can use to test against for the startup and pause screens here: I'd appreciate y'all's help to confirm what is and isn't working there.

@wallmachine Startup and shutdown screens work fine in beta 6, sans for the issue with the wrong shutdown theme being used, which I've fixed for the next beta. If you're still having issues with it, we should put that discussion into another thread.

The aim of this thread is to test and confirm/fix coverage for the LaunchBox and Big Box startup and pause screens, as well as detail good, working AutoHotkey scripts. I've replaced the table that used to be here with a Google Sheets document: https://docs.google.com/spreadsheets/d/1wuGiwg8I5QqulDncQvGBZP83BVDSXpbSOzdYqDrsCxI/edit?usp=sharing The above document contains compatibility details on all known emulators, and known working scripts for many of them. There are two sheets in the document, so be aware that you can navigate between them via the tabs on the bottom. Please let us know if: You're aware that an emulator in the document no longer works properly on modern versions of Windows (so we can remove it from this list) You're aware that an emulator has been completely obsoleted (so we can remove it from this list) You're aware of a missing emulator (so we can add it) You've tested and confirmed an emulator broken or working for startup and/or pause screens You have working scripts to add to the document We have moderators who have access to editing the document, so please post in this thread if you have something to add, and we'll get it updated.

Yes, hopefully it will still be useful, thanks.

I'm glad you mentioned this. It's pretty unexpected and I haven't figured out why, but the guide button on the Xbox One controllers are indeed causing it. So I'm on it.

Alright, well then it's not a visible key that causes a key stroke at least. There's probably some kind of keypress happening, but it's going to be difficult to debug it without having the controller. Do you have any controller mapping applications running or anything of that nature? Anyone else using a PS4 controller? Can you test this?

We've confirmed that it's keyboard automation that's doing it, right? Only happens when you enable keyboard automation. So that pretty much proves that for some reason, the home button on that controller is sending a key press of some sort. No idea why, but that appears to be the case. What happens when you open Notepad, focus it, and then press the Home button? Anything?

Hmm, well, if you enable keyboard automation but don't set the buttons, they will all be zero by default. So maybe that button is bound to zero? I guess that shouldn't really be a legitimate situation. We should probably just disable it if nothing is bound for the hold key.

It shouldn't make any difference whether you use a split or merged set. The new MAME importer doesn't even look at the files for this reason. It just knows "here's what the full set looks like, and here's all the games". This is assuming that you are using new the MAME importer, and not the ROM/file importer.

This stuff is confirmed working and hasn't changed in a long time. So if there is an issue, it would be obscure and we'll need details on everything.

Good to hear. Yeah, if you happen to figure out what setting it is that's causing the issue, let me know. That way I can test with it to see if it's possible to fix it for that scenario.

Thank you guys; I have these translations in for beta 7 (should be out soon).

It could be an issue with Project64's settings, or an issue with the LaunchBox emulator settings, or even a crappy driver. The startup screen settings should look something like this: