Jason Carr

If you try navigation with axes on a wheel for a while, you'll find that it's really annoying and you don't really want that (or at least that was my experience). Which is why the wheels come with D-Pads for directional navigation.

Hey all, LaunchBox for Android 1.6-beta-2 is out today with a shiny new Themes Manager, just like the desktop apps. Let me know how testing goes.

That's not known to be any different than what we use in our tests either. I've tested internal storage just the same. So I'm really not sure what the difference would be. You could try creating a new folder in the root of your internal storage instead, just in case that is the issue and permissions got screwed up somehow. But other than that, I really don't know why it wouldn't be working, unfortunately.

@Browser Hound First off, you will save yourself some grief if you uninstall your version of RetroArch that is from the Play Store, and install the sideloaded version instead. This is because Google's overbearing policies for apps on the Play Store often break a lot of the cores, so the best RetroArch experience is only available when sideloading. You might find missing cores that way too. There is not a guide, but if you're confused, honestly the best thing to do is just to download all cores for a system inside of a RetroArch. That's pretty easy and avoids any confusion.

Welp, I've been testing on a Samsung Galaxy Tab S8, so no, Samsung shouldn't be the issue. My ROMs are on an SD card and everything works properly. Where are your ROMs located?

@Arne Let us know if Neil's response solves this issue for you.

@SiobonkeyKong I just upgraded to the latest version and tested this and everything is working fine. However, you may need to start AetherSX2 manually and let it re-parse your ROM files after updating. The latest versions of both LaunchBox and AetherSX2 should be working fine if you use the built-in AetherSX2 emulator option. What device are you using?

To be honest, stuff like this is so far out in left field and so full of false information that it really is just spreading misinformation. The fact that we exist, are growing tremendously, and have such a large base of users is proof that the majority of this is false. We just hired another developer, and we are now 4.5 strong (4 full-time and one part-time). Most of this stuff I've already addressed, but I will reiterate some of it. We would love to be on Linux, but it's not feasible as of right now because the technology that exists is very far behind on Linux. Big Box is a huge success partially because of the theming engine, which is highly customized, but it's based on WPF and XAML. Without that theming engine, Big Box as we know it would not exist, and we would have to throw away all existing themes. Obviously, that's a very, very bad idea. To code something like WPF is way outside of the scope of what a 3-developer team can accomplish in any decent amount of time, and there is literally nothing on Linux that even comes close to competing with WPF in terms of development ability and performance. It doesn't exist. The closest thing that I've found is indeed Xamarin.Forms/MAUI, and that is the course of action that we plan to take in the future. Unfortunately though, both Xamarin.Forms and MAUI are very immature thus far on Linux, and our attempts to port them were not fruitful thus far. But I do believe that eventually we will be able to go that route. Regardless, the notion that Microsoft is deprecating, or planning to deprecate WPF any time soon, is false, and would be a very stupid move for Microsoft. We have found so much success because we have two (now three) full-time developers working on the project, so we can meet the community's needs very well, and much better than the open source projects out there. They don't have the bandwidth to build what we can build, because we have full-time staff doing it, which is enabled, of course, by the fact that Big Box is a paid product.

FYI, we are actually planning to work on some more social features regarding high scores.

FYI guys, I have a slightly better solution. Was looking to add my own Teknoparrot games tonight. The above settings will allow you to use the profile files like ROM files, and will no longer require you to manually override the startup parameters for each game, or use text files, or any of those hacks (note the changed Default Command-Line Parameters field). The only remaining issue that I'm running into is the fact that Teknoparrot won't read the Escape key to exit from anything other than the keyboard, so we can't use AutoHotkey scripts to exit it with button combos.

Yeah, it won't be the easiest thing to catch on to quickly. Unfortunately I can't walk you through the XAML though, especially since I didn't even write the theme, so that would be a ton of work.

No, actually, not at all. In that scenario it would be rather important to have completely separate/copied setups. I suppose you *could* use the same media files, but you're probably still asking for trouble if you're making any modifications. So I would recommend just leaving the duplication then. Not sure anything else will really work well.

You might need to modify your network share permissions/group policies to allow executing apps from the network share.

For what it's worth, did you know you can you have two different LaunchBox installations on the same machine without virtualization? I'm just not sure why you would want to do that in the first place. But you would set it up the same way you would set up any network share (but explaining how to do that is probably outside the scope of these forums and I'm sure there's a million walkthroughs for that online). The only custom step would be just changing the paths for your media files, which is done under Tools > Manage Platforms. Alternatively, you could keep the entire LaunchBox folder, including the app, on the network share.

Thanks Claudio; no worries. I have this in for the next beta, and we plan to put out a bugfix release in about a week or so anyways.

@DanCue You can do that, but it's not recommended for performance reasons. Generally, you can keep your game files (ROMs) on the network and that should work fine. However, it's a bad idea for performance to keep your media files over the network. A better idea is to use FreeFileSync to simply sync/copy the files between machines while LaunchBox is closed.

Just to conclude this thread:

Thanks to the support of this entire community, we have grown again! We've added @Flynner to our team as our third developer. For the time being he'll be working on our games database, forums, and main LaunchBox websites; it's great to begin tackling some much-needed improvements on our websites, and we're looking forward to being able to improve the experience for everyone. In the future, he'll also be focusing on mobile/Android development, and possibly some Windows development as well. Let's all welcome @Flynner to the team, and many thanks to the entire community for so much support and enabling us to grow once again.

@moudrost Thanks. We're still testing and working on some fixes. I'll let you know when we have something worth revisiting.

Thanks guys; I have these translations in for the official release.

Yes, if you're using emulation, then the changes won't apply.

If the application path starts with steam://, then yes, we completely disable the shutdown screen. Shutdown screens never worked properly in this scenario, for any games, at least as far as we are aware. However, if you use a script in that application path field, then those games should not be affected or changed.

It's finally that time again guys; we're looking to put out the official 12.15 release on Monday, so it's time to get the translations in for the 12.15 release. Thanks y'all as always. @Offone @Kondorito @Cauptain @Nyny77 @Opak @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock @Soomin papa

Apologies, I forgot to get this updated for beta 6. I do have it in for the next beta, however.

Beta 6 is out now with the following: Fixed: Popups were not always playing the Select and Back sounds (introduced in 12.14) Improvement: The shutdown screen has been disabled for Steam games, which generally results in a smoother experience