![]() ![]() The simplest is to have a FrontEnd ( LaunchBox, HyperSpin, EmulationStation …) that directly launch your emulator (Retrorarch, Mame, Fba, Fba-Neo …) ![]() Why ? because the configuration is already not very simple, if in addition you add an extra layer, you will quickly get lost and especially spend a lot of time. My opinion, which can be questionable, is to avoid going through this kind of program. Here’s what it can do with and without overlays :Īlmost all emulators have a system of overlays, and when the emulator does not have it is possible to go through external program like RocketLauncher. The screens, at the time, were in a 4/3 format (rather square), now most screens are in 16/9 (rectangular), which leaves a blank space on the sides of the game. Overlays allow to add visual effects to an emulated game, it allows to simulate CRT screens or to add on the sides of the game an image that can be related to the console type, or in relation to the game itself. Otherwise, the text could be shorter than the original while still being more descriptive.Today, I’m going to give you my feedback about the overlays in RetroArch. I am not sure the description needs the technical verbiage "implements frontend keyboard callback functionality" but I left it in to err on the side of conservatism. When set to 'Detect', option will be enabled if current core implements frontend keyboard callback functionality. Here is my 217 character edit (+34 over the current text):ĭisable Retroarch hotkeys for core use when launching or resuming content. The current one is 183 characters:Īlways enable 'Game Focus' mode when launching and resuming content. These options are longer but still understandable at a glance, while suggesting the user has switched control contexts.ģ) The Input menu description. ![]() (keyboard icon) Core using keyboard: Hotkeys disabled I would consider renaming it, like "Keyboard: Core Focus" or "Core keyboard: Game Focus." "Game Focus" is not wrong, but it's vague, easily confused with the important gaming term "Game Mode," and arguably not accurate enough as it impacts the frontend and the core, not individual games. I have a question - Is this specifically focused on cores accessing keyboards? The text in the Input option menu suggests so, so just using the word "keyboard" more would be okay.ġ) The option name. I don't think improving this specific function leads RA down a slippery slope of tedious overwritten descriptions for the mundane, and this seems not super related to the meta-question of how the RA menus should be organized, which I know is still a hot topic. RA's design precludes some of the standard UX approaches to context switching (like tabs). ![]() This is a special case among RA options in that it's a context switch for the user interface. The fair number of upvotes here (thanks!), in my first post to the sub, shows this is still news to many RA users. Before writing the OP, I searched for '"quick menu" disabled retroarch' and the results were less relevant. People complained then that they hadn't had any inkling the feature existed, or felt it wasn't visible enough. The top result is a reddit post from last year. I searched Google for '"Game Focus" Retroarch'. I also want to note my research - as it stands, the option is a missed opportunity for users. I also think the ingame notifications are a close second. tl:dr - the most important one is 3) at the bottom, the menu description. Thanks for explaining things and listening to my views :) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |