C-Beats

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.

Sounds like something that would best be asked in the eXoDOS discord server

You can delete one in Tools > Manage > Emulators. If you remove the one that was default you'll need to set default to the one you didn't remove though.

Would greatly depend on how you imported it. Full set wizard has a LOT of options in it and most remove games for one reason or the other.

It's a reference to Caliburn.Micro which is a library we use for to help facilitate a MVVM workflow inside of LaunchBox. If you search for "cal:" (without quotes) in that same file you'll see everything that is referencing it in that view. Typically it's used to make an element call a function in the code that standard WPF can't do just in XAML files.

Older version used .NET Framework and an older version of Direct X (9 I believe) that probably didn't send the signals FreeSync uses to determine what the app's "refresh rate" is to make the determination. FreeSync being on for an app like WPF that only actually refreshes the GPU buffer when there is a UI change (opposed to a game that does it as fast as possible regardless if there was any changes) could cause some weird issues like what you were seeing potentially. I've not really ran the software to know of all it's weird quirks and how to get around them.

Thanks for this. May be onto something with the startup/pause processes still running. I'll see if I can use that to attempt to replicate the issue.

Theming documentation is located in \\LaunchBox\Themes\Documentation.pdf

Worth noting that this feature is ENABLED for new installs of LaunchBox by default, but if you are upgrading an existing build of LaunchBox to this version this is DISABLED by default.

Not sure if the post was changed in your edit, or I simply misread. I didn't see you ask about changing the main theme without changing the platform theme. I'd have to look but I believe if you change the theme via the Theme Manager ("Manage Themes" system view option) instead of inside the options menu a prompt appears asking if you want to apply it just as the main theme or to all the platforms as well. If you haven't you could try that and see if it does as you're asking. As I get time this week I'll try to test some things and see if I can get a decent work flow found for you.

Only report issue I've heard recently about this being an issue is with the ROG Ally when armory crate takes focus after a game or emulator closes. Are you running into this one a non-Ally device? Is there a game or application that seems to cause the issue the most?

You can browse our database online to look for some of the games you are hoping to find and see how it fares.

There's an option in Big Box Sound options to change "Attract Mode Navigation Sound Volume". That option affects the move up/down and select sounds that play while in Attract Mode.

What games are you not seeing using the import? I believe the EA games may not appear.

I've locked it.