RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    Input configuration for each console

    Scheduled Pinned Locked Moved Ideas and Development
    controlsinputsconfigurationuser interface
    12 Posts 4 Posters 12.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nemnadogg
      last edited by

      There are countless threads out there about dealing with changing the input configuration for consoles and even specific ROMs. I would say it's the most common issue. There should be an option one can activate so that each console prompts you for an input configuration the first time you use it. Those who would leave the default configuration can just leave this option switched off. It would save so much trouble for configuring generic gamepads, as many buttons may have to be repurposed for different consoles.

      N 1 Reply Last reply Reply Quote 0
      • N
        nemnadogg @nemnadogg
        last edited by

        @nemnadogg in the same way that one can rename a ROM by pressing select over it, one could select a console and configure the input. Console specific input would be great because you would only be asked to map the buttons that the console needs.

        mituM 1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator @nemnadogg
          last edited by

          @nemnadogg You can do per-core (console as you call it) input overrides/configurations in RetroArch gui, just press Select + X while in-game and do your configurations, then select 'Save core overrides`. This way, your input configuration will be applied to all games started for that emulator core.

          Impman66I N 2 Replies Last reply Reply Quote 0
          • Impman66I
            Impman66 @mitu
            last edited by

            @mitu Does this only work if Hotkeys are enabled? As I have pressed Select +X numerous times in different games, in order to do the exact same thing and nothing happens. The Retroarch menu just simple doesn't come up.

            Pi Model or other hardware: Raspberry Pi 3 Model B
            Power Supply used: Generic 5v 2.5A Panasonic
            RetroPie Version Used : 4.5.1
            Built From: Retropie website
            USB Devices connected: 2 x Dragonrise N64 Encoders

            mituM 1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator @Impman66
              last edited by

              @impman66 If you mapped other button as Hotkey, then press Hotkey + X (instead of Select + X) to bring up the RetroArch GUI.

              Impman66I 1 Reply Last reply Reply Quote 0
              • Impman66I
                Impman66 @mitu
                last edited by

                @mitu OK Thanks, I will look into it

                Pi Model or other hardware: Raspberry Pi 3 Model B
                Power Supply used: Generic 5v 2.5A Panasonic
                RetroPie Version Used : 4.5.1
                Built From: Retropie website
                USB Devices connected: 2 x Dragonrise N64 Encoders

                1 Reply Last reply Reply Quote 0
                • N
                  nemnadogg @mitu
                  last edited by

                  @mitu the problem with this is that, because my joypad is generic, the controls get scrambled for each console and I can't even access retroarch. Also configuring the controls within retroarch can be confusing, and doesn't work for non-libreto emulators. I'm suggesting a much more user friendly option.

                  N 1 Reply Last reply Reply Quote 0
                  • N
                    nemnadogg @nemnadogg
                    last edited by

                    @nemnadogg getting into retroarch and manually changing the controls for a console is a huge hassle. It's also confusing. And for the non libreto emulators one has to manually change the files, and that's definitely not friendly to those who don't know much about software. A configuration window, like the one for Emulation Station, is definitely the most intuitive. It asks you where you would like a button configured, and you simply press that button. The point of the retropie project is to come up with a complete, friendly UI for tye smoothest gaming experience. I think this is the best way.

                    1 Reply Last reply Reply Quote 0
                    • dankcushionsD
                      dankcushions Global Moderator
                      last edited by

                      what's a 'generic' joypad in this sense, and why does it need to be separately configured for each system? this seems to be a fairly unique use-case.

                      N 1 Reply Last reply Reply Quote 0
                      • Impman66I
                        Impman66
                        last edited by

                        Now working thanks, just reconfigured input and all hotkey options working ok

                        Pi Model or other hardware: Raspberry Pi 3 Model B
                        Power Supply used: Generic 5v 2.5A Panasonic
                        RetroPie Version Used : 4.5.1
                        Built From: Retropie website
                        USB Devices connected: 2 x Dragonrise N64 Encoders

                        1 Reply Last reply Reply Quote 0
                        • N
                          nemnadogg @dankcushions
                          last edited by

                          @dankcushions In my case it's a retrolink N64 USB controller. I call it a generic joypad because that's how retropie calls it. The controls are weirdly scrambled for every console. Even for the NES, which is supposed to have the same controls as Emulation Station, yet for some reason is different. But this isn't just the case for this controller. I've wanted to change the button configuration that my PS3 controller uses for N64 emulation. But I'm not using one of the libreto emulators, so I'd have to do that in the system files, I believe. And as someone who knows nothing of software, I'm afraid of ruining something. I have friends with the same issue. I way to configure inputs for cores by assigning buttons the way you do for ES would be the perfect solution.

                          dankcushionsD 1 Reply Last reply Reply Quote 0
                          • dankcushionsD
                            dankcushions Global Moderator @nemnadogg
                            last edited by dankcushions

                            @nemnadogg said in Input configuration for each console:

                            @dankcushions In my case it's a retrolink N64 USB controller. I call it a generic joypad because that's how retropie calls it. The controls are weirdly scrambled for every console. Even for the NES, which is supposed to have the same controls as Emulation Station, yet for some reason is different.

                            this is the suggested layout for n64 pads: https://retropie.org.uk/docs/RetroArch-Configuration/#nintendo-64

                            if you bind it to that in initial setup, it will be this layout for all libretro cores, and a number of standalone cores.

                            I've wanted to change the button configuration that my PS3 controller uses for N64 emulation. But I'm not using one of the libreto emulators, so I'd have to do that in the system files, I believe. And as someone who knows nothing of software, I'm afraid of ruining something.

                            again, this all happens automatically. if you bind it during initial setup (https://github.com/retropie/retropie-setup/wiki/First-Installation#configure-controllers) to the PS layout (https://retropie.org.uk/docs/RetroArch-Configuration/#ps1) then it should create the relevent config files for mupen64plus standalone.

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post

                            Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                            Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.