Been public knowledge since it was built it was released that it's done so using Xamarin.Forms and is mentioned heavily in the forum and our videos.
So massive that the thread has went over a year without a single person commenting.
Yep, never a reason to use it move on...
I get your frustrations. Always sucks to not be able to use something the way you feel you should be able to. That being said this really isn't a solution to the problem. Thankfully there are a lot of options in the Android eco-system for front ends. If our app doesn't fit your needs you definitely have other options you can try. All of which would be more productive than attempting to scream at the development team here to "git gud"...
Update is already out. You can just check the box to not show the BIOS error in LaunchBox if you don't want LB to warn you about stuff like that. No functionality has changed in this version once you check that box and ignore the feature.
Yeah, I can see that change log being confusing though. Saying accepted despite the fact the change couldn't be applied. I'll let the team know see if they can think up a better way of handling that.
You'd have to alter the theme's XAML file to do what I was referring to. Just so you're aware you CAN press the letter or letters of the game you want to jump to as well. If you know you want to scroll to games starting with "Su" for example you can click on any game in the view then type s-u and it'll jump to the first game starting with that.
1) Sounds plausible that this is the reason for what you're seeing
3) If I had to guess that change may have been accepted but failed to be applied because there is already a game with that name in that platform on the database (found here )
Best way is to just manage it in LaunchBox. Go to Tools > Manage > Platforms. Select the one you want to change artwork for and then press Edit. The gray box on the right is where you media is display, you can drag images to it and then change the image type to the correct one. When finished press OK and LaunchBox will make sure the images are saved correctly. Then when done go to Big Box and reset the cache like you were and they should work.
Typically what you would do is a combination of two things. You'd do as JoeViking suggests and make OBS capture based on window title. You'd then also just set up a few different OBS scenes. When you're transitioning between games switch to a scene that isn't dependent on that window until RetroArch is open, and then switch the scene back.
If on premium you can theme the change to the scrollbar. When you refer to the middle mouse, you mean clicking the middle mouse and scrolling that way, or something else? Wheel already scrolls so I want to make sure I'm understanding the request.
We check install state on startup for certain storefronts using that storefronts files/registry. Would appear that you have a storefront that either doesn't realize that game is installed, or didn't clean up the files properly. I'd try to leave LaunchBox closed and then open and close that storefront launcher and see if that sets the files/registry entries correctly.
I have LaunchBox on my Odin 1 Pro. Not checked what Android versions it's on though. I don't see any reason it wouldn't though. You can install the app for free to verify.
Tools > Manage Emulators. Select RetroArch and press Edit. In the window that opens pressed the "Associated Platforms" tab. Remove the "-f" part of the command line of every platform you have in there. This switch is what is telling RetroArch to open full screen regardless of your settings.
If you have games in your epic library that hosted from other storefronts like EA and Ubisoft I believe those won't show in the EGS import but should in the parent store importer.
If it only happens when LaunchBox is opened the controller binding to check would be "Close Active Window". You can also look at your running AHK scripts. Those are typically the two things that would close a process from our app.