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] 8Bitdo Issue @ game launch

    Scheduled Pinned Locked Moved Help and Support
    8bitdo snes30retroarch
    6 Posts 2 Posters 836 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.
    • L
      Luke_O
      last edited by Luke_O

      So I've been putting together a new Retropie build for a friend and been setting up 2 8Bitdo controllers for him. After working through some connection issues between the controllers and the Pi I got everything to stay connected (and reconnect with no issues) and mapped the controllers. When first trying to test them out I launched a random rom and the system seems to freeze on the retroarch/libretro screen (may be the wrong name). I thought something had frozen so I had to do a hard power down and restarted the system to try again, same thing happened. This time though I shut down the controller first and as soon as the controller disconnected the game launched... I turned the controller back on, it connected with no issues, and I was able to play the game. I went through this process several times, with various games across several different emulators (megadrive, nes, snes, etc.) and the same thing happened, system would freeze with the controller on. It didn't matter how long I waited, as soon as I turn the controlled off the game will launch. Not really sure how to fix this, any suggestions?

      Setup:
      RPI ZeroW
      Retropie v4.4 - Ran all the updates for Retropie and the underlying Debian OS
      8Bitdo SNE30 - updated to Firmware v6.1 - udev rule was setup through config screen.

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

        You shouldn't be needing the udev rule if you're on a recent firmware. It looks like the runcommand is stuck before launching the emulator.
        Can you try disabling the launch menu in runcommand from RetroPie-Setup as explained here and see if you get the same problem ?

        1 Reply Last reply Reply Quote 0
        • L
          Luke_O
          last edited by

          I tried to turn off the launch menu but when launching a game it just get stuck on a blank screen now. Again tried this for various amounts of time and same thing every time, as soon as my controller is turned off the game launches.

          As far as the Udev rule, I thought this was still needed, I thought it was only the 'mapping hack' that wasn't needed on later firmware? Could the udev rule be causing an issue?

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

            @Luke_O said in 8Bitdo Issue @ game launch:

            Could the udev rule be causing an issue?

            I don't think so, but if it works without it, I don't see the point in adding it - it was meant only for certaing firmware versions where the controller wasn't properly detected as a gamepad.

            L 1 Reply Last reply Reply Quote 0
            • L
              Luke_O @mitu
              last edited by

              @mitu either way I went and deleted the udev rule and no change... At this point I'm going g to completely remove the controllers and the config files and run back though the setup process. If doesn't work I'll completely wipe the SD card and redo everything.

              I'll post back with any updates

              1 Reply Last reply Reply Quote 0
              • L
                Luke_O @Luke_O
                last edited by

                I finally got these controllers working after completely wiping my SD card and rewriting the Retropie image. The only difference this time is that when running through the update I didn't update the underlying kernel, only the Retropie packages. The only reason I did this was on the previous setup this caused several issues such as having to log in at power-on. These were easy to fix but I didn't feel like dealing with it.

                1 Reply Last reply Reply Quote 1
                • 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.