Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • johnnygossamer
    Participant
    Post count: 11

    Well the NES30 should still work fine connected with its USB cable, right?

    johnnygossamer
    Participant
    Post count: 11

    [quote=104327]

    I seem to have bluez installed, but I cannot install bluez-utils.

    Looks like my usefulness has been exhausted with yourself then :S In fairness I’m only running RetroPie by itself so yeah it might be some conflict there.

    Yes, I did it today. At the step where we need to make the controller a trusted device it returns the error you can see in the picture below (sorry I didn’t know how to copy the text from Putty).

    It might be because you tried to set up the controller with a different method, leading to a conflict? If it were me I would start over with a new image.

    [/quote]

    Perhaps. I am getting sort of tired of flashing new clean installs of Retropie over and over, though. Thinking of maybe setting the whole thing aside for a time (a long time) until proper Bluetooth functionality is built in.

    johnnygossamer
    Participant
    Post count: 11

    [quote=104242]Did you go through the Adafruit tutorial that I suggested?

    [/quote]

    Yes, I did it today. At the step where we need to make the controller a trusted device it returns the error you can see in the picture below (sorry I didn’t know how to copy the text from Putty).

    [attachment file=”putty does not exist.jpg”]

    johnnygossamer
    Participant
    Post count: 11

    [quote=104225]So you’re at the same place as me then? Let me know if you solve it!

    [/quote]

    Nope. I don’t even get as far as you. See above.

    Also, if I forge ahead to the step where I’m supposed to enter

    cd /opt/retropie/emulators/retroarch/configs

    I get

    -bash: cd: /opt/retropie/emulators/retroarch/configs: No such file or directory

    …and my controller, while it was connected with a solid blue light before, has now turned itself off, and does not reconnect when I turn it back on again by holding Start.

    Like I said, the guide by NinjaJoey, while detailed, does not appear to match up with what goes on in the stable 3.0 release of Retropie.

    johnnygossamer
    Participant
    Post count: 11

    [quote=104220]Is it not KeyboardDisplay you search for as opposed to DisplayKeyboard?

    [/quote]

    Yep, that was my mistake. Still run into a problem at the stage of actually configuring the controller though (see edited post above, sorry I edited while you were replying).

    johnnygossamer
    Participant
    Post count: 11

    [quote=104182]I think your solution is found in the setup guide for the NES30 controllers:
    http://forum.8bitdo.com/thread-328-1-1.html

    I had the same problem, till I followed the setup to the letter. You need to configure the controller twice. Once for the dpad first, then a second time for the remaining keys.

    <quote>
    reboot your raspberry pi

    While loading hold start on your controller to turn it back on

    your blue light should go solid when you get into emulation station

    it should ask to setup a controller. ( if not use the a usb keyboard hit enter to open the options and config controller)

    Hold down on the Dpad (it should say keyboard)

    Only set UP, DOWN, LEFT, RIGHT

    Skip A, B, START, SELECT, LEFT BUMPER, RIGHT BUMPER

    then hit ok

    Now reopen the controller config and hold A (should say 8Bitdo NES30 GamePad)

    skip UP,DOWN, LEFT, RIGHT ( you should be able to use your down arrow on your Dpad to skip them)

    Set A, B, START, SELECT, LEFT BUMPER, RIGHT BUMPER

    then hit ok and you should have a working controller.
    </quote>

    [/quote]

    Yes, this is the same guide I said I tried in the first post of the thread.

    I decided to try it again but once again, that guide appears to be somewhat out of date. 317 in RetroPie setup is no longer “Register RetroArchController.” It’s “Install RetroArch Joypad Autoconfigs.” I did that and it scrolls through a long list of what appears to be config files for various different gamepads and then drops me back to the setup menu.

    johnnygossamer
    Participant
    Post count: 11

    Bunglenutter,

    I’ll take any advice I can get, getting the controllers to reliably connected via Bluetooth is more progress than I’ve made so far.

    Does the issue you run into prevent you from successfully binding all of the controller inputs and playing?

    johnnygossamer
    Participant
    Post count: 11

    I think I might repost this in the controller forum and see if it attracts more notice there.

    johnnygossamer
    Participant
    Post count: 11

    I already tried PiAssist, sadly. And I made the “DisplayYesNo” change in the bluez-simple-agent file since it’s recommended in the other tutorial by NinjaJoey.

    What asturnauta is describing where ES will recognize buttons but not the D-pad sounds like what happens to me when I get the controller connected in Keyboard mode. If I get it connected as a gamepad, ES recognizes the D-pad and nothing else… quite a fun choice! And now it’s stopped connecting at all. It was autoconnecting if I turned on the controller during the Retropie boot, but not anymore. I could use the console to make it connect again probably but my goal here is to never have to use the console for this again once setup is complete, just pick up and play.

Viewing 9 posts - 1 through 9 (of 9 total)