RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    (solved) Upgraded to latest retropie (fresh install), retroarch not functional?

    Scheduled Pinned Locked Moved Help and Support
    retroarch
    5 Posts 3 Posters 658 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.
    • T
      tjsgaming
      last edited by tjsgaming

      Linux veteran, been using retropie for about 2 years.
      Just did a fresh install of the latest retropie off the official image. Had been using, I think, 4.0 or 3.8 before this.

      It seems that the retroarch functionality is no longer working. Once I load a rom, I can no longer hit Select + X to bring up the retroarch menu, nor can I quit a game with Start + Select anymore. I use a wired PS2 controller via a USB adaptor, everything else is working fine, buttons map properly and all that. This is a bit of a show-stopper problem, obviously, and a bit of a let down since the entire reason I'm trying the latest version was to try and get fastforward/rewind working (I kept running into issues trying to save the config after setting it up in my old install, gave up after 16+ hours trying to make it work).

      I can't find any info about this glancing around the forums or with google, has some default changed somewhere?

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

        @tjsgaming Give us more details about your system - https://retropie.org.uk/forum/topic/3/read-this-first.
        You probably have a different Hotkey mapped instead of the Select button, I would advice to remove any controller mappings and re-configure your gamepad again in Emulationstation. During the configuration, don't choose a Hotkey button when asked and then choose the Select button as Hotkey when asked to do so at the end.

        1 Reply Last reply Reply Quote 0
        • T
          tjsgaming
          last edited by

          Yep, ended up being a controller mapping issue.

          If anyone else has this problem or something substantially similar, the eventual steps I had to rectify it was :

          have USB gamepad plugged in and configured and all that

          Unplug it

          ssh into the pi from a PC/terminal/whatever - get a command prompt

          manually delete the gamepad mapping with the rm command, apologies I dont remember what the exact path was

          power down the pi

          plug in USB gamepad

          Power-up the pi, follow the on-screen gamepad setup

          I don't know why, but somehow in the process of remapping my gamepad a couple of times, it seemed to 'forget' the mapping for my 'hotkey' (select button for me) and wouldn't restore it. Something kept removing or perhaps over-writing the setting. Manually deleting the config from the command line solved the problem.

          robertvb83R 1 Reply Last reply Reply Quote 0
          • robertvb83R
            robertvb83 @tjsgaming
            last edited by

            @tjsgaming there is an easier way for this :-)
            just press start in ES and go to input options --> configure input
            it will start the input assistant for your chosen joypad.

            Sorry that this help comes too late for you but maybe it will help others. I know things are often a pain in the a... if you don't know the "right" way to do things... I spent countless hours on such myself

            My full size arcade cabinet Robotron vs. Octolyzer

            1 Reply Last reply Reply Quote 0
            • T
              tjsgaming
              last edited by

              I tried to reconfigure from within retropie, and for some reason the changes weren't holding correctly. I suspect it was probably permissions related, though I'm not sure how the permissions on the .cfg could have gotten messed up.

              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.