![]() You can see your buttons and their corresponding values in either quick menu's controls section or the global settings controls section. So the above config shows I have the turbo default button set to "0" which refers to my B button (the in-game fire button in this example), and my dedicated turbo button set to "5" which refers to my R button. I tweak the turbo fire settings per game as needed, especially the turbo period setting. The input_player1_turbo_btn is how we tell RetroArch what the dedicated turbo button will be. Regardless of their configurability through the UI itself, game override configuration files fortunately allow for custom per game/per core control over RetroArch's many options. These are the default settings of Turbo Fire, with the exception of turbo mode being set to "2", corresponding with the Single Button (Hold) setting, and the inclusion of the input_player1_turbo_btn setting-this is the secret right here. After, I'll exit back to the desktop, navigate to the config folder, for me retroarch/config//, open the newly created cfg file, and manually add in the following lines: input_turbo_period = "6" First, I'll create a game override configuration file, typically by setting up runahead within a game I'm going to play. ![]() Instead, I take a more hands on approach. To avoid this, I actually never configure the turbo button under the global settings. RetroArch's turbo fire feature is going to frequently run into these button conflicts that will have you playing around in the settings to get things working how you want. For instance, what if in one game you want button B for the turbo default button, and the R button as the dedicated turbo button, but in a different game the R button has its own function. That is to say, RetroArch is aware enough to understand a user will want unique turbo fire settings on a per game/per core basis, but fails to recognize a user may also want to configure their dedicated turbo button on a per game/per core basis as well. There's a glaring omission in this feature though: while RetroArch's quick menu settings know to accommodate for which button you would like turbo fired, it frustratingly restrains the user to their globally assigned turbo button, at least from the user interface (more on this later). ![]() This turbo button will then be used to rapidfire the "turbo default button" set within a game's quick menu > controls > turbo fire settings. The way RetroArch's turbo feature currently works is, first a turbo button must be configured under settings > input > port 1 controls. The turbo feature has always been a weakpoint within RetroArch, and while recent improvements to it have made it considerably better, it is still far from perfect. So as it turns out, setting up a turbo button isn't as intuitive as one would expect.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |