Jason Carr

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.

By chance, are you using the key that spins the wheel while pressed? There are two keys for attract mode. One starts attract mode properly, and the other only spins the wheel while the key is pressed.

I actually have this on my to-do list, but unfortunately there's no way currently to show custom fields without building a plugin.

@Xrc6 Thanks for the video explaining things. It's certainly odd, especially since I haven't heard about this being an issue from anyone else. Can you zip up and PM me your LaunchBox\Data folder (in a state where the issue is occurring)? Sorry if you already have; I should be able to walk through the code to figure out what's going on if I can replicate it here on my end with your data.

@Kraken13 As stated above, this is an issue that needs reported to the Cemu developers. It will likely get fixed if enough people report it. See the rest of the thread for details.

I don't currently have plans to add fields and such for new types of documents like game guides (for this release at least), but you'll at least be able to pull up the game's manual. We may also add something that lets you pull up additional documents via additional apps.

This was something I tried to tackle ages ago, but MS made it far more difficult than it should be. I'll add it to my list to revisit.

Alright, this has been a huge headache, but beta 6 is out now and I'm hoping the pause screens are a lot more stable than beta 5. Thus far with this beta I have not seen any issues with MAME, Retroarch, or Dolphin in my testing. Other emulators are still up in the air, however, and I still haven't added any real features outside of just showing and closing the pause screen. Let me know how this beta fares compared to beta 5.

You can turn off gamepad/joystick input under Tools > Options > Input > Gamepad/Joystick in LaunchBox. There's a separate setting in Big Box as well under Controller.

@alissongamer Let me know if you find a bunch of bad data coming in, and I can take a look to see if there's someone being malicious. In the past when I've looked into it, it's never turned out to be malicious, just different people making mistakes. But if you see a string of bad data come through, you can give me some examples and I'll take a look. I do realize that the system could be improved in that regard. Unfortunately it's not high up on my list, but it is on the list.

@Thunder345 Sorry for the non-responses and delays on this. If you can, zip up and PM me your LaunchBox\Data folder, and I'll take a look to see what might be happening.

There's not really a recommended or easy way to do that as it may cause performance issues to load all the counts up at once. They are cached, but not in every single situation. You might need a plugin in order to pull it off.

Thank you all. I'm slowly working through the issues and I'll get a new beta out soon. @Juzzotec I warned everyone in this thread that there might be stability issues. Probably best to not use the betas if that's where you're coming from. They're betas for a reason.

Beta 5 is out now with the very beginnings of the pause screens. At this point it's really just a proof of concept, but simply getting the pause screen showing and hiding properly is the hardest part of this endeavor. Some important notes: The screen that is displayed currently is really just a placeholder that was carried over from the startup screens. I haven't yet put any work into what happens or what is available on the pause screen itself. In Big Box, there are several options for ways to pause and show the pause screens: Options > Keyboard Mappings > Show Pause Screen Options > Keyboard Automation > Show Pause Screen Options > Controller Automation > Show Pause Screen If you bind a key to Show Pause Screen in Keyboard Mappings (without automation), then that key will of course no longer work for anything else while you're in games, so it's recommended not to bind a key that is regularly used. In LaunchBox, currently the only way to show the pause screen is by using controller automation. There's a new option for Show Pause Screen in that section of the Options window. Other methods will be coming for LaunchBox. I've primarily tested with Retroarch and MAME. It seems to work fairly well with both, but I still see an issue or two every once in a while. If you're testing with this beta, be prepared to potentially have to force close things, or even worse, force log out or reboot. Sometimes you won't have a mouse or just get a black screen if things go awry. I am interested in test results for various emulators, so do let me know what emulators are working and what emulators aren't in your setups. Pause screens are proving to be even more difficult than startup and shutdown screens were, but I do believe that we can pull it off.

I know games have music that you can play whenever a game is selected, but I don't think platforms do. We'd have to add a new field to platforms for music and then hook it all up.

I think images are used for the borders, so it would probably be a 2-step process, first to change the border image, and then change the XAML to use it properly. I would first check Unified Refried though to see if RetroHumanoid has already done that.

It would be in the OptionsCheckBoxMenuItemView.xaml file. If you put the CheckBox inside a grid or a panel of some sort, that should stop it from changing the font size.

Per #2, I'm not exactly sure what you mean, but you can easily add web links as additional apps already.

Ah, I see. Try adding a Text property binding like this: <TextBlock Name="Test" Text="{Binding Name}" />