8bitdo SNES30 Bluethooth Input Issues

pimpmaul69

@mediamogul said in 8bitdo SNES30 Bluethooth Input Issues:

@pimpmaul69 said in 8bitdo SNES30 Bluethooth Input Issues:

there is a hashtag and a space right before the word add. not sure why the forum is removing it
# Add the ID_INPUT_JOYSTICK attribute to the device so SDL picks up on it

SUBSYSTEM=="input", ATTRS{name}=="8Bitdo NES30 GamePad Joystick", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"
Markup nuances can be frustrating. Here's a link that might be of help in future postings:

http://commonmark.org/help/

Sometimes the 4 spaces doesnt work for me. Not sure why? I think i got it working this time.

yoink

@pimpmaul69 Yes I added the file using the setup utility.

mediamogul

@pimpmaul69

Both the 'Blockquote' and 'Inline code' specifics are referenced in the link I posted. I believe you were intending to post 'Inline code'.

Edit: You got it. Score one for the good guys.

pimpmaul69

@yoink said in 8bitdo SNES30 Bluethooth Input Issues:

@pimpmaul69 Yes I added the file using the setup utility.

and you held down the right trigger before and while powering on the controller? that is the mode it has to be synced in and booted in. i got the nes30 working on the 1.69 just fine this way. i believe the 2.68 is the equivelant version. if you are just powering on only, that mode does not work and gives a keyboard only input on the pi.

yoink

@pimpmaul69 Yes I used the Start + R method. I followed the instructions in this post:

http://www.austinjmorlan.com/2016/04/8bitdo-snes30-retropie-36.html

Which recommended the 2.68 Beta firmware.

theroamer

You need to edit the config file here: /opt/retropie/configs/all/retroarch-joypads/
for the nes30pro it's called 8BitdoNES30ProJoystick.cfg for yours it will prob say snes 30. You need to change the numbers to correspond to your controllers numbers. You can get this info by running:

jstest /dev/input/js0

and test each button for the number.

yoink

@theroamer So I finally got the SNES30 controllers to work. The key was to downgrade the firmware to stable 2.67. Afterwards, I removed them from RetroPie, repaired them and then setup the controllers via ES and now everything works.

Here's a copy of the config:

input_device = "8Bitdo SNES30 GamePad Joystick"
input_driver = "udev"
input_l_btn = "17"
input_load_state_btn = "17"
input_start_btn = "22"
input_exit_emulator_btn = "22"
input_up_axis = "-1"
input_a_btn = "11"
input_b_btn = "12"
input_reset_btn = "12"
input_down_axis = "+1"
input_r_btn = "18"
input_save_state_btn = "18"
input_right_axis = "+0"
input_state_slot_increase_axis = "+0"
input_x_btn = "14"
input_menu_toggle_btn = "14"
input_select_btn = "21"
input_enable_hotkey_btn = "21"
input_y_btn = "15"
input_left_axis = "-0"
input_state_slot_decrease_axis = "-0"

Abstract3000

Same issue here Retropie straight out of the box at the 3.8 download you will need to downgrade the firmware to 1.68, "But" if you go into the RetroPie Menu and download the latest config file, you will then need to upgrade back to 1.69 or 1.70 (as it appears they have made recent changes)

yoink

@Abstract3000 I'm going to hold off on any beta firmware from 8bitdo until it's stable. Is 1.70 beta working for you? What changed?

Abstract3000

@yoink said in 8bitdo SNES30 Bluethooth Input Issues:

@Abstract3000 I'm going to hold off on any beta firmware from 8bitdo until it's stable. Is 1.70 beta working for you? What changed?

Yeah it seems to work fine, It is the firmware my controller was shipped with. from what I have read it only improved the following:
1.Improve automatic connection.
2.Make the LED blink much quicker when the controller is in auto-connect status.

and I can say with 1.70 installed retropie synchs much quick with it.

yoink

I wouldn't expect a controller to ship with beta firmware. Are you using this firmware? http://forum.8bitdo.com/thread-1179-1-1.html

BuZz

Just FYI, I have a couple of controllers that the retroarch mapping doesn't work for, but without our "workaround" for the older firmware it does, so I will introduce an option in the bluetooth settings to switch this behaviour. It will need to be changed "before" settings up your controls.

yoink

@BuZz Is that related to the issue I've been having with the 2.68 Beta firmware for the SNES30?

BuZz

I hope so.

yoink

@BuZz So when I used my SNES30 controller with 2.68Beta5 firmware, ES was fine, but Retroarch and all the games only the D-Pad worked. Only by downgrading to 2.67 stable did the controllers work again in Retroarch after unpairing, pairing, then setting them up in ES. Should I update Retropie to fix this issue addressed here? If so, what method should I use?

BuZz

if you update retropie-setup it has a new mode in the bluetooth setup to turn off the controller mapping hack that is needed for libretro emulators with the older firmware. You will need to remove / repair the gamepad first make sure the setting is off, and then reconfigure the controller in Emulation Station.

Or just stay on the older firmware if it works for you.

yoink

@BuZz Just updated the firmware to stable 2.68 on the SNES30 controllers, disabled the hack, removed then repaired. Both are now working. Thanks.