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

    RetroPie keeps forgetting Bluetooth controller configuration whenever I launch a ROM

    Scheduled Pinned Locked Moved Help and Support
    retropiehelpbluetooth8bitdo nes30
    4 Posts 3 Posters 1.0k 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
      loquacius
      last edited by

      So, I recently set up a new RetroPie console on a Raspberry Pi 3 B (not B+), and got an 8bitdo NES30 Pro controller to go with it. I've successfully paired the controller with the console, and they find each other on startup just fine. After I went through controller configuration again, I can even use the controller to navigate the menu over Bluetooth.

      But whenever I actually launch a game -- any game, for any system -- the Pi apparently loses track of the controller configuration and I can't get any response out of it via the controller. This includes hotkey shortcuts, so I can't even quit the game to get back to the system menu and have to reboot the Pi entirely.

      When the ROM launches, I get an output on the lower-left corner of the screen claiming that the controller is not configured ("100%: 8bitdo NES30 Pro (11720/14368) not configured."), even though I've checked and the config file at /opt/retropie/configs/all/retroarch-joypads/ looks normal as far as I can tell (I've linked it in a Pastebin at the end of this post).

      The same controller works fine to play games on if it's connected via USB; there's only a problem if I'm trying to use Bluetooth. And, again, as soon as I boot up I can navigate the RetroPie menu and pick a game over Bluetooth; the problem only starts when I launch a ROM. Both RetroPie and the 8bitdo firmware are fully up-to-date. None of the guides I've been using seem to indicate that there's anything left I need to do to actually play games wirelessly. What step am I missing? Thanks for any help!

      Pi Model or other hardware: B
      Power Supply used: Gowoops 5V 2.5A Power Supply Adapter Charger
      RetroPie Version Used: 4.4
      Built From: Image linked from https://www.kintaro.co/pages/guides (links to here, image was v4.3 but I upgraded to 4.4 using the standard update script while troubleshooting this; it didn't help)
      USB Devices connected: just a keyboard
      Controller used: 8bitdo NES30 Pro
      Error messages received: "100%: 8bitdo NES30 Pro (11720/14368) not configured."
      Guide used: The one from the Kintaro website, followed by the one from the RetroPie website
      Emulator: All of them I've tried; as an example, my SNES emulator is lr-snes9x2010
      Attachment of config files: /opt/retropie/configs/all/retroarch-joypads/

      1 Reply Last reply Reply Quote 0
      • C
        CaelThunderwing
        last edited by

        try w/o a Pre-modified Image, but i use a 8bitdo NES30 Pro myself, in my main Media/Emulation Pi3b box and all i did as additionally did was setup a udev rule for the controller but i didnt turn on the mapping hack (as my controller's had it's fw updated)

        L 1 Reply Last reply Reply Quote 0
        • EcksE
          Ecks
          last edited by

          Update the firmware in your controller if you have not done so and also as a suggestion to just install RetroPie on a different SD Card and the image from the official site and try it out then and also they are now known as the N30 Pro controllers cause even the official site for the controllers now label them as that and also i use my SN30 Pro controller all the time on my Pi and i never came across this type of problems.

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

            @caelthunderwing @Ecks Man, I really didn't want to have to flatten and reinstall because I'd already put a LOT of roms on this thing, but the Kintaro image appears to have been the problem, yup. Using the base one from the website solved the problem. Time to start moving the roms over again!

            At this point I just have input lag to deal with, but that's a separate issue I'm going to have to look into and make a separate thread for if necessary. Thanks for your help!

            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.