Retroarch menu opens with SELECT-Button

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

possible that the emulator doesn't even react to the new controller settings if even the configs were manually deleted?

The input settings hard-coded in your retroarch.cfg's were probably overriding the gamepad autoconfigs.

And why do I have to reinstall everything right away?

It's just the easiest way to restore your default config. If you've got one in the folder called retroarch.cfg.rp-dist (it's created automatically in certain situations), you can just rename that to remove the .rp-dist instead of doing a full reinstall.

If it's so easy to break your entire Retropie system just by trawling through the settings, then these settings or updates should also be removed from Retroarch right away.

Just don't save anything (except remaps and shader profiles) from the RGUI, and don't set it to auto-save on exit. Use the menu to test out new settings all you want, but once you find ones you like, use the configuration editor to make them permanent.

Do your updates through the RetroPie-Setup script, not from within RetroArch.

PARALAX

@sleve_mcdichael

I've tried several times but just can't get it the way I want it to be. Whoever came up with this, it's the biggest crap on earth! The operation is incomprehensible, completely uncomfortable and does not do what it is supposed to do at all. When I used emulators - and I've been using them for two decades - you could set everything via the respective menus and it worked then. Here with Retropie NOTHING works! I go into the Retroarch configuration and set my home button as a "hotkey" button. I launch "Donkey Kong Country" on the SNES - no response when pressing the button. Only ESC works. I go into Retroarch's menu with ECS, try to set the button again. The menu says: "10 (N/A), (Key: escape)" - it still doesn't work. No matter what I do.

And why the hell should I configure my controller, set the hotkey, save states, etc. via a script or the keyboard outside of the emulator in the respective game? There is an absolute lack of logic and understanding.

And to be clear: I tried both configurations. On the one hand via the Retropie menu (via Retroarch), as well as via the loaded ROM within the emulator. Neither works! I only get the default keys. I'm not going to uninstall and install Retroarch again, nor mess with any configs that just don't do what I want.

Sorry, but in my eyes, Retropie has completely failed here. And I think that I'll probably watch "Lakka" instead or ask around in the retroarch community what's going on. How you can offer such a hyper complicated program for free download is simply a mystery to me.

windg

I have F310 and F710, and i never had a similar issue.
Are you sure you have an original Logitech F310? Controller on the back it's a small a switch, this must be to X position.

Also, if you press the ESC button and the Retroarch menu open that means that the retroarch.cfg file is broken. This can create a lot of issue's.

PARALAX

The joypad is definitely original F310, especially since I bought it from Amazon. In addition, the home button is recognized both in the Retropie configuration manager and in Retroarch itself (as "button 10"). The problem, however, is that Retroarch partou refuses to assign this button as a menu button, even though it is in the configuration In addition, the assignment of the joypad keys only works after I have assigned them again through Retroarch in the joypad settings. In the meantime I have found an alternative to this, because apparently you can also use the menu with other key combinations such as R3+L3 However, this is apparently a Retroarch bug. The worst thing for me is the standard assignment of the Select key. In many games like "Donkey Kong Country" this is used by the game itself at the same time, in the above-mentioned case to change the character So, willy-nilly, I'll have to do all the settings through Retroarch's joypad settings, but in the end I prefer it that way , as long as it finally works, even if I have to do it separately for each emulator.

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

The problem, however, is that Retroarch partou refuses to assign this button as a menu button, even though it is in the configuration

Did you delete all your corrupted retroarch.cfg files and (by reinstalling or otherwise) restore the default RetroPie configs?

PARALAX

@sleve_mcdichael said in Retroarch menu opens with SELECT-Button:

Did you delete all your corrupted retroarch.cfg files and (by reinstalling or otherwise) restore the default RetroPie configs?

Yes, I delete all the retroarch.cfg files in /opt/retropie/configs/all and /opt/retropie/configs/snes. After this I re-configured the pad from the Retropie-Menu with the same effect. So I'm forced to open the menu with another hotkey configuration. The main thing now is that the Select button no longer opens the menu. However, I am not really satisfied with the solution.

Here is my current config file with all relevant settings: https://www.mediafire.com/file/p30e41s0eyximl2/config.zip/file

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

Here is my current config file with all relevant settings: https://www.mediafire.com/file/p30e41s0eyximl2/config.zip/file

configs/all/retroarch/config/snes9x_libretro.cfg still has a config_save_on_exit = "true" in it which is fouling up everything else.

How did you install RetroPie? What image did you use?

PARALAX

@sleve_mcdichael

I only re-install Retroarch from the installation script, not the whole Retropie-Image and I don't intend to do that, as I already installed and set up too many other things there, e.g. the pixel browser, as well as all the other stuff. If the makers aren't able to offer a stable system, so that you have to do everything from scratch on a regular basis, that's a very bad omen. Before I start all over again here, I would rather look around for an alternative.

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

I only re-install Retroarch from the installation script, not the whole Retropie-Image and I don't intend to do that,

I'm not saying that you have to re-install the image (though sometimes, it is the easiest and most direct way to get where you need to be), I am just asking how you've done so in the first place.

What hardware are you on, and how did you install RetroPie? If you used a pre-configured SD image, what was the filename of that image?

If the makers aren't able to offer a stable system, so that you have to do everything from scratch on a regular basis,

You don't, usually. Your configs are still bad. Or they're bad again, I don't know; one way or another, the most recent ones you've uploaded are not good either.

I suspect that config_save_on_exit has infiltrated its way into and corrupted several, perhaps all, of your individual system configs, and if you don't catch and correct every last one of them, it's going to get back into your global config and start all over again.

config_save_on_exit should not be enabled, and is not enabled by default. This is nonstandard behavior, caused by something unique to your particular configuration. How did you install RetroPie, and if you used a pre-configured SD image, what was the filename of that image?

PARALAX

@sleve_mcdichael said in Retroarch menu opens with SELECT-Button:

How did you install RetroPie, and if you used a pre-configured SD image, what was the filename of that image?

I installed Retropie directly from the image provided on the website, the version for the Raspberry Pi4/400. https://retropie.org.uk/download/

I copied the image directly to the SD card using the Raspberry Imager and then set everything up accordingly.

@sleve_mcdichael said in Retroarch menu opens with SELECT-Button:

What hardware are you on, and how did you install RetroPie? If you used a pre-configured SD image, what was the filename of that image?

I used "retropie-buster-4.8-rpi4_400.img.gz" for my Pi 4b (8 GB Version).

@sleve_mcdichael said in Retroarch menu opens with SELECT-Button:

config_save_on_exit should not be enabled, and is not enabled by default. This is nonstandard behavior, caused by something unique to your particular configuration.

I've since re-enabled it to make anything work at all, since the only way to disable the SELECT button was to reconfigure the controller buttons via the Retroarchive menu. I can deactivate this option again in Retroarch, but I don't see any point in doing so, since I also want to make a few settings like "Video Filter", for which Retropie doesn't offer me any options at all. So how else should I make such settings if, on the one hand, the controller assignment is not adopted and, on the other hand, important options are missing?

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

So how else should I make such settings if, on the one hand, the controller assignment is not adopted and, on the other hand, important options are missing?

https://github.com/libretro/RetroArch/blob/5e258eb8f09ff05f1f0ea7a5447656769cf0b7ae/retroarch.cfg#L243-L244

PARALAX

@sleve_mcdichael

So enter the whole stuff by hand. Serious? Sorry, but that's not an option for me, especially since I sometimes have to make other settings depending on the system/emulator. In addition, I don't want to have the same controller assignment for every system. I looked again at the configuration files and the only one that has the setting config_save_on_exit = "true is the snes9x_libretro.cfg in the opt/retropie/configs/all/retroarch/config directory, but not in opt/ retropie/configs/all/, i.e. the superordinate directories. Why there are several configurations of this kind is a mystery to me.

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

So enter the whole stuff by hand. Serious?

No, just the individual line or lines that you want to change. The rest of it is already there in the default config. Unless you keep clobbering it.

I sometimes have to make other settings depending on the system/emulator.

That's why there are the different config files. Settings common to all cores and systems go in all/retroarch.cfg. Those unique to a particular system in [system_name]/retroarch.cfg. Those unique to a particular ROM go in ~/RetroPie/roms/[system_name]/[rom_name.ext].cfg.

In all cases you should only change or add the lines that you want to change from default or previously-defined settings.

In addition, I don't want to have the same controller assignment for every system.

This is one of the very few (two?) things you can and should save through the RGUI menu. Quick menu > controls > port {n} controls < controls > save {game | core} remap file.

I looked again at the configuration files and the only one that has the setting config_save_on_exit = "true is the snes9x_libretro.cfg in the opt/retropie/configs/all/retroarch/config directory

That file shouldn't even exist.

Why there are several configurations of this kind is a mystery to me.

So you can have different settings for each system. Games launched from the menu are ultimately passed to command-line with an option that sets the [system]/retroarch.cfg as the config path; each individual system config then in turn applies the global settings from all/retroarch.cfg through the use of:

#include "/opt/retropie/configs/all/retroarch.cfg"

Gamepad controls are not defined in either of these files, so that the autoconfig profiles instead may be dynamically applied at runtime for the gamepad you are using. Otherwise, you would have to reconfigure each time you switched out your controller.

All of this is thrown right out the window the moment you save configuration through the RGUI menu. Current values for all 3,000+ RA settings are written to a custom config that either replaces or supersedes (depending on how you saved) the default config in configs/[system], removing the #include line and the core or system becomes "disconnected" from the global hierarchy of configs, existing in its own little bubble.

PARALAX

@sleve_mcdichael

Thank you for the detailed explanation! It wouldn't be a problem if Retroarch adopted the changes made in the menu when you exited, which unfortunately isn't the case. It doesn't matter whether I make joypad or video filter settings, I always have to make the settings via "Main Menu > Configuration File > Save Configuration File".

sleve_mcdichael

@PARALAX said in Retroarch menu opens with SELECT-Button:

It doesn't matter whether I make joypad or video filter settings, I always have to make the settings via "Main Menu > Configuration File > Save Configuration File".

Right, settings changed through the RGUI menu are never permanent. (Unless you manually save a configuration, which you shouldn't do for the reasons outlined above. Find the setting you like, then paste that line or lines into your global or system retroarch.cfg file, instead.)

It wouldn't be a problem if Retroarch adopted the changes made in the menu when you exited, which unfortunately isn't the case.

That's what config_save_on_exit does but you don't want to do that either, for the same reason.

dankcushions

retropie is a way of centralising various emulator configurations, so when you start configuring them directly, the centralisation falls down and retropie is out of the loop, and you're now the 'retropie' in this situation, trying to unpick an existing configuration heirarchy and bend it to your will. to use this approach you'd be better off not using retropie at all, and manually installing the emulators in raspbian.

it should rarely be necessary to hack files directly, though. there's the configuration editor which allows settings to be edited for one or all libretro emulators, without breaking the config hierarchy.

@PARALAX said in Retroarch menu opens with SELECT-Button:

since I also want to make a few settings like "Video Filter", for which Retropie doesn't offer me any options at all.

if by 'video filter' you mean shaders, there are documented instructions for this here: https://retropie.org.uk/docs/Configuration-Editor/

PARALAX

Unfortunately, due to various issues, I'm still forced to use Retroarch's local configuration save option. This starts, among other things, on in the PlayStation emulation. Although the BIOS files are in the correct folder on the external USB stick, they are simply not found and I always get the corresponding message from Retroarch that they are missing. Only after I explicitly specified the BIOS folder under Settings > Directories does everything work as expected. However, now I have the problem that Retroarch always starts my controller with the "Dualshock" profile, even though I set it to "Standard" before saving. Can anyone tell me the reason for this and how I can fix it? The settings should actually be in opt/retropie/configs/psx/retroarch.cfg, but I just can't find the relevant line.

Otherwise, I have found that Retroarch takes over the controller assignments of most systems as they are usually assigned and that the retroarch.cfg files saved in the respective system only contain the changes that I have made that deviate from the Retropie config. With a few exceptions, this doesn't seem to be a big problem, so that you can actually use it and recommend it, at least from my point of view.

dankcushions

@PARALAX yeah, we can't really support you if you're using your own configuration - eg the "correct" BIOS folder for retropie is so because retropie's config heirarchy sets it - if you make your own config it will be whatever you set/retroarch defaults to.