C-Beats

As stated in my announcement. Our hands are tied and until RetroAchievements gets their API back up there isn't much we can do to restore functionality. They've made progress and updated their website with changes required for the upcoming API fixes but they have not announced an ETA on when they expect the API will be back up.

I just updated Omni to 1.3 which adds the notification system introduced in 13.6 Beta 3. PLEASE NOTE: This version requires you be on LaunchBox v13.6 Beta 3 or newer to work! @Jakatsu This version does NOT address the bugs you've found. I have confirmed they exist but haven't gotten them corrected yet. I do plan to address them before 1.4.

For any theme developers wanting to get the notification center (the new notification bell icon/button) to your themes you simply need to copy lines 312-400 of Default's MainView to your theme and then tweak to your liking. Let us know if you're having too much problems trying to integrate it into your themes.

np @KingSlayer420. Wasn't insinuating you were attempting to mislead or anything. The shaders do make things look far better, just comes at a cost. For me the startup thing is noticeable but not the end of the world. Still starts up faster than any AAA title, but if you don't have the GPU to keep frames at 60+ not sure they worth it.

I personally use HSM bezels on my PC and enjoy them quite a bit. Though I feel it should be said that HSM shaders (unless a recent update improved them) have a SIGNIFICANT performance impact and WILL cause the first time RetroArch starts to take considerably longer. The shaders also hit your graphics card FAR harder than most shaders. You won't get a much better visual experience than the stuff HSM is putting out, but you definitely need more juice behind them to get them to work than other shaders.

We have a few known issues affect stability in some themes that we are actively looking to improve. I don't believe any fix will make it into 13.6 for them. Right now Default theme should be stable, but some of the issues do still affect other themes. What theme are you running that is failing that quickly?

Yeah, those options have their own view file. I'll have to see which it is, but it's the views that start with the word "Options". Each type of menu item has it's own file. Just not entirely sure what one is driving those two options.

Does Windows play the disconnect sound when that happens? Sounds like there is something weird going on with the monitor but I'm not entirely sure how best to troubleshoot that. I've never seen anything like this reported. Only suggestions I have right now is just the standard stuff: Check video drivers, open command prompt as admin and run "sfc /scannow" (without quotes) and see if the system repair fixes anything. Also if you don't already can install/repair your Direct X (I believe WPF will default too 12 if you have it).

I edited the post to help with it. In most browsers you can paste plain text by pressing CTRL+SHIFT+V to help eliminate this issue.

Does it happen with every theme or just that one? I don't believe I've seen that issue before.

Enter Platform Category sidebar filter and then navigate to your Arcade platform and right click it. Should be an option in that context menu to create the MAME playlists.

On the sidebar of LaunchBox enter either Platform Category or Playlist sidebar filter. Then in the values that appear right click on any and go to Add > New Playlist. In there name the playlist what you want and then go to Auto-Populate. Then check auto-populate and in the fields set up the playlist to look like so: Platform - Is Equal To - Arcade Favorite - Is True Then go to the parents tab and parent the playlist wherever you want (this is to place the playlist in the position you want in Platform Category view) and press OK to save.

I'd try the image pack importer first and see if correctly matches the images for you. If it does it'll automatically change the file name to the one LaunchBox uses and it'll just work

Thanks for the bug reports. I'll take a look into it and see why it isn't working and what I can do to correct.

If you purchased the old Android app via the Play Store in the past you can reach out to support@unbrokensoftware.com about it and they can get you a license for the new app. If you didn't you can purchase a license for Android here.

When you press Add in Armoury Crate you can press LB/RB to get file explorer to open and then manually navigate to what you want to add. If you're adding LB/BB to crate I'd suggest you add the executables in the \\LaunchBox\Core and not the ones in \\LaunchBox

Are you asking how to add LB to Armoury Crate UI, or Armoury Crate to LB?

I just uploaded version 1.2 of Omni. This version adds 2 more game details layouts that change automatically as the size of the details panel increases. This brings the number of possible layouts to 12 in the theme. As with most settings in the theme if you want to tweak where the layouts change you can do so in the ThemeValues file. If you change a value in the file with LaunchBox open you will probably need to restart LaunchBox for all the settings to take hold. I've updated the screenshots on the theme to reflect most of the various layouts. PLEASE NOTE: This version requires 13.6 Beta 1 or newer to work!

LaunchBox can utilize any application that can run your files via command line. Yuzu included. You just have to point LB to it and put in the command line it expects. For Yuzu it's just adding the "-f -g" (without quotes) to the command line parameters

My theme Omni also has a link to it in Game Details if you were looking to do it that way.

For any application that reads if an EXE is open and in focus to load profiles you will want to point to the executables that are in the \\LaunchBox\Core folder, not the ones in the parent \\LaunchBox folder. Those are just redirects that open the ones in the core folder that are there to help with backwards compatability.

@KawaiiKuroki I'd check your LB/BB settings and make sure you don't have "Close Active Window" set to Button 7 + Button 8. If so that could be the cause. I believe RetroArch has something similar built into their hotkey menu but I'm not as well versed in how to get there.

Most control related issue's I've seen reported is by people using "auto" control mode instead of "gamepad". If pushing B is closing RetroArch you are almost certainly in desktop controls which will cause issues like what you're describing.

It's so the platform has a default value that can be applied to games so you don't HAVE to manually go to each one and assign an emulator after an import and just play the game. It also drives the logic for the "Play With..." menu's that let you choose which emulator you want to play the ROM with if you have more than one emulator that can play a given system.