Jason Carr

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:

Messy starts are already hidden properly in most cases. We've discussed this stuff to the moon and back, and as long as you allow for fullscreen exclusive mode, it's entirely impossible to overlay things exactly like Rocket Launcher, so that is not planned (Rocket Launcher just makes sure that nothing runs in fullscreen exclusive mode, which is a performance issue). If you can figure out how to reproduce it, I can look into it. Unfortunately I need more of a lead in order to figure out what happened.

Per the home button, I'm guessing you have some other kind of automation thing that is causing keypresses or something of that nature. There are a bunch of ways to bind the pause screens. Trying unbinding all of them (see the original post). I suspect that the Dolphin issue is somehow related to that as well. I'll try to test with SSF.

Ah, good to know. Just an oversight on my part; should be easy to fix.

For Cemu and Yuzu, were they working properly in previous versions? Most likely it's just a setting issue somewhere, but I haven't specifically tested those two emulators. Try playing with the emulator startup screen settings in LaunchBox. Per MAME, I'll do some more testing, but I'm guessing it's a setting issue of some sort. Can you try a new copy of MAME with default settings to see if it's your MAME settings? We'll have to identify the difference somehow in order to get it fixed.

That's interesting. Probably a fluke, but good to know. Clicking Ignore in the setup process is pretty much guaranteed to result in a broken LaunchBox, so it is wise to make sure that it can continue with LaunchBox closed.

It's likely your settings if you're having issues with the startup screens with the latest beta. None of the startup screen stuff has been changed. Project64 is known to work fine with the startup screens, so that's not something I'm tackling currently. I just tested this to confirm and I'm not having any issues. I may not be fully understanding though. If I set LaunchBox and Big Box to both use the same startup theme, the startup screens are working just fine for me. What am I missing? Honestly I didn't even know this was an issue. No, I don't think that will be a fix for anything, but can you explain the issue in more detail? What games is it happening on?

@Thunder345 I took a look at your data and figured out the issue, though I'm not sure how it managed to get like this to begin with. Somehow your Parents.xml file got messed up with a bunch of playlists that don't have any parents specified, but are still in the Parents list. The easiest way to fix it is just to delete your LaunchBox\Data\Parents.xml file. You'll lose the platform/playlist parent structure, but that was already messed up and it should be relatively easy to re-define the parents how you want (there's only a handful of platforms and playlists so it should go quickly). If you're able to get it to mess up again, let me know. That way I can fix it so it can't happen again. I doubt it's a common issue though because I've never seen this before.