![]() ![]() When you have a core open or content running, that should reveal in the main menu a menu that contains all core-specific settings, and ONLY core-specific settings. IMO, the current "Quick Menu" contents should be separated into two menus. It's just kind of a mess of settings from all over the place. My personal pet peeve: the "Quick Menu" is named badly, and contains options across all three scopes - some things (like Rewind) can be accessed there but are Retroarch-scope settings, the core options are also there and only there, and it's also the only place to find shader and controller settings that are stored separately. Once you understand how the various config files are loaded it kind-of makes sense, but the UI does you no favors in helping you figure it out. Even just renaming certain things to make it more apparent how the configuration scopes work and whether you're changing a Retroarch setting, a core option, or an option that's stored separately (like controller mappings or shaders) would be a huge help. It takes time and effort to organize things, and when efforts are more focused on features and compatibility, sometimes the interface takes a back seat for longer than perhaps it should. I think the main answer to your question is the same as it often is for apps that have been around a while - they just keep adding/changing things, throwing them wherever they kind of made sense, but haven't done a UI rewrite in a long time. Also you do realize that it's possible to change both the menu GUI you're using, and some of the options aren't visible until you turn on advanced user settings, so this isn't likely anywhere near all of the options at your disposal, right? A multiple emulator/program front end that makes a lot of things much easier to understand. RetroArch is a front end similar to LaunchBox but started with a different direction in mind, namely always being what it is currently simply expanding on it. This also comes down to what each was made for, since LaunchBox started as a front end for Dos Box, a particular kind of emulator for Dos games, and expanded from there. I've used both LaunchBox and RetroArch, I'd rather have RetroArch because that way I'm able to see exactly what can go wrong instead of wondering what of the multiple settings I screwed up in LaunchBox to cause my problem. The choice is either simple UI with you doing more work behind the scenes, complicated UI that does all the work right in front of you, or all your emulators and various other items separated and requiring you search around for them. You don't want all this overcomplicated UI go with launchbox, but that means you have to setup the emulators and other associations yourself manually. This is because it's not just 'another emulator' it is, as you said, being able to run multiple retro games in a single package. ![]() What any of these things actually do and why.įortunately I discovered the Libretro Docs. To be fair to those yearning for a simpler experience, I had a great deal of difficulty learning:ĭifference between controller inputs on Main Menu vs Remaps on Quick Menu In the end, all I gained in those situations was a prettier interface that took up even more CPU power.Ī positive example of what Libretro has done to make the base UI easier is how they've cleaned up the Core Options page. Or you will go through an even more tedious config text file to assign specific cores to specific systems. Eventually something won't work right and you'll default back to the "labyrinth" behind the new UI to fix those things. Or another party can bury that base UI behind another UI (Emulation Station and others like this.) Only problem is instead of pilfering through the "labyrinth" now you are beholden to stick with stock settings and cores. This removal of customization is often partially implemented by disabling "advanced settings." Lakka does this by default and I find that aggravating until I dig around and cut that back on. Now combine all of the emulators under one roof.) (I have yet to find a stand-alone emulator that worked right without configuring. ![]() The only way to practically simplify the UI (to satisfy the most newcomers) is to take freedom of customization away like Ludo.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |