8bitdo SNES SFC30 Issues

Floob

Are you turning on your controller with Start+R?

jay81uk

I am yes @Floob

jay81uk

You mentioned a hack earlier... maybe I missed something?

jay81uk

Sorted. Turned the hack off for 8bit controllers. Thank you.

Floob

Check out the video I posted above, that should cover it. But your controller file seems ok, so it shouldnt really make a difference.
That said, I havent tried 2.68, you could try 2.67 and see if it works ok (or flip the hack to off and re-setup the controller).

Floob

@jay81uk Ok, 2.68 must need the hack off, glad you sorted it.

BuZz

Aah new firmware 2016-08-06 - must have brought it in sync with the others.

Does it now connect when the rpi is already booted and the controller is turned on without having to use the hacky "background connect" mode in the bluetooth config ?

my 8bitdo snes30 pro do, so hopefully they will have fixed that for the sfc30 now also.

Floob

I just updated my SFC30 to 2.68 from 2.67.
Tried this in RetroPie 4 RC1. Added the SFC30 to be registered as well as adding the udev rule.

Rebooted.

Both my FC30 Pro and SFC30 pro connected when Emulation Station had already loaded, this is with the "boot" menu selected in the bluetooth menu - as opposed to "background", so that looks good.

However, when I tried to "Configure input" in ES, the FC30Pro seemed largely fine, but the D-Pad and buttons did nothing on the SFC30, ES sees it as a controller but doesnt see the button presses.
I'll check some settings now.

For reference, New 2.68 firmware:
1.Joystick Mode(Hold START button power on) support OSX.
2.Enhanced the stability of the Bluetooth automatic connection.
3.Enhanced the stability of automatic connection with the Retro Receiver NES.
4.Make the LED blink much quicker when the controller is in auto-connect status.

Definitely saw the LED #4 happen when connecting.

BuZz

Sounds like it isn't in Joystick mode. Just flashed and tested on my sfc30.

Still have to power on with start+r for the right mode. Disabled background connect - powered off then on fine and paired automatically. Disabled the hack mode, and reconfigured on ES and all seems well.

Floob

Something very odd went on, not sure what (tried different power up modes, different boot modes, just wouldnt take the input from SFC30).
Just wrote RetroPie 4 final to a card. Chose basic install.

Added controller with hack off, added udev rule, left the boot mode where it was, didnt choose "boot" or "background".
Turned controller off after it registered and connected.
Rebooted.
Waited until fully in ES, turned SFC30 on, connected automatically.
ES happily saw its inputs - wrote the correct values. All power ons were with Start+R here.

All good! :)

Now just trying to work out how I managed to get ES to not see inputs from a SFC30 but see the FC30 Pro....